SP Dungeons

0.2.0 prototype · Minecraft Java 26.2 · Fabric · Java 25+

Create dungeon templates, enter private group rooms and return to your entrance through native SP menus. Each run is a separate room in the dedicated dungeon dimension.

This is a playable room prototype. Encounters, bosses, loot, entry fees, level gates and physical entrance portals are not implemented yet.

Canonical location: Minecraft / sp-dungeons. The former standalone repository is archived; its original history and 0.1.0 release remain preserved.

Open the SP panel

Use /dungeons or /spdungeons. The window uses the SP dark emerald background, gold borders, tabs, selectable entries and scrollable details.

• Dungeons: choose a template and press Enter dungeon to create a new private room.
• My runs: choose one of your existing rooms and press Resume run. This does not rebuild the room.
• Group: invite an online player, accept an invitation, or press Return to entrance.
• Admin: administrators can open the shared SP Core management window.

The included Forgotten Crypt template is immediately usable. It creates a protected 17 × 17 stone room. RUINS uses a sandstone room instead. These are simple test templates, not finished adventures.

Create a new dungeon

1. Open /spadmin → SP Dungeons → Dungeons → Add dungeon.
2. The ID is assigned automatically, for example dungeon_000001.
3. Enter the name and description, then choose CRYPT or RUINS from the style dropdown.
4. Press Apply or Apply and close. Cancel discards the draft.
5. Open /dungeons, select the new entry and press Enter dungeon.

Saving a template does not generate world blocks. Entering starts a new run. Editing or disabling a template affects future runs; existing rooms keep their frozen template and remain resumable by their members. Disable is reversible; there is no destructive Delete or Reset action.

Bring your group

The creator enters first, then opens /dungeons → Group, enters an online player's name and clicks Invite. The invited player opens /dungeons → Group → Accept invite. Invitations expire after two minutes and require the creator to remain inside when accepted.

Up to eight participants can share one prototype run. Every participant has an individual entrance/return point. This is per-run membership, not a global party or guild system. Starting a fresh run creates another separate copy. Other groups cannot enter through the UI or a forged run ID.

On exit, choose Return to entrance. The room and membership history remain saved, so you can return using My runs. Disconnecting and rejoining retains an active visit.

After death, vanilla respawning and the installed mods' loss rules apply, then SP Dungeons returns the player to their recorded entrance. It does not add a second item, coin or RPG-XP penalty. Dropped items remain in the old room and can be recovered by resuming it. No room is automatically reset or deleted.

Requirements

Commands and access

Player-facing results appear in the native panel; the console retains text status/list/reload output. Creative mode alone does not grant administrator access. Existing Core session/revision checks protect catalog changes. Dismount before entering a room.

Storage and limits

• Shared server catalog: config/sp-dungeons/dungeons.json, format 2. Up to 128 templates, stable IDs, names up to 80 characters and descriptions up to 512.
• Format-1 metadata loads automatically with CRYPT/enabled defaults. The first upgraded catalog save preserves the original as dungeons.json.pre-v2; existing backups are not overwritten.
• World-specific runs, frozen templates, member history and active return points: <world>/sp-dungeons.json.
• Generated rooms: <world>/dimensions/sp_dungeons/instances/, in a dedicated void dimension.
• Catalog/history network snapshots are paged. Requests use server-owned session tokens and permission/membership checks.

Room slots are never reused or cleared: the prototype supports 4096 runs per world, with eight members per run. A short technical rate limit protects room creation from repeated clicks. No daily cooldown or automatic cleanup policy has been chosen. Breaking/placing/using blocks is disabled in the test dimension to protect its geometry; administrators' world-edit commands are outside these interaction guards.

Back up the complete world before upgrading or removing the mod, and return everyone to their entrance before uninstalling. A blocked entrance is searched vertically for free space; if no position is available, clear it as an administrator. Missing entrance dimensions or failed saves preserve the return record for recovery. Separate Minecraft player/chunk files and instance metadata are not a crash-atomic transaction.