You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
classes to handle both encounters and variant encounter data
encounter autocomplete searches by encounter name and variant name
encounter presented in legible embed
ability to view encounter variants in their proper context (by default, or optionally?)
Further development:
include message component that can generate a combat progress track (with a prompt to adjust challenge rank) directly from the encounter
alternatively: the progress track is simply attached to the encounter output, encapsulated in its own embed
this is mainly a convenience to quickly set up a progress track
generated track could include button to reference the original encounter
generated track could include "tactics" and "goals" notes in one of its fields - perhaps even a way to randomly select among those tactics/goals if someone wants a prompt?
once text input is available, it could prompt the user for a more precise objective
ideally this isn't "front and centre" (to avoid inadvertantly tilting people towards dealing with encounters by combat) but is still easy to find/use
generate some thumbnails to include with the encounters
i'm thinking the 1-5 hexagon rank indicator used in the book, but tweaked slightly so it reads well on both light and dark UX
depending on how the licensing for the book's art pans out, could include entire illustrations?
encounter autocomplete searches by rank (+ includes rank info in returned strings... perhaps only if there's a rank being searched?)
encounter autocomplete searches by type (Creature, Human, etc)
DBSet for encounters instead of dictionary
users can store custom encounters in dbset
users can store custom variants of 'vanilla' encounters in dbset
The text was updated successfully, but these errors were encountered:
a fairly straightforward data reference command to view encounters from the book. in dataforged, these are available in
encounters.json
.sample command:
/encounter [autocomplete:encounter] ephemeral?:true keep-message?:false
MVP:
Further development:
The text was updated successfully, but these errors were encountered: