Homes and Teleportation

Setting useful homes

Homes are saved return points for places you expect to revisit. The safest home is inside land you control, with enough space to arrive without falling into hazards or loading into another player's protected area.

• Claim the area before treating a home as permanent.
• Give homes descriptive names so you do not teleport to the wrong location.
• Keep at least one dependable base or recovery home rather than filling every slot with temporary locations.
• Remove obsolete homes when a project moves or a location is no longer safe.

Home limits and supporter perks

The number of homes available to a player can depend on current server permissions and supporter-rank benefits. The live Store/rank listing and the server's own feedback are the authority for the current allowance.

• Do not rely on an old rank screenshot for a current home limit.
• If a rank upgrade changes your allowance, existing homes should not be treated as proof of the current maximum.
• Use the account/order route for a missing purchased perk rather than repeatedly deleting homes to test it.

Spawn, back and teleport restrictions

• /spawn returns you to the main server hub when your current state permits it.
• /back can be a rank or permission benefit and may cover eligible previous teleport/death locations.
• Combat, duels, protected inventory restoration or another active system can intentionally block teleport commands.
• A blocked teleport should be treated as a state restriction first, not immediately as a broken command.

Safe travel habits

Teleport convenience should support survival rather than replace basic recovery planning. Keep food, spare gear and a known route home when exploring far from established builds.

Planning homes around real survival travel

Homes are most useful when each one solves a real travel problem. A main base, a long-term project and a distant resource area are easier to manage than a list of temporary locations whose purpose you no longer remember.

A teleport point is not a substitute for land protection. If a saved home lands in an area another player can alter, the destination can become unsafe even though the command itself still works.

• Keep your main recovery home inside a claim you control.
• Name homes by purpose rather than by the date you created them.
• Use RTP to discover territory, then set a home only after choosing and claiming the final location.
• Review old homes before a rank downgrade or permission change rather than assuming every saved entry remains usable.

Diagnosing a blocked home or back command

Teleport commands are deliberately sensitive to combat and other protected gameplay states. The most useful first step is therefore identifying what state the server thinks you are in, not repeatedly running the command.

• Read the exact command response.
• Check whether combat, a duel, inventory restoration or another protected flow is still active.
• Check your current home allowance if the problem occurs while setting rather than using a home.
• Use the current in-game command help if an alias or permission has changed.
• If a restriction persists after the protected state clearly ended, report the command, location and approximate time.

Designing a dependable home network

A useful home network reflects the places you actually revisit rather than every temporary stop made during exploration. Keeping a small number of clearly named destinations reduces mistakes and makes rank-based limits easier to manage.

The strongest permanent home is inside claimed land with a safe arrival area and enough room for the build to evolve.

• Keep one dependable main-base home.
• Use additional slots for long-term projects or distant resource areas.
• Remove obsolete destinations instead of relying on memory.
• Treat RTP as discovery and homes as deliberate saved travel.

Why teleport restrictions exist

• Combat restrictions stop teleport commands becoming an escape mechanic.
• Duels and protected inventory flows can temporarily isolate movement while state is saved or restored.
• A rank or permission change can affect which home/back actions are available.
• When a block persists after the protected state should have ended, record the command and exact response before reporting it.