Content generated with AI — it may contain mistakes.

ExyliaSurvivalCore/GuidesUpdated in v1.2.2

Set up spawn, homes, warps and teleports

Set the server spawn, choose how many homes players get, add priced warps, tune TPA and /back, and open random teleport worlds, with the warmup and cooldown settings of each.

Page 5 of 3812 min read

Seven modules of ExyliaSurvivalCore move players: spawn, homes, warps, TPA, /back, random teleport and /near. This page gets each one working and shows the settings you will want to change.

Five of them (spawn, homes, warps, TPA and /back) share the same warmup: a countdown shown as an action bar and a title, cancelled by moving or by taking damage, with a per-second sound and a permission that skips it. Each module has its own copy of those settings, so a home can be instant while a warp takes five seconds. A teleport that cannot happen says why instead of doing nothing.

Rules that apply to every teleport#

  • Combat. With combat-blocks-teleports: true (the default, top level of config.yml), /spawn, /home, /warp, /rtp, /back, /tpa and portal teleports are refused while the player is in combat, whichever plugin tracks it, and the refusal says how long is left. A permission that skips the countdown does not skip this. Teleports the server makes on its own (spawn on join, an admin's force) do not ask.
  • Per-rank times. A rank lowers a countdown or a wait with a permission number, and the lowest number a player holds wins: exyliasurvivalcore.<module>.warmup.<seconds> for spawn, homes, warps, tpa, back and rtp, exyliasurvivalcore.warps.cooldown.<seconds>, exyliasurvivalcore.rtp.cooldown.<seconds> (lowers a world's own cooldown, never raises it) and exyliasurvivalcore.tpa.cooldown.<seconds>. The module's bypass node still skips the countdown entirely.
  • Menu buttons (rename, icon, delete, teleport) need the same permission as the command they stand for.

Set the server spawn#

Stand where players should appear

Go to the world and spot where new and respawning players should land.

Run /spawn set

Run /spawn set (needs exyliasurvivalcore.spawn.set). A placement wizard stores the spot. /setspawn and /survivalcoreadmin setspawn do the same.

Choose when players go there

In modules/spawn/config.yml, set teleport-on-join, teleport-on-first-join, respawn-at-spawn and override-bed-spawn (see below).

/spawn teleports to it and needs exyliasurvivalcore.spawn (granted to everyone). Where Apollo or Feather is installed, the spawn is also pushed to clients as a waypoint.

Every server keeps its own spawn, named after the server, so servers sharing one database do not overwrite each other. A server with no row of its own reads the single spawn older versions wrote and saves a copy under its own name. If the spawn's world is not loaded on that server, respawn-at-spawn leaves the respawn point alone.

Spawn settings
SettingDefaultWhat it does
warmup-seconds3Countdown before the teleport
cancel-on-move, cancel-on-damagetrueWhat stops it
permission-bypass-warmupexyliasurvivalcore.spawn.bypassThe node that skips the countdown; the string is yours to change
blacklisted-worlds[]Worlds /spawn refuses from
teleport-on-joinfalseEvery join goes to spawn
teleport-on-first-jointrueA first join goes to spawn
respawn-at-spawntrueDeath sends them to spawn
override-bed-spawntrueEven when they have a bed

Choose how many homes players get#

Players use /sethome [name], /home [name], /delhome <name> and /homes for the menu (rename, change icon, teleport, delete). /homes set|del|tp are the long forms. Deleting a home gives a slot back, so /delhome asks for no node.

How many homes a player gets is a permission tier: exyliasurvivalcore.homes.max_homes.<n>, and the highest node they hold wins. max-homes (default 3) is only what somebody with no node gets. To give VIPs ten homes, grant them exyliasurvivalcore.homes.max_homes.10.

Homes store a server alongside the coordinates, so /home works from anywhere on the network. In the Settings ▸ Homes menu of /survivalcoreadmin you can change these without editing files. /homesadmin delhome <player> <home> and /homesadmin listhomes <player> need survivalcore.admin.homes and run from the console.

Homes settings
SettingDefaultWhat it does
max-homes3The floor for everybody
default-home-namehomeWhat /sethome with no name is called
default-iconGRASS_BLOCKThe icon a new home gets
home-name-max-length16Longest name
warmup-seconds and friends3As for spawn
permission-bypass-warmupexyliasurvivalcore.homes.bypassThe node that skips the countdown
blacklisted-worlds[]Worlds /sethome and /home refuse from
waypoint-colour85,255,85Colour of the home markers on the client, as R,G,B

Add a warp and charge for it#

Open the warp editor

Run /warpadmin (needs exyliasurvivalcore.warps.admin) or click Admin ▸ Warps in /survivalcoreadmin.

Create it

Click Create ▸ Warp, then open the new warp.

Fill in the details

Use Warp ▸ Location (a wizard places it), Warp ▸ Display name, Warp ▸ Icon, Warp ▸ Cost and Warp ▸ Permission to set where it goes, how it looks, what it costs and who may use it. Warp ▸ Status turns it on or off.

/warp (or /warps) opens the list of the warps a player may use; /warp <id> goes straight there. A warp without a permission of its own needs exyliasurvivalcore.warps.use (granted to everyone). Warps cross the network too.

The cost is checked before the countdown but charged on arrival. Money and cooldown are only spent when the teleport succeeds: walking out of the countdown, a world that is no longer loaded or a server that cannot be reached costs nothing and starts no cooldown. To charge in a currency other than the default, set currency to an id from ExyliaLib's economy.yml (see Economy).

The cooldown (cooldown-seconds, 0 is off) is counted per player and per warp and stored in the database (sc_warp_cooldowns), so a warp that puts the player on another server does not hand them a fresh cooldown.

Bypass nodeWhat it skips
exyliasurvivalcore.warps.bypassThe cost, the cooldown and the warp's countdown
exyliasurvivalcore.warps.bypass.costThe cost
exyliasurvivalcore.warps.bypass.cooldownThe cooldown
Warps settings
SettingDefaultWhat it does
warmup-seconds3Countdown before the warp
cancel-on-move, cancel-on-damagetrueWhat stops it
cooldown-seconds0Seconds before the same player may use the same warp again. 0 turns it off
blacklisted-worlds[]Worlds /warp refuses from
currencyemptyThe currency costs are charged in: an id from ExyliaLib's economy.yml, items and experience included. Empty is the default currency

modules/warps/menus/warp_setup.yml is an admin editor that lives with the player menus rather than under menus/admin/, so your edits to it are kept. Everything under menus/admin/ is rewritten from the jar on every start.

Let players teleport to each other (TPA)#

/tpa <player> asks to go to them; /tpahere <player> asks them to come to you. /tpaccept (also /tpyes) and /tpadeny (also /tpno) answer, with an optional name to pick which request; with no name they answer the newest one. /tpacancel [player] takes back a request you sent (needs exyliasurvivalcore.tpa.cancel).

The request is a centred prompt with clickable [✔ ACCEPT] and [✘ DENY] buttons. /tpatoggle flips whether a player receives requests; /tpatoggle autoaccept and /tpatoggle confirm flip the other two. /autotpaaccept is an exact duplicate of /tpatoggle autoaccept. All three preferences are also on the /settings screen, reading and writing the same rows. Server-wide defaults are in Settings ▸ Requests.

The other player can be on any server of the network. That needs ExyliaLib's cross-server teleports; where they are not available, a player on another server reads as not found. A tpa moves the sender and a tpahere moves the target, and where the other player stands is read when the countdown ends, not when the request was accepted. Auto-accept is decided by the target's own settings, on the target's server.

A sender who switches servers before the answer is not moved

Each server keeps its own copy of the requests that involve somebody standing on it. A sender who leaves for a third server while waiting has no copy there. When the target accepts, the target is told it was accepted, but nobody moves.

TPA settings
SettingDefaultWhat it does
request-expire-seconds60How long a request lives
send-confirm-defaulttrueWhether a confirmation screen is shown before sending
tpa-enabled-defaulttrueWhether players accept requests at all to begin with
auto-accept-defaultfalseWhether requests are accepted without asking
request-cooldown-seconds10Seconds before the same player may send another request to the same target. 0 turns it off
warmup-seconds3Countdown after a request is accepted
blacklisted-worlds[]Worlds where requests cannot be sent or accepted

The confirmation screen shows a player on another server by that server's name; their world, position, health and food read —. tpa.request-received and tpa.request-here-received in messages.yml are lists, one line per entry, and a line may open with [center]. An existing messages.yml gets the new prompt only where the line was still the old default.

Let players return with /back#

/back returns a player to where they were. One place is remembered per player. It is stored in the database (sc_back), survives a restart and follows the player to another server. It stops being offered after teleport.back-history-minutes in config.yml (30 by default). exyliasurvivalcore.back.bypass skips the countdown.

Which moments are remembered: save-on-death (true), save-on-teleport (true) and save-on-portal (false). Homes, /back and a TPA on the same server record the place only when the teleport succeeds, so a countdown the player walks out of leaves no /back pointing at where they stood. A warp records it after its countdown, just before the move.

Open random teleport worlds#

List the world

Add the world to modules/rtp/worlds.yml. A world that is not in the file cannot be reached at all.

Set its box and price

Give it min-x, max-x, min-z, max-z, an optional price, a display-name and an icon.

Reload

Run /survivalcoreadmin reload.

/rtp opens a world list; /rtp <world> goes straight to one. A pool keeps safe locations ready in advance, so /rtp is instant rather than a search. Pre-generating the world's chunks, with Chunky for instance, shortens the time the pool needs to fill. /rtpadmin (alias /rtpa, needs exyliasurvivalcore.rtp.admin): forcertp <player> <world> (also needs exyliasurvivalcore.rtp.admin.forcertp) sends somebody and pool reports the pool. The Settings ▸ Random teleport menu edits the module settings.

exyliasurvivalcore.rtp.bypass always skips both the cooldown and the price; the two config keys bypass-cooldown-permission and bypass-price-permission ship with that same value and are yours to change.

Random teleport settings
Per-world keyWhat it does
enabledWhether it is offered
display-name, iconHow it appears in the menu
min-x, max-x, min-z, max-zThe box searched
priceCharged per teleport
cooldownSeconds, or -1 to use the module's own
biome-blacklistBiomes a landing spot may not be in
Module settingDefaultWhat it does
warmup3Countdown, in seconds
cooldown300Seconds between uses; a world's own cooldown overrides it
max-attempts15Tries to find a safe spot before giving up
cancel-on-move, cancel-on-damagetrueWhat stops the countdown
yaml
pool:
  enabled: true
  size: 40
  max-concurrent-searches: 3
  refill-interval: 30

Show who is nearby#

/near (exyliasurvivalcore.near) lists nearby players with their distance and a compass direction. exyliasurvivalcore.near.radius.<n> raises a player's radius, highest node winning, but max-radius still caps it.

Near settings
SettingDefaultWhat it does
display-modeUIUI for the menu, CHAT for a chat list
default-radius100Searched when nothing else applies
max-radius1000The ceiling, permission included
cooldown-seconds3Between uses
distance-typeHORIZONTALHORIZONTAL or 3D, for filtering; the distance shown is always horizontal

Commands and permissions#

CommandWhat it doesPermission
/spawnTeleports to spawn, after the warmupexyliasurvivalcore.spawn
/spawn setSets spawn where you standexyliasurvivalcore.spawn.set
/home [name]With a name, teleports to that home; without, opens the home menuexyliasurvivalcore.homes.tp
/homesOpens the home menu, or says you have noneexyliasurvivalcore.homes
/homes set [name]Sets a home here; no name uses the configured default nameexyliasurvivalcore.homes.set
/homes del <name>Deletes one of your homes—
/homes tp <name>Teleports to one of your homesexyliasurvivalcore.homes.tp
/sethome [name]The same as `/homes set`exyliasurvivalcore.homes.set
/delhome <name>The same as `/homes del`—
/homesadminPrints the usage linesurvivalcore.admin.homes
/homesadmin delhome <player> <home> [confirm]Deletes somebody's home, online or notsurvivalcore.admin.homes
/homesadmin listhomes <player>Lists somebody's homes and where they aresurvivalcore.admin.homes
/warp [id]With an id, warps there; without, opens the warp listexyliasurvivalcore.warps.use
/warpadminOpens the warp editorexyliasurvivalcore.warps.admin
/backReturns to your last locationexyliasurvivalcore.back
/rtp [world]With a world, teleports somewhere random in it; without, opens the RTP menuexyliasurvivalcore.rtp
/rtpadminPrints the usage lineexyliasurvivalcore.rtp.admin
/rtpadmin forcertp <player> <world>Sends an online player on a random teleportexyliasurvivalcore.rtp.admin.forcertp
/rtpadmin poolShows how many locations each world has cachedexyliasurvivalcore.rtp.admin
/nearLists the players around youexyliasurvivalcore.near
/tpa <player>Asks to go to a player, on any server of the networkexyliasurvivalcore.tpa
/tpahere <player>Asks a player to come to youexyliasurvivalcore.tpa.here
/tpaccept [player]Accepts that player's request, or the latest oneexyliasurvivalcore.tpa.accept
/tpadeny [player]Denies that player's request, or the latest one—
/tpacancel [player]Withdraws a request you sent to that player, or your latest one—
/tpatoggleTurns receiving requests on or offexyliasurvivalcore.tpa.toggle
/tpatoggle autoacceptTurns accepting every request automatically on or offexyliasurvivalcore.tpa.autoaccept
/tpatoggle confirmTurns the confirmation before sending a request on or offexyliasurvivalcore.tpa.confirm
/autotpaacceptThe same as `/tpatoggle autoaccept`exyliasurvivalcore.tpa.autoaccept
PermissionWho has itWhat it allows
exyliasurvivalcore.spawnEveryone`/spawn`
exyliasurvivalcore.tpaEveryone`/tpa`
exyliasurvivalcore.tpa.hereEveryone`/tpahere`
exyliasurvivalcore.tpa.acceptEveryone`/tpaccept`
exyliasurvivalcore.tpa.denyEveryoneKept for old setups; denying never asks for it
exyliasurvivalcore.tpa.cancelEveryoneKept for old setups; cancelling never asks for it
exyliasurvivalcore.tpa.toggleEveryone`/tpatoggle`
exyliasurvivalcore.tpa.autoacceptEveryoneAuto-accepting requests
exyliasurvivalcore.tpa.confirmEveryoneThe confirmation before sending a request
exyliasurvivalcore.homesEveryone`/homes`
exyliasurvivalcore.homes.setEveryoneSetting homes
exyliasurvivalcore.homes.delEveryoneKept for old setups; deleting never asks for it
exyliasurvivalcore.homes.tpEveryone`/home`, `/homes tp`
exyliasurvivalcore.homes.renameEveryoneRenaming a home in its menu
exyliasurvivalcore.homes.iconEveryoneChanging a home's icon
exyliasurvivalcore.rtpEveryone`/rtp`
exyliasurvivalcore.backEveryone`/back`
exyliasurvivalcore.warps.useEveryone`/warp`, `/warps`; also what a warp without its own node needs
exyliasurvivalcore.nearEveryone`/near`
The teleport section of config.yml

config.yml has a teleport section, handed to ExyliaLib on start and again on every /survivalcoreadmin reload. It holds the defaults for any teleport that does not set its own, plus what cross-server handovers share. Values outside a range are clamped.

yaml
teleport:
  warmup-seconds: 0.0
  cancel-on-move: true
  cancel-on-damage: true
  safe-search-radius: 5
  safe-max-attempts: 32
  cross-server-ttl-seconds: 300
  cross-server-settle-seconds: 0.5
  back-history-size: 3
  back-history-minutes: 30
  tpa-expiry-seconds: 60
  tpa-max-pending: 8
  random-max-attempts: 16
KeyRangeWhat it does here
warmup-seconds0 or moreThe countdown for a teleport no module times itself. Decimals allowed
cancel-on-move, cancel-on-damagen/aThe same, for that countdown
cross-server-ttl-seconds30–3600How long a destination queued for another server stays valid
cross-server-settle-seconds0.05–5How long the arriving server waits before moving the player
back-history-minutes1–1440How long /back keeps offering its place

warmup-seconds here reaches the teleports meant to be instant: a spawn, home or /back for a player holding that module's bypass node, a warp for a player holding exyliasurvivalcore.warps.bypass, any module whose own warmup-seconds is 0, a portal, and the move a warp makes after its own countdown. Raising it above 0 adds a second countdown to warps and a plain one, with no title or sound, to the rest.

safe-search-radius, safe-max-attempts, back-history-size, tpa-expiry-seconds, tpa-max-pending and random-max-attempts belong to ExyliaLib's own teleports. No module here uses them.

Teleport failures share four lines in messages.yml: errors.server-unreachable, errors.world-not-loaded, errors.player-not-found and errors.teleport-failed.

Something missing on this page? Tell us on Discord