Tony Vargas
Legend
"Process Sim" in the Forge-ite way pem is using it? Not really, no, for the reasons he sites, AFAICT (I'd hate to have to argue Forge stuff with him, as he's far more conversant than I).Which D&D is, though, at least in 2E and 3E.
OTOH, 3e, in particular, lends itself to treating the rules as de-facto laws of physics. Mainly because of impressions it gives, more than specifics. For instance, the impartial-feeling & consistent way it uses Class & level for PCs (pc classes), NPCs (NPC classes), and Monsters (CR, LA, PC/NPC class levels), and the similar way it uses Feats and Skill Ranks. The way STR scales and doesn't max out in a way that's a little more organic for really big monsters (and profoundly leathal to melee types who fight really big monsters). Then there's also the way the community, in blatant defiance of Rule 0, put so much faith in RAW. It's not the same thing as simulation or process-sim, because it doesn't start with the things being simulated, but with the rules. But it creates a very similar vibe.
Yet all those things are highly abstract and not neatly correlated. You don't know what kind of 'wound' a sword caused, just how many hps it represents, just for the obvious instance that we've been poking around (again) in this thread.It's telling you that you are simulating the process of swinging a sword, by considering all of these factors and how they interact with each other, to determine whether or not you hit and how much damage you deal.