Introduction

SoapsFloor runs vertical dungeon sessions on Paper 26.2. Each room is a multi-floor challenge built from WorldEdit schematics.

Core concepts

Term	Meaning
Room	A saved dungeon with a starter area and one or more floors
Session	A live party inside one room
Floor	One schematic layer; mobs spawn, then the floor drops when cleared
Locked floor	Optional paid floor the host can buy in the lobby before the run
Wand	Admin editor tool for creating and editing rooms
Floor Editor	Wand hub for Access, Mobs, Countdown, and Commands per floor
Room Settings	Wand nether star for room-wide PvP, auto-start, party scaling, keep inventory/XP, countdown, min/max
Weakness	Optional challenge modifier voted before the run; boosts rewards

What players do

1. Join a room with /sf join <id>, /sf quickjoin, clickable /sf list, a join sign, or the GUI hub.
2. Wait in the starter room. The host can buy locked floors in the lobby when they exist.
3. Vote on a weakness (if enabled).
4. Survive the countdown, then clear mobs on each floor.
5. Reach the final playable floor to win. Stats and rewards are recorded.

What admins do

1. Place .schem files in plugins/SoapsFloor/schematics/.
2. Run /sf wand create <id> and define the starter box, entry/exit, and floors.
3. Configure floors in the Floor Editor hub (Access, Mobs, Countdown, Commands). Use Room Settings (nether star) for PvP, auto-start, party scaling, join-in-progress, keep inventory/XP on death, countdown, and min/max players. Optionally enable Falling Hazard.
4. Assign reward tables with /sf setreward if you use rewards.yml.
5. Adjust global behavior in config.yml and reload with /sf reload.

Plugin files

plugins/SoapsFloor/
  config.yml
  messages.yml
  gui.yml
  weaknesses.yml
  rewards.yml
  schematics/
  rooms/
  data/

Rooms are stored as YAML under rooms/. Schematics are never overwritten on update if they already exist.