The map stays gone on a world that had already removed it, and a single-player world is locked down by installing the mod rather than by configuring it afterwards.

Two things were wrong, and they compounded. The engine silently places the host of any single-player or LAN world in the highest-privilege role, which carries every privilege the game defines — including the one this mod used to decide who is an admin. So "exempt the admins from the client-side closures" quietly meant "exempt every single-player", and the coordinate HUD, the debug readouts, the clipboard positions, the screenshot metadata and the world map were all handed straight back to the one player who had just installed a mod to take them away. Nothing said so.

The world map was the worst of it, because there the mod did not merely fail to close something — it forced it open. The map closure was written on the assumption that the only reason a world ever forbids a map is that this mod forbade it, so lifting the closure had to override the game's own answer or the exemption would have granted nothing. On Wilderness Survival that assumption is false: the playstyle switches the map off when the world is created, before this mod is consulted. An exempt host therefore got back the vanilla M-key map on a world that had never had one — installing Null Lockdown left you with more map than not installing it.

Both are fixed at the root. The admin exemption now lifts nothing until an operator lists what it should lift; the privilege is still configurable, so a server that wants its moderators to keep the debug screen names the closures and nothing else changes. And the map closure no longer invents an answer in either direction: with the closure on the map is closed, and with it lifted the game decides, exactly as the other five closures have always behaved.

For an operator who does want one role to keep a working map on a locked-down world, the instrument is the game's own: grant that role the allowMap privilege in serverconfig.json. That works on a playstyle-closed world as well as a mod-closed one, which the old override never did, and the start-up privilege report has always watched for it.

Operators upgrading: if you relied on the old behaviour where holding controlserver lifted all six client closures, that is no longer the default. Name them in AdminExemptions in ModConfig/nulllockdown.json to get it back. A config file written by an earlier version does not carry that key, so it will load with nobody exempt.

A way to undo what installing this mod does to a world.

Null Lockdown forces four of the savegame's own world settings — allowMap, allowCoordinateHud, allowDeathwaypointing and temporalGearRespawnUses — and that change persists with the save. Removing the mod never put them back, so a world that had run it kept a map-less, coordinate-less, waypoint-less configuration for good, with nothing left installed to explain why.

/nulllockdown restore puts them back. It needs nothing to have been recorded in advance: a savegame still knows the playstyle it was created on, and a playstyle is a named set of world settings, so the value each key held before the mod arrived is still derivable on any existing world. A world made on Wilderness Survival or Homo Sapiens keeps its own false for the map and the coordinate HUD — those playstyles set it themselves, and restoring such a world to the game's default would hand it a map it never had.

allowDeathwaypointing is the reason this has to be a command rather than a note. The game never declares that key, only reads it, so /worldconfig refuses to set it and a player fixing their world by hand can repair three of the four and has no route to the fourth. The restore removes the attribute outright, which is the state it was in before.

The command prints its plan and changes nothing until the word confirm follows it, and it refuses outright while any of the forcing switches in ModConfig/nulllockdown.json are still on — with those on, the guard would simply force the keys again at the next start. A restart applies the result.

One thing it cannot recover: a value changed by hand with /worldconfig after the world was created but before this mod was installed. The playstyle has no record of that, and neither did we. The command says so when it runs.

Now required on the client. The mod patches the coordinate HUD, so a client without it saw readouts this mod exists to remove; a server running Null Lockdown will no longer admit one.

No gameplay changes.

Initial Release.