World PIN Lock

1. Configure a new world normally and select Create New World.
2. On the World PIN Lock screen, enter exactly six digits. Leading zeroes are allowed.
3. Enter the same digits in the confirmation field.
4. Select Protect and create world.

Choose Create without PIN to leave that world open. If the protection record cannot be stored safely, world creation stops instead of silently continuing with incomplete protection.

Select a world in Select World and choose Manage PIN (Bulgarian: Управление на PIN). The button is disabled until a world is selected and for worlds locked by another running instance.

• No PIN: enter exactly six ASCII digits, repeat them in the confirmation field, then choose Add PIN. Leading zeroes are supported. This also works for old worlds, worlds created without a PIN, and worlds whose PIN was previously removed.
• PIN protected: verify the current PIN first. Wrong attempts use the existing persistent progressive cooldown. After verification, choose Change PIN and enter/confirm the new PIN, or choose Remove PIN and confirm removal separately.
• Cancelling leaves protection unchanged. Management returns to the previous menu without loading a world. A changed credential requires fresh authentication if another management session changed it meanwhile.

Inside a local world, use Esc → World PIN Settings for the same controls. Adding a PIN blocks LAN/online publication immediately and the next world load requires the PIN. For an already shared world, close it and reopen it locally before changing PIN settings; this prevents leaving existing remote connections inside a newly protected world. The settings are unavailable on remote multiplayer servers.

To play, select the protected world, enter its PIN, and select Unlock and play. The world does not start loading before successful verification. A wrong PIN keeps the world closed and counts as a failed attempt.

To change it, select Change PIN, enter the current PIN, enter and confirm the new six-digit PIN, then select Save new PIN and play. The previous PIN stops working immediately after a successful change.

To remove protection, enter the current PIN and select Remove PIN. Standard LAN and online controls return the next time the unprotected world loads.

To delete a protected world, use Minecraft's normal Delete action and enter the current PIN first. After successful verification, Minecraft shows its standard final deletion confirmation. Wrong attempts use the same progressive cooldown as world unlocking.

Failures are counted per world and persist after Minecraft restarts.

No further attempts are accepted while the countdown is active. A correct PIN resets the failed-attempt count and the escalation level.

Protected worlds also show PIN Locked at the end of their mode and version line. Badges have tooltips and narrator descriptions, and their state refreshes once per second.

For a protected world, the mod disables multiplayer and friends controls and blocks the integrated server from publishing either supported LAN/online mode, opening a TCP listener, accepting the Minecraft 26.2 friends/online channel, or logging in anyone other than the local owner. A dedicated server also refuses to start a protected world.

The PIN is never written to disk or logged. Each protected world stores its credential at:

saves/<world>/world-pin-lock/credential

The credential uses PBKDF2-HMAC-SHA256 with 600,000 iterations, a random 256-bit salt, and a 256-bit hash. Records are strictly validated and replaced atomically. Cooldown data is stored separately in the same world-specific directory.

If the protection directory exists but its credential is missing, damaged, too large, symlinked, or unsupported, access is blocked. The mod never silently resets the PIN.

World PIN Lock is a local access gate, not world encryption.

• If the mod is removed, vanilla Minecraft can open the world without a PIN check.
• Someone with filesystem access can remove protection data, modify the mod, or copy the world elsewhere.
• A six-digit PIN has one million combinations and can be attacked offline by someone who obtains the credential.
• There is no forgotten-PIN recovery or back door. Keep secure world backups.
• Mods that replace or deliberately bypass protected Minecraft methods may be incompatible.
• A Minecraft mod cannot prevent another program from copying or uploading world files.

For stronger separation on a shared computer, use separate operating-system accounts, suitable file permissions, and disk encryption. Keep the mod installed in every Minecraft instance used for protected worlds.

Fabric API incompatibility: version 1.1.0 accepts Fabric API 0.160.0+26.2 or a compatible newer build for Minecraft 26.2. Remove outdated or duplicate Fabric API JARs.

Forgotten PIN: restore a backup whose PIN you know. Direct protection-file editing is unsupported and may trigger fail-closed denial.

Temporary block: wait for the displayed countdown. Restarting does not clear it; a successful PIN resets escalation.