v0.57.6 - Patch Rollup
Four player reports and a community PR, shipped together. Huge thanks to everyone who reported issues with repro steps; this build wouldn't exist without them.
Aldric Auto-Equipped a Weak Weapon
"Aldric just auto equipped worst weapon than he was using. I chose Pass after a fight and he grabbed it. Used: Soldier's Sword of Thunder (Blessed) [WP:407 AP:3 Def:+3 Str:+3 Dex:+3 Wis:+3 Crit:5% Leech:5%] Exchanged to: Fine Tempered Blade [WP:123] No bonuses. I fixed that, thankfully. The original weapon was in my inventory." — Lumina
The auto-pickup check reads your companion's current weapon by ID. If that lookup ever fails; which it can, transiently, in multiplayer between session ticks the slot looked empty, and any non-zero loot counted as a "100% upgrade." Aldric's Sword of Thunder slot hit exactly that case and the first weak weapon to drop stole it.
Fixed. Auto-pickup now cross-checks the stored ID directly. If the slot has an ID but the database can't resolve it right now, the pickup is refused for that slot rather than risking a silent downgrade. A warning-level log records every time this path fires, so any future lookup instability is visible in the debug log instead of eating a legendary weapon.
Spending Time With Children Was Broken
"The game claims I spent time with the chosen child, even if I did not that day. I could spend time with newly born child, but not the rest. Now with any of them." — Lumina
The "Spend Time with Child" interaction has a daily cooldown. The old check compared against a shared day counter that gets overwritten between concurrent player sessions in multiplayer. Once your last-interaction day caught up to the counter's current value, the cooldown stayed active forever. Newborns worked exactly once, then locked.
Fixed. The cooldown is now a real-time 20-hour gap per child, independent of any shared counter. Saves with stuck cooldowns self-heal the next time you try to interact.
Dungeon Monsters Weren't Coming Back
"I run out of enemies to fight before the boss, making the battle very very difficult to unachievable. Dungeons are supposed to reset every hour with a thematic message — is that not happening?"
It wasn't. The hourly respawn logic was coded and the "the dungeon stirs" thematic message was written, but the gate required the entire floor to be cleared before the timer even started; which almost never happened for the players who needed it most (the ones stuck in front of a boss they couldn't beat). Their floors sat empty forever.
Fixed. Respawn now keys on your last visit to the floor, not your last full clear. Retreat to town, come back an hour later, monsters are back, and the thematic message that was gathering dust in the loc files finally plays. Boss rooms and special floors (seals, secret bosses) are unaffected — once you beat them, they stay beaten.
Daily Murder Cap: 3 Per Day
With the murder-mechanics rework below, execution no longer deletes characters — the remaining "don't murder the whole town" deterrent was 2 days of prison. Not much of a brake on a committed evil build.
Added a hard cap of 3 non-bounty murders per day. After the third, a short message fires — "Your hands tremble. You have already murdered 3 souls today — even your conscience has limits." — and the attack is refused. Bounty contracts are exempt; those are sanctioned kills, not murder.
Murder Mechanics Rework (Community Contribution)
Huge thanks to community member LowLevelJavaCoder for submitting this one — the first external code contribution of this scale. They're added to the in-game credits (press at the main menu) and to the project credits page.
The v0.53.11 "murder is a capital offense" system tied execution to character deletion. This PR tones it down.
What's different now:
- Execution no longer deletes the character. You die through the normal death-and-resurrection flow instead.
- Prison sentence is 2 days instead of 3, with equipment and bank gold preserved. The magistrate now takes half your on-hand gold as a fine instead of stripping everything.
- New "surrender or fight" branch. When the guards arrive to arrest you, you can choose to fight them off. Beat all five Royal Guards and you escape capture entirely (with +100 darkness for resisting arrest). Lose the fight and you're arrested. Die and you revive at the Temple normally.
- Darkness reward for murder is now +250 (was +50), paired with -125 chivalry. Murder leaves a deeper stain on the soul than lesser crimes.
Follow-up cleanup after the merge fixed a handful of smaller issues, including:
- "I killed all the guards but still got sent to prison." The PR checked a victory flag that only gets set in berserker-mode combat, not normal fights. Won fights registered as "not victorious" and players got arrested anyway. Now checks the actual victory outcome.
- Renamed the guards from Murder Guard to Royal Guard. The original name was unintentionally funny for what's supposed to be the Crown's enforcement arm.
- Rewrote the magistrate's flavor text. The old strings claimed "all equipment confiscated" and "bank account frozen and seized" — both of which the new softer code doesn't actually do. Players thought they'd lost gear they still had. Text now matches the actual punishment (a fine, not total seizure).
- Fixed a darkness double-count bug that would've granted +500 per murder instead of +250.
- Input validation on the surrender/fight prompt so a misclick doesn't silently throw you into the guards fight.
Why The Day-Counter Bug Class Keeps Appearing
Both the Aldric item-downgrade and the parenting cooldown failures trace back to the same pattern: a piece of state built for single-player as a process-wide singleton, which gets shared across concurrent multiplayer sessions and bleeds between players. Previous hotfixes moved NPC inventory, companion state, and world state off singletons. The parenting timestamp is the newest migration. More of this cleanup over time is expected.
No other changes in this build.
