Beta v0.60.7 Patch Notes

v0.60.7 Patch Notes

A small but important hotfix on top of v0.60.6. One critical security fix (a non-admin user could delete another player's save file via a hidden command) and one new admin feature (server-wide permadeath / resurrection controls so sysops running their own MUD server can pick the death model their server uses).

SECURITY: cross-player save deletion via hidden Main Street command

Same player who responsibly disclosed the v0.60.5 trusted-AUTH bypass also flagged this one: typing the bare word settings or config from the Main Street prompt (with no leading slash, no menu hint, no documentation) opened a hidden "SETTINGS & SAVE OPTIONS" menu. The menu exposed all-players save management: Load Different Save, Delete Save Files, View Save File Information, Force Daily Reset, Change Daily Cycle Mode. In MUD or online mode, any non-admin user could use this to delete the admin's save file, or any other player's save.

The repro was: in MUD mode, register a regular user account. Type settings or config from Main Street as that non-admin user. Pick "Delete Save Files." Pick the admin's save. Gone.

The menu was originally a single-player save-management UI from the desktop / standalone build. When MUD mode was added, the bare-word handler for these commands was never gated, so it stayed reachable globally. The visible [~] Settings hotkey on Main Street has always routed to the SAFE per-player preferences menu (combat speed, auto-heal, intimate scenes), which is the only thing players ever needed from "settings." The dangerous all-players menu had no visible entry point at all, only the hidden bare-word command, which functioned as an undocumented backdoor.

A v0.60.6 attempt removed the bare-word settings / set cases from one source file but missed a duplicate override in another. The reporter retested on the live server post-deploy and showed the menu still opening via config.

The fix: the dangerous menu and all of its helper methods are deleted entirely (594 lines removed). No code path can reach the all-players save-management UI from any context. The visible [~] Settings hotkey continues to work and routes to the safe per-player preferences as before.

What this means for you:

• The visible [~] Settings menu (combat speed, auto-heal, intimate scenes, language, font scale, etc.) is unchanged. All your per-character preferences still work exactly the same.

• Single-player save management (Save Game Now, Load Different Save, Delete Save Files, etc.) is no longer reachable from the in-game Main Street menu. If you want to manage saves, use the standalone editor: launch UsurperReborn --editor or pick [G] Game Editor from the title screen. Same functionality, proper UI, single-player only by design.

• Force Daily Reset and Change Daily Cycle Mode are no longer in the in-game menu. Sysops who need them can use the SysOp Console (BBS), the admin dashboard (MUD), or the SysOp Config file.

Thanks again to the reporter for two responsible disclosures in two releases. Persistence and care, exactly the right way to do this.

Admin: server-wide resurrection / permadeath controls

Sysops running their own MUD server now have two new knobs in the Online Admin Console under [R] Resurrection / Permadeath Settings:

1. AddedStarting Resurrections (default 3, range 0-99)how many free deaths each NEW character gets before permadeath fires. Setting it to 0 means one death equals permadeath. Existing characters keep their current Resurrections counter unchanged. Only new characters use the admin-set starting count.

2. Online Permadeath ENABLED / DISABLED (default ENABLED): master switch for the whole online death model.

Permadeath ENABLED (default): each death consumes one resurrection. At zero, the next death erases the character permanently with a server-wide red broadcast and a news entry. This is the live-server beta default and matches v0.60.6 behaviour exactly.

Permadeath DISABLED: online deaths route through the legacy single-player penalty menu (Temple, Deal with Death, Accept Fate). The Resurrections counter is no longer consulted. No character is ever erased regardless of how many times they die. This is "softcore" mode for sysops who want a more forgiving server.

Both settings persist in a new SQLite table on the server, are auto-loaded into the game on startup, and survive restart. The admin UI shows the current values, prompts for confirmation on the permadeath toggle (since flipping it changes how every player's next death plays out), and writes an audit log line on every change.

This only affects MUD-server admins. Regular players see no UI change. Default behaviour matches v0.60.6 exactly. The new controls only kick in when a sysop explicitly opens the admin console and changes them.

Files Changed

• Scripts/Core/Character.cs (documentation update on MaxResurrections)

• Scripts/Core/GameConfig.cs (version bump, two new admin-tunable statics)

• Scripts/Locations/MainStreetLocation.cs (deleted the dangerous menu and 10 helper methods, -594 lines)

• Scripts/Systems/CharacterCreationSystem.cs (Resurrections initialised from admin setting)

• Scripts/Systems/CombatEngine.cs (permadeath gate ANDs the new admin toggle)

• Scripts/Systems/OnlineAdminConsole.cs (new [R] menu entry + EditResurrectionSettings)

• Scripts/Systems/PermadeathHelper.cs (soft revive when permadeath disabled)

• Scripts/Systems/SqlSaveBackend.cs (new server_config table, GetServerConfig/SetServerConfig, startup load)

The new server_config SQLite table is created via CREATE TABLE IF NOT EXISTS on first MUD-server startup post-deploy. No manual SQL needed. Empty table on first boot means both settings stay at their defaults (3 resurrections, permadeath enabled).

Beta is live. Bug reports and feedback always welcome. Press the! key in-game or type /bug to report. See you in there.