- GET ALL /battle
- GET /battle/
- GET /battle//step/
- POST /enemy
- POST /player
npm install
npm start
- Dice System (d20, d100, future: Dice Pool)
- Resources
- Level
- Challenge Rating (CR)
- Attack(s)
- Damage Range
- Hit bonus
- Attack Type (Melee, Ranged, Magic)
- Damage Range (Min-Max)
- ALTERNATIVE: Damage roll text XdY(+/-)B
- Sub-Types: Spell
- Spell Level
- FUTURE: Saving Throws (would require saving throws on Combatants)
- Represents:
- "Consumables":
- Potions, Scrolls, etc
- "Regenerators":
- Magic Spell Slots
- IDEA: Each spell level uses (level) resources from Regenerators pool
- Daily Abilities
- Daily Item uses
- Magic Spell Slots
- "Consumables":
- Option 1: Single "Resource" value representing all things for players
- CON: There is a difference between "Consumables" and "Regenerators"
- PRO: Simplest
- Option 2: 2 Resource values (Consumables and Regenerators)
- CON: Might not be granular enough for encounter vs. daily regen
- PRO: Versatile but still relatively easy
- Option 3: Track/add resources separately
- CON: Extremely Granular, and different systems have lists of these
- PRO: Most versatile, allows for system-like simulation
- Something that translates from "Level" to stats for Combatants
- Turn tracking for a combat
- FUTURE:
- Something for adding/storing enemies from bestiaries
- Balancing around taking full day instead of using resources