These values are then referred to by the die roller nodes elsewhere in the sheet.
Looks like to copy the HTML in here isn't possible so here's alink to it at googleDocs:

http://docs.google.com/View?id=dc9bxccj_205kbg9k5g3

BTW the calculations are all switched off for the purposes of displaying the "code".

So anyway you can see there's some fairrly sophisticated calculation going on in there although of course you can never model a complex system like D&D perfectly by any means. For example the calculation of AC goes like this.

The dexterity / dodge part of AC has a sub-calculation for where dodge bonuses apply and where they do not (flat footed).

For where dodge bonuses apply:


Here you can see that the dexterity is compared to the armor's max dexterity value so that id someone casts Cat's Grace and their Dex is boosted it automatically knows that that won't help someone in plate armor much. Now there's no mention of dodge here because dodge is a bonus that would apply to this value (called "Dodge", though I could have called it Dexterity_Aspect_Of_AC_when_Not_Flatfooted I suppose).

For when flat-footed the formula is different:

Note that this calculation says that people with dexterity less than ten don't get a better AC for being flat-footed!

There's a physical aspect to AC which is calculated as simply:

Those three are all values that can have bonuses applied to them. They also happen to all be ignored by touch attacks so it's convenient to group them together.

The four AC results are then simply 10+!@Dodge@!+!@Physical@! for regular AC and take either the didge bonus or the physical bonuses (or both) off for flat footed or touch attacks.

Another example of the power of the min/max is with applying strength bonuses to weapon damage. Let's say for a two handed weapon. the die roller is pretty simple:


Not sure if the square brakets are getting through. You get the idea.

!@Melee@! is defined as the sum of !@BAB@! and !@Str_Base@! (it is in a grid that sums columns automatically)

!@2H_Damage@! is defined as,


Looks like I have a uppercase/lowercase typo on one of those str_base's but case doesn't matter in my system. A huge improvement (IMO) I forgot to mention elsewhere. Note that again here if someone has a strength below 10 then fighting two handed doesn't do less damage than fighting one handed which would be silly so the house rule I have is that it does regular damage in that case. There's a global !@Damage_Base@! added to all damage so you can easily apply the effect of spells such as Bless (+1 damage to all friendly creatures).

it would be achieved by typing in to chat:


Except Bless also gives a +1 to hit so you'd also want:


And you could write both those into a node called Bless inside the character sheet and activate both effects for a single click or by typing in "Bless" (and nothing else) to chat while that PC's alias is selected (or when your player name matches the character name). You could even (I think!) type in /all Bless if you had a lot of PCs.

If you are wondering why there is a "Dex_Base" and also a "Dex" it is because in D&D 3.5 there are many effects which say they are effecting "Dexterity based checks" but strictly speaking do not effect Dexterity. eg they don't alter the AC. So things like Move Silently and Open Locks and Initiative are effected by "Dex" but your AC is only using "Dex_Base" in its calculation and thus misses any bonuses applied to "Dex". You can add bonuses to either Dexterity directly or to the Dex bonus. In D&D 3.5 it can matter because named bonuses don't stack (and yes the system can handle that too) if they are on the same entity but an enhancement bonus to Dexterity will be stackable with an enhancement bonus to "Dexterity based checks". They're not the same.

The more complex bonus stuff is handled by the /effect command which has a (optional) variable for the name of the type of bonus (eg "competence", "moral", "resistance", "luck", "insight", "enhancement") and room for some unimplemented stuff like duration.

/bonus is the quick and easy command

Don't confuse with /add command which permanently adds to the node (by editing it). /bonus doesn't change the node, but does change the result when anything asks for the node's value. These bonuses are saved between sessions and can be reviewed in a dialog.

What I need next is a time stamp feature and of course as ever, shared data.