nhcarrigan/elysium
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 5 Pull Requests 1 Actions Releases 10 Activity

auto-boss and auto-quest turn off upon failure #40

New Issue
Closed
opened 2026-03-09 12:24:28 -07:00 by amari · 0 comments
amari commented 2026-03-09 12:24:28 -07:00
Copy Link
Copy Source

Description

When a user enables auto-boss or auto-quest, encountering any kind of failure (whether it's a combat loss, resource depletion, or an error condition) causes the automation to completely disable itself. This creates a frustrating experience where players have to manually re-enable the feature after every setback, rather than having the system gracefully handle the failure and continue operating.

We'd love to improve this so that temporary setbacks don't derail the automation experience. The goal is to make these features more resilient and player-friendly — they should work with the player during challenging moments, not against them.

Current Behavior

  • Auto-boss or auto-quest toggles OFF when any failure occurs
  • Player must manually re-enable the feature to continue
  • No indication of why the automation stopped

Desired Behavior

  • Auto-boss and auto-quest should remain enabled even when individual attempts fail
  • The system should be smart about distinguishing between "try again" scenarios and "stop and alert the player" scenarios
  • Players should have clear visibility into what happened and why the automation paused (if it does)

Acceptance Criteria

  • Auto-boss remains enabled when a combat attempt fails; it attempts the next battle automatically
  • Auto-quest remains enabled when a quest attempt fails; it queues up the next attempt
  • The automation clearly communicates to the player if it encounters a critical issue that requires manual intervention (e.g., insufficient resources that can't be replenished)
  • Logs or status messages indicate why the automation paused, if it does
  • User testing confirms the experience feels more supportive and less frustrating during challenging gameplay moments
# Description When a user enables auto-boss or auto-quest, encountering any kind of failure (whether it's a combat loss, resource depletion, or an error condition) causes the automation to completely disable itself. This creates a frustrating experience where players have to manually re-enable the feature after every setback, rather than having the system gracefully handle the failure and continue operating. We'd love to improve this so that temporary setbacks don't derail the automation experience. The goal is to make these features more resilient and player-friendly — they should work *with* the player during challenging moments, not against them. ## Current Behavior - Auto-boss or auto-quest toggles OFF when any failure occurs - Player must manually re-enable the feature to continue - No indication of *why* the automation stopped ## Desired Behavior - Auto-boss and auto-quest should remain enabled even when individual attempts fail - The system should be smart about distinguishing between "try again" scenarios and "stop and alert the player" scenarios - Players should have clear visibility into what happened and why the automation paused (if it does) --- # Acceptance Criteria - [ ] Auto-boss remains enabled when a combat attempt fails; it attempts the next battle automatically - [ ] Auto-quest remains enabled when a quest attempt fails; it queues up the next attempt - [ ] The automation clearly communicates to the player if it encounters a *critical* issue that requires manual intervention (e.g., insufficient resources that can't be replenished) - [ ] Logs or status messages indicate why the automation paused, if it does - [ ] User testing confirms the experience feels more supportive and less frustrating during challenging gameplay moments
naomi closed this issue 2026-03-09 21:12:03 -07:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/elysium#40
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?