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
quests and objectives currently have a boolean completed field. this should become an enumy thing of (incomplete|complete|failed). have the splash say the right thing. would require support in edit-card.js's SchemaFields for <select>s. state machine would probably be best implicit in the quest control thing. maybe a different sound than ka-shing for failed quests?
The text was updated successfully, but these errors were encountered:
I'd also quite like for the quest UI in the dashboard admin to have more labelling if that's something you're open to? Possibly a drop-down? Mostly there have been a few times where I've accidentally changed the state of a quest and then had to recreate it.
Another question: is there scope for "current" or "active" to be one of the states? Or is this worked out in a completely different way?
so there's no real concept of "active" quest/objective, apart from the currentQuest campaign session variable, which only governs which quest to show at hte top of the list. i was looking at sorting the quest/objective list by most recent history which seems complex. do you have a suggestion for how it could work?
in the #59 world there would be no separate quest editing on the dashboard widget, and with #126 you'd be able to revert the history (note that you can current fix a quest state by doing it through the cards view not the dashboard). you can fix the ux of the quests block if you like though 🙂
quests and objectives currently have a boolean
completed
field. this should become an enumy thing of(incomplete|complete|failed)
. have the splash say the right thing. would require support in edit-card.js'sSchemaFields
for<select>
s. state machine would probably be best implicit in the quest control thing. maybe a different sound thanka-shing
for failed quests?The text was updated successfully, but these errors were encountered: