Dec inheritance
<MonsterDec decName="Tier4Monster" abstract="true">
<gold>4d100</gold>
<loot>Tier4LootTable</loot>
<health>70</health>
<damage>3d6</damage>
<visuals>
<icon>t4monster.png</icon>
<color>#ff8080</color>
</visuals>
</MonsterDec>
<MonsterDec decName="GoblinElite" parent="Tier4Monster">
<!-- Derives from Tier4Monster, so we get all the existing members automatically -->
<name>Goblin Elite</name>
</MonsterDec>
<MonsterDec decName="GreaterBlob" parent="Tier4Monster">
<!-- Here, we override a few members piecemeal -->
<!-- GreaterBlob still has the same gold, loot, and visuals of the Tier4Monster -->
<health>120</health>
<damage>2d6</damage>
</MonsterDec>
<MonsterDec decName="GoldBlob" parent="GreaterBlob">
<!-- You can inherit from non-abstract decs too -->
<gold>12d100</gold>
<!-- Child composite types can be overridden piecemeal as well -->
<visuals>
<!-- The color is changed, but the icon is still `t4monster.png` -->
<color>#ffff80</color>
</visuals>
</MonsterDec>
When you need many things that are in some way similar, it can be useful to create a set of default values that can be applied on demand. Abstract decs, determined by the abstract="true" attribute, won't be included in the Dec database.
A standard single-inheritance structure is not always sufficient, but multiple inheritance is not yet implemented.
Most members are straight-out replaced if specified in child types. This includes collections, such as List and Dictionary. More fine-tuned behavior can be accomplished with merge modes.