[FEATURE] 2e beta->gamma packet support

[LegoFed3]

The 2e beta packet adds a lot of changes that will necessitate tweaks to the system to properly support the new rules. This issue is to track and prioritize them.

Must Haves

• [x] Change high level weapon/recovery scaling to have a static bonus based on level
  • We could get by just adding +10/20/30 to weapon damage and recovery expressions, but this might be a good time to start thinking about a more general damage bonus field
  • I'd rather not get rid of the explicit per-level number of dice for now, as I have a sneaking suspicion this part of the rules isn't quite finalized yet
• [x] Update conditions
  • Add new Charmed and Frenzied conditions
  • Update Vulnerable, Confused, Stunned and Hindered conditions
• [x] Disable recently added breath reminder if 2e enabled
• [x] Automate breath weapon extra crit range
• [x] Add new default bonuses for items
  • Need a bonus to Str, Con Dex checks for gloves
  • And one to Int, Wis, Cha checks for helments
  • Probably best to code individual attribute bonuses, these can be used to support older items that yield such bonuses outside their default bonus
• [x] Update boots bonus to also apply to initiative (and rename it)
• [x] Support separate usage tracking for shields and necklaces
  • [x] Add new bonus fields to equipment template and sheet
  • [x] Add new PC sheet elements and listeners
  • [x] automate usage tracking
• [x] Update actions to have 4 special roll fields
  • A few monsters like derros need them
• [x] Adjust base stats for core classes
• [x] Separate strength and size for monsters
  • [x] update structure
  • [x] write migration
  • [x] update npc sheet styling @asacolips
  • [x] update SRD monsters
• [x] Fix skulls always resetting to zero on combat deletion
• [x] Add 11th level to PC powers
• [x] Add some way (keyboard modifier?) to easily roll a spell at +1 level (max 10, or 11 if set)
  • Needed by some bard and wizard stuff at the very least, and the bard's applies to all spellcasters
• [x] Icon symbols / names in equipment
  • This might require a custom font
  • At the very least we should add a field to store a related icon in plain text

Should Haves

• [x] Change all instances of "daily" to "arc"
  • That would leave macros having to use internal names, but that's fine I reckon, not player facing enough to bother with
• [x] Update all instaces of "omega" with "iconic"
• [ ] Support "actual extra hit points"
  • These kind of behave like temporary hit points but do last until consumed, and presumably count for stuff that counts your current actual hit points (like fear)
• [x] Add support/automation for stoke on dragons

Nice to Haves

• [x] Automate barbarian Grim Determination
• [x] Complete support for Combat Rhythm
  • We already have logic to set and update it, we're missing automation for rolling two d20s
• [ ] Expand death saves to 7 @asacolips
  • Sorcerers have a talent that allows them to die at 7 skulls - maybe make number configurable?
  • Could we make it so that there's a marker denoting death between the first five and the last two?
• [ ] Add a state and UX to mark powers as not usable
  • Bard has powers that (sometimes) grant to use of other powers when expended;
• [x] Add recharge/desperate usage mode (needed for the C feat of the Fighter's Web of Steel)

Uncategorized.

• [ ] NEEDS RULES CLARIFICATION natural X+ triggers imply on hit unless explicitly contraticted? (This would apply to 1e as well, I guess)
• Add 2e support to power importer and browser
  • Uncategorized because strictly speaking it's not needed unless we have 2e content to ship
  • [x] Power importer can load and discriminate between 2e and 1e content, with the latter as fallback
  • [x] compendium browser loads data from the 2e module, and ideally discriminates between 1e and 2e content @asacolips

[asacolips]

Superwash in the 13th Age discord had this suggestion for displaying Stoke on dragon tokens, and I like it in concept. @ben then followed up with suggesting using v12's new dynamic token ring feature, and that sounds like an interesting option to me once we have time to dig into the API for it.

In either case, we'll want to structurally implement Stoke using resources (along with likely adding Custom Resources to NPCs). Even if we don't have something like dynamic token ring integration, implementing it as a resource will allow the token to be configured to use it as the secondary resource bar.

[asacolips]

Article with dynamic token ring docs for reference: https://foundryvtt.com/article/dynamic-token-rings/