-
Notifications
You must be signed in to change notification settings - Fork 1
Module Spawn
j-gaertig-co-dev edited this page Aug 13, 2026
·
2 revisions
Config file: modules/spawn.yml — current version: 1.2 — view current default on GitHub
Enable via config.yml → modules.spawn: true
- A global spawn point (
/spawn) that any player can teleport to. - A separate first-join spawn point — new players are teleported here on their very first join, independent of the global spawn.
- Both points support setting exact coordinates or relative coordinates (
~) at your current position. - Each sub-feature (global spawn, first-join spawn) can be disabled independently, and each command can be individually toggled off in the config.
| Command | Description | Permission |
|---|---|---|
/spawn |
Teleport to the global spawn point. | plainbase.spawn.spawn |
/setspawn [x y z] |
Set the global spawn (uses your current location if no coordinates given). | plainbase.spawn.setspawn |
/disablespawn |
Disable the global spawn. | plainbase.spawn.disablespawn |
/setfirstspawn [x y z] |
Set the spawn location used for a player's first join. | plainbase.spawn.setfirstspawn |
/disablefirstspawn |
Disable the first-join spawn. | plainbase.spawn.disablefirstspawn |
| (all Spawn commands) | Grants every permission of this module. | plainbase.spawn.admin |
spawn:
enabled: false
location:
world: world
x: 0.0
y: 0.0
z: 0.0
yaw: 0.0
pitch: 0.0
first-spawn:
enabled: false
location:
world: world
x: 0.0
y: 0.0
z: 0.0
yaw: 0.0
pitch: 0.0
commands:
spawn:
enabled: true
setspawn:
enabled: true
disablespawn:
enabled: true
setfirstspawn:
enabled: true
disablefirstspawn:
enabled: true-
spawn.enabled/first-spawn.enabledare set automatically totruethe moment you run/setspawnor/setfirstspawn— you don't need to flip them by hand, but/disablespawn//disablefirstspawnflip them back off. - Each entry under
commands:lets you disable an individual sub-command without touching permissions.
Known quirk:
/setfirstspawninternally writes to afirstspawn.location...path (no hyphen) while the enabled flag lives underfirst-spawn.enabled(with a hyphen). This is intentional/inherited behavior, not a bug — don't "fix" it by hand-editing the YAML structure.