Note Update: Due to discovered issues in Game Play testing (see next post), the Class Database release has been delayed by 1 week. The next release for the RPGMaster series of APIs will be a major upgrade, in two instalments. The release is intended to continue the push to externalise every possible rule-set in the RPGMaster API suite, so it is easy to change the behaviour to work with other versions of D&D, or even totally different RPGs. To this end, the Character Class properties, Attack & Damage Calculations, and Races & their properties will all be provided with databases allowing simple addition or overwriting of the default characteristics and rules applied by the APIs during game-play. 1. Character Class Database - 16th March release (updated date) As mentioned in my post of February 25 , I have been working on defining Character Class rules in a database, with: Allowed weapons, armour & shields Non-proficient weapon penalties Attacks per round progression Wizard specialist & banned schools Priest Major & Minor spell spheres Non-standard spells per level progressions Non-Wizard / Non-Priest spellcaster definitions Class power specifications As you might come to expect now, these aren't just lists but can actively restrict or allow Players / Characters to use or be prevented from using the relevant items/spells/powers and only at the experience levels defined. This behaviour can be configured in a menu available to the DM. The DM / Game Creator can add their own classes or overwrite the supplied classes in their own version of the Class-DB using the information in the Class Database Help Handout created when the APIs (specifically the AttackMaster or MagicMaster APIs) are loaded. Final test campaign games are being held this coming Friday and Monday (UK afternoon), and (assuming all goes well, and previous test games have all been fine) the APIs will be merged Monday (US time) for release on Wednesday. 2. Attack Calculations Database - anticipated 23rd March release To date, the APIs have only supported standard AD&D2e weapons attack/damage calculations, and then only as I have interpreted them (which I believe to be a strictly correct interpretation, but who knows if I'm right!). The up-coming Attacks Database allows DMs / Game Creators to amend the way attacks are calculated. As with all other databases, the APIs use standard Roll20 functionality to support creation and editing of the specification. The system supplies many derived and calculated fields taken from data on the Character Sheet combined with that provided in the supplied databases (such as the Weapons Database), which are referenced in the Attack Calculation using the ^^field-name^^ syntax (common with the existing Effects Database). A full list of the provided derived/calculated fields is provided in the Help Handout that comes with the APIs & Attacks Database. DMs / Game Creators can also read any available Character Sheet data using the @{^^cname^^|data-field-name} (^^cname^^ will be replaced by the APIs with the name of the Character/NPC/Monster doing the attack) . Even the attack dice to roll in the calculation can be specified as different from 1d20 - if your RPG calls for it. Attack definitions can be specified to be generic for all attacks, and can also be specific to a Race, Class, or even an individual Weapon! for example: MW-ToHit-Elf would be a specific "ToHit" attack calculation for Melee Weapons only used by any character of the race "Elf" RW-ToHit-Bard would be a specific Ranged Weapon "ToHit" attack calculation for the character class "Bard" RW-Targeted-Attk-Longbow-of-Valour would be a Targeted attack calculation (which gives full details of the target AC & HP as well as the attack rolls) only for the Weapon "Longbow-of-Valour" and no other weapon. Weapon takes priority over Class, which takes priority over Race, and if none of them exist the default is used. Monster/Creature attack calculations, using innate attack definitions on the Character Sheet, are also catered for and can be altered. Weapon vs. Armour modifiers are displayed to the Attacking Player/Character for Targeted Attacks, and are available for the attacked Player/Character/NPC to view (the Slash/Pierce/Bludgeon modifiers are specified for each Armour entry in the Armour Database). The Armour calculations are also exposed in a similar manor to Attacks in the Attacks Database.