prestige should not reset the "first kill" state of bosses. #39

New Issue

2026-03-09T12:03:40-07:00

amari commented

2026-03-09 12:03:40 -07:00

Description

Hey team! 🎯 We've stumbled upon something that's affecting the player experience in a way that doesn't feel quite right. When players prestige their character, the "first kill" state for bosses is being reset — which means bosses they've already defeated for the first time are showing as "new" again. This breaks the intended progression feeling and creates confusion about what they've already accomplished.

The prestige system should feel like a fresh challenge that respects and celebrates past victories, not one that erases the memory of them. Let's make sure that first-kill achievements carry their weight through prestiges!

What's Happening Now

Player defeats a boss for the first time (achievement state is set)
Player initiates prestige
Boss "first kill" state resets to uncompleted
On new prestige run, boss appears as if it's being fought for the first time

What Should Happen Instead

The "first kill" state for bosses should persist across prestige cycles and remain marked as completed, even though other progression elements (character level, gear, etc.) reset as intended.

Acceptance Criteria

Boss "first kill" state persists after a prestige is triggered
Completed first-kill achievements remain visibly marked across prestige runs
Other prestige reset mechanics continue to function as designed
QA confirms the behavior with at least 2 different bosses across different prestige cycles

Additional Notes

This feels like a data persistence issue where the achievement flag might be grouped with resettable progression. We'll want to make sure the first-kill marker lives in the right place in our data structure!

## Description Hey team! 🎯 We've stumbled upon something that's affecting the player experience in a way that doesn't feel quite right. When players prestige their character, the "first kill" state for bosses is being reset — which means bosses they've already defeated for the first time are showing as "new" again. This breaks the intended progression feeling and creates confusion about what they've already accomplished. The prestige system should feel like a fresh challenge that respects and celebrates past victories, not one that erases the memory of them. Let's make sure that first-kill achievements carry their weight through prestiges! ## What's Happening Now - Player defeats a boss for the first time (achievement state is set) - Player initiates prestige - Boss "first kill" state resets to uncompleted - On new prestige run, boss appears as if it's being fought for the first time ## What Should Happen Instead The "first kill" state for bosses should persist across prestige cycles and remain marked as completed, even though other progression elements (character level, gear, etc.) reset as intended. ## Acceptance Criteria - [ ] Boss "first kill" state persists after a prestige is triggered - [ ] Completed first-kill achievements remain visibly marked across prestige runs - [ ] Other prestige reset mechanics continue to function as designed - [ ] QA confirms the behavior with at least 2 different bosses across different prestige cycles ## Additional Notes This feels like a data persistence issue where the achievement flag might be grouped with resettable progression. We'll want to make sure the first-kill marker lives in the right place in our data structure!

hikari referenced this issue from a commit

2026-03-09 21:35:09 -07:00

fix: preserve boss first-kill state across prestige

~~hikari referenced this issue 2026-03-09 21:35:26 -07:00~~

fix: preserve all-time stats, achievements, and boss first-kill across prestige #47

naomi referenced a pull request that will close this issue

2026-03-09 21:53:20 -07:00

fix: preserve all-time stats, achievements, and boss first-kill across prestige #47

naomi closed this issue

2026-03-09 21:53:59 -07:00

naomi referenced this issue from a commit

2026-03-09 21:54:00 -07:00