TECH said: Is there any particular reason for not having Damage Die and Number of Dice text boxes in the weapon sections? Additionally, neither the Type or Notes text boxes are referenced by the default macros resulting in needing to manually insert references to have them appear in uses of the macros. The main reason there is no separate damage die/number of dice text boxes is because I was trying to make the damage area as generic and capable of handling a variety of weapon types as possible. My campaign has things like: 1d8cs>9 +[[@{weapon1damagestat}]][weapon dmg stat] +@{weapon1enh}[Weapon Enh] +@{weapon1specialize}[Weapon Specialization] +?{Favored Enemy Bonus?|None, 0 |@{repeating_notes1_0_note1body}, @{repeating_notes1_0_note1date} |@{repeating_notes1_1_note1body}, @{repeating_notes1_1_note1date} |@{repeating_notes1_2_note1body}, @{repeating_notes1_2_note1date} |@{repeating_notes1_3_note1body}, @{repeating_notes1_3_note1date} |@{repeating_notes1_4_note1body}, @{repeating_notes1_4_note1date} |@{repeating_notes1_5_note1body}, @{repeating_notes1_5_note1date} }[Fvrd enemy bns] +?{Power Attack Bonus?|0}[Pwr Attk] +?{Other Damage Bonus?|0}[Other Damage Bonus] ]] phys +[[?{Fire?|No, 0|Yes, 1}*(1d6cs>7) [fire damage] entered into the damage area. I don't have the sample macros reference the type or notes text boxes because I never did decide how I liked having the type reference in there best (so I left it up to the user) and for the notes/special properties, depending on how folk used that section before the roll templates even existed (my campaign used it as general information about the weapon but not necessarily something that was needed to be displayed with each attack), I figured that there would be as many folk who did not want it displayed as did want it displayed. And to my mind it is easier to paste {{notes=@{weapon1specialproperties} }} in the attack somewhere than it is to find it and delete it. You can even add the notes in a custom Ability on the Attributes and Abilities tab, ie: @{weapon2fullattackmacro} {{notes= @{weapon2specialproperties} }} is perfectly valid (though if you have the notes= part in both places, only one of them is actually displayed). So basically: that's how my brain works so that's how I programmed it. :)