v0.11.0

• Portrait art (if available), with background removed if that option was chosen, fall back to token art
• Name
• All bars (these can be shorter than they are on the map to fit a small tooltip)
• Property values (e.g. HP, AC) as defined in the campaign
• "Friendly" (if in your party), "Hostile" (if generated as a monster), or "Neutral" (if neither)

• Special UI: when a token has the 'dead' condition active, shade the token art dark red, and put a big red X over it.

• Special UI: when a token has the 'dying' condition active, shade the bottom half of the token dark red, and put a red downward arrow over it.

• Analysis: the roll() function is likely the culprit. Enhance roll() to take a second, optional argument to pipe the output to chat (default true). When generating these actions, use 'false' for this. Return the result of the action in the final function return, which will appear in chat log.

• [x] The category for ability check actions should be 'ability check'. Similar for saves.
• [x] The category for attack actions should be 'attack'.

• For System properties, increment order by 1000. Thus, an order value can be 0, 1000, 2000, etc; no other values.
• For Campaign properties, allow any integer value except those divisible by 1000, to ensure they are always ordered between system properties.
• This allows campaign owners to sort system and campaign properties in any mix without collision (assuming they have fewer than 1000 properties total, which seems reasonable).
• [ ] Bug: order seems wonky. TODO: document all broken use cases

Pagination isn't intuitive; infinite scroll would be better

Having a hard time with images. Didn't see Artwork tab at first

[ ] Character Sheet

• [x] Add an option to set ability scores with guidance, instead of manually.
  • This spawns a modal.
  • For 5e, offer the following options:
    • Standard array
    • Custom array (input your own numbers)
    • Point buy (input a number of points to spend, and it calculates how many points you have left as you assign them to different ability scores)
  • For System 8:
    • Show a "drop zone" for each of the 6 stats
    • Show a draggable 16, a 14, two 12s, and two 10s.
    • They can drag the numbers into the drop zones to assign them to different stats. This ensures all stats are within the valid range, and takes the guesswork out of assigning stats.
    • Additionally, show a -2 draggable, which is optional. This decreases the stat it's dropped on, and once done, a +2 is spawned that can also be dragged to increase a different stat. The +2 cannot be applied to the 16.
    • When all 6 drop zones have a value, allow the user to click "apply", which saves the assigned stats to the character sheet.
  • All of this is for the "base" component of ability scores. Proficiency, racial, etc are not affected.
• [x] Template should apply stats. Logic:
  • Fighter: max out strength and constitution, then dexterity, then intelligence/wisdom/charisma
  • Rogue: max out dexterity, then intelligence, then constitution/strength/wisdom/charisma
  • Arcanist, Psion: max out intelligence, then constitution, then dexterity, then wisdom/strength/charisma
  • Elementalist, Witch, Priest: max out wisdom, then constitution, then dexterity, then intelligence/strength/charisma
  • Warlock: max out charisma, then constitution, then dexterity, then intelligence/wisdom/strength
  • By "max out", I mean:
    • Get the highest valid base score possible. Meaning:
      • 5e: if the user didn't already use the stat wizard, ask for the method (roll, standard array, point buy, custom), and apply the template in a way that gets the highest possible base score for the relevant stats based on that method's rules.
      • System 8: max base stat is 16, so assign 16 to the relevant stats first, then 14, etc until the template is fully applied.
    • In 5e, apply Ability Score Increases as appropriate if they are level 4+.
    • In System 8, use existing proficiency bonus logic to max out stats in order. To wit:
      • Character has (level + 3) * 2 proficiency points to assign to stats (no weight).
      • Max proficiency bonus for one stat = (level + 3).
• [x] In the ability score section in build mode, show a notification if the current ability scores do not match the expected distribution based on the character's class and level, based on logic described above.
  • Special case: in 5e, if they haven't selected an ability score generation method yet, prompt them to do so or to use the wizard to set their stats.
• [x] Feat and Power modals should default to current class(es) if the character isn't classless
• [x] Feat/Power modal filter popup doesn't close on clickout
• [x] Feats and Powers should have full detail tooltips (play, build, and modal)
• [x] Feat and Power modal filter should have 'all valid' option in system 8 (which means ancestry, background, disposition, skill, and all classes the character has, only the ranks they qualify for)
• [x] Feat and Power modal filter is treating multiple filters as AND when they should be OR (note: this may require extending the API to support OR filtering) — backend already handles OR for same-field filters correctly

• Choose one image
• It creates token and portrait from that image, with tokenization and background removal automatically applied respectively. User can then edit each artwork separately as desired.