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

bug: auto-boss stops with "Save rejected: signature mismatch" after first completion #148

New Issue
Closed
opened 2026-03-25 15:10:01 -07:00 by hikari · 0 comments
hikari commented 2026-03-25 15:10:01 -07:00
Owner
Copy Link
Copy Source

Description

When using the auto-boss feature, the first boss fight completes successfully. However, after the first completion, auto-boss halts and displays the error message:

Auto-boss stopped: Save rejected: signature mismatch

Steps to Reproduce

  1. Activate auto-boss
  2. Observe first boss fight — completes successfully
  3. Observe second attempt — auto-boss stops with the signature mismatch error

Expected Behaviour

Auto-boss should continue looping through boss fights without stopping, re-saving state correctly each iteration.

Actual Behaviour

Auto-boss stops after the first fight with a save rejection due to a signature mismatch. This suggests the game state token/signature computed after the first boss fight is not valid when submitted for the second save.

Notes

Likely a state mutation issue — the signature may be computed before state is fully updated after the first fight result is applied, causing the second save to carry an invalid signature.

✨ This issue was created with help from Hikari~ 🌸

## Description When using the auto-boss feature, the first boss fight completes successfully. However, after the first completion, auto-boss halts and displays the error message: > Auto-boss stopped: Save rejected: signature mismatch ## Steps to Reproduce 1. Activate auto-boss 2. Observe first boss fight — completes successfully 3. Observe second attempt — auto-boss stops with the signature mismatch error ## Expected Behaviour Auto-boss should continue looping through boss fights without stopping, re-saving state correctly each iteration. ## Actual Behaviour Auto-boss stops after the first fight with a save rejection due to a signature mismatch. This suggests the game state token/signature computed after the first boss fight is not valid when submitted for the second save. ## Notes Likely a state mutation issue — the signature may be computed before state is fully updated after the first fight result is applied, causing the second save to carry an invalid signature. ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-04-06 19:33:06 -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#148
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?