Beds and homes
Last updated 25 August 2026. Report a discrepancy through the GeoNations Discord.
Beds, saved homes, and the hub form the server's respawn order. Some bed behavior differs from what its chat messages suggest.
Setting a bed respawn
The game saves the respawn point before checking whether the player may sleep. As a result, messages such as "you can only sleep at night" and "there are monsters nearby" do not prevent the bed from setting the respawn point.
Respawn point set appears only when the saved position changes. Using the same bed again may produce no message because that position is already saved.
Sleeping and the night cycle
Night skips when 25% of online players are in bed at the same time (changed 16 August — it used to need everyone). The seasons system still controls how long days and nights run through the in game year, and beds still set your respawn point. See Seasons and temperature.
Missing or obstructed beds
If a saved bed is missing or obstructed at death, the game removes that respawn point without an additional message. A bed placed outside claimed ground can therefore stop working if another player removes or blocks it.
Place beds inside claimed ground and save a /sethome as a separate respawn location. A saved home does not depend on a block remaining in the world.
The respawn chain
| 1. Your bed | If you have a valid respawn point, you wake up there. |
| 2. Your nearest home | No bed, but a /sethome set? You respawn at the closest one. |
| 3. The hub platform | Neither? You come back to the geo_hub platform with nothing, and leaving again costs $50 unless you walk. |
Respawn anchors do not work here. The anchor option is off, so the chain above decides where you respawn. You can still charge an anchor with glowstone, but you will not respawn at it. Do not build your nether base around one.
And there is no free /back — it is switched off by design. Your gear stays in your corpse where you died (see Dying): walk back to it, or pay $1,000 for /deathback (run twice to confirm; PvP deaths lock it for ~17 minutes).
Homes
You get two homes.
/sethome | Saves a home where you stand, under the default name. |
/sethome <name> | Saves a named home. Use this for your second. |
/home | Travels to your home, or lists them if you have more than one. |
/home <name> | Travels to a specific one. |
/delhome <name> | Frees a slot when you have used both. |
The two home limit applies to every player. Common uses are a primary base and one remote location such as a mine, Nether portal, or trading area.
/sethome with a name you already used and the old location is overwritten immediately. Name your two homes something you will recognise.Run /home with no home set and you are sent to spawn instead of getting an error. Homes also work across worlds: a home in the nether is reachable from the overworld and the other way round.
Spawn
/spawn puts you on the hub platform. You cannot use it to escape a fight: the 3 second warmup applies, and in combat every command is blocked for 15 seconds.
Reaching another player
/tpa <player> | Asks that player if you may teleport to them. |
/tpaccept | They run this to let you in. |
/tpdeny | They run this to refuse. |
/tpacancel | You run this to take your own request back. |
An ignored request expires on its own after 120 seconds. You do not have to answer it. You can have at most 5 requests pending at once. Note the direction: /tpa always moves you to them. There is no player command that pulls somebody else to you, so nobody can teleport you out of your own base.
Typing a Bedrock player's name into /tpa? Type it exactly as it appears in the player list. The naming rules are on the Java + Bedrock page.
An accepted /tpa teleports like every other normal teleport: 3 second warmup that movement cancels, then you arrive centred on a block, never in water, with 4 seconds where neither you nor anyone else can deal damage.