Getting startedguide

First steps

A first permission group, the spawn, the first warp and kit, the currencies, and the ladders worth writing before opening the server.

The nodes a player needs

Nothing is declared in plugin.yml. There is no permissions: block, so no node carries a default: — an operator passes every check because operators pass every check, and everybody else starts with nothing.

A default group, with every module on, wants roughly:

exyliasurvivalcore.homes
exyliasurvivalcore.homes.set
exyliasurvivalcore.homes.del
exyliasurvivalcore.homes.tp
exyliasurvivalcore.homes.max_homes.3
exyliasurvivalcore.back
exyliasurvivalcore.tpa
exyliasurvivalcore.tpa.here
exyliasurvivalcore.tpa.accept
exyliasurvivalcore.tpa.deny
exyliasurvivalcore.tpa.cancel
exyliasurvivalcore.tpa.toggle
exyliasurvivalcore.rtp
exyliasurvivalcore.warps.use
exyliasurvivalcore.near
exyliasurvivalcore.kits
exyliasurvivalcore.crates.use
exyliasurvivalcore.bounties.use
exyliasurvivalcore.afkzones.use
exyliasurvivalcore.farming
exyliasurvivalcore.rankup
exyliasurvivalcore.stats
exyliasurvivalcore.settings
exyliasurvivalcore.repair.hand
exyliasurvivalcore.playerutils.ping
exyliasurvivalcore.economy
exyliasurvivalcore.economy.pay
exyliasurvivalcore.shop
exyliasurvivalcore.shop.sell
exyliasurvivalcore.market
exyliasurvivalcore.market.sell
exyliasurvivalcore.auctions
exyliasurvivalcore.auctions.sell
exyliasurvivalcore.orders
exyliasurvivalcore.orders.create
exyliasurvivalcore.trade
exyliasurvivalcore.vaults
exyliasurvivalcore.graves
exyliasurvivalcore.missions
exyliasurvivalcore.rewards
exyliasurvivalcore.votes
exyliasurvivalcore.seasons
exyliasurvivalcore.boosters
exyliasurvivalcore.protections

Three commands check no permission at all

/spawn, /reclaim and /playtime have no node. /spawn is harmless; the other two write: /reclaim runs the commands of the highest section the player holds, and /playtime <rewardId> claims that reward. What a player may actually get is decided by the reclaim section's own permission, and by whether they have earned the playtime — but the commands themselves are open to everybody.

Eight nodes still start with `survivalcore.`

The prefix everywhere else is exyliasurvivalcore., but the core admin, rankup admin, farming admin and portals admin nodes were written without it. Grant them exactly as spelled on the Permissions page; an exyliasurvivalcore.admin does nothing.

An administrator wants survivalcore.admin plus each module's own admin node — they are not covered by one another.

Setting the world up

Set the spawn

/spawn set where you are standing. modules/spawn/config.yml decides whether players are also sent there on first join, on every join and on respawn, and whether that overrides a bed.

Make a warp

/warpadmin → create. Each warp has a display name, an icon, a cost, a permission and a location, and /warp lists the ones a player may use.

Make a kit

/kitadmin → create, then Edit items to fill it. Cooldown, use limit, permission, whether it auto-equips armour and whether it is given on first join are all on the same screen.

Look at the currencies

/economyadmin opens the currency list. The currencies live in the database: a fresh server gets the shipped ones, and a server that had plugins/ExyliaLib/currencies.yml gets that file imported once instead. See Economy.

Point RTP at a world

modules/rtp/worlds.yml ships world enabled and world_nether disabled. A world that is not in that file cannot be reached with /rtp. Pre-generate the area with Chunky and the pool fills in seconds instead of minutes.

The ladders worth writing first

Most content is built from in-game menus and stored in the database. Nine things are files, because they are ladders rather than objects:

File	What it is
`modules/rankup/ranks.yml`	The rank ladder: order, requirements, rewards
`modules/playtime-rewards/rewards.yml`	What is claimable at 30m, 1h, 5h, 25h, 100h
`modules/farming/categories.yml`	What counts as farming, per-N rewards and milestones
`modules/kill-rewards/rewards.yml`	What a kill pays, and the streak milestones
`modules/reclaim/config.yml`	The `/reclaim` sections and their cooldowns
`modules/repair/groups.yml`	Repair prices and cooldowns per permission group
`modules/missions/missions.yml`	The missions a daily or weekly rotation draws from
`modules/seasons/seasons.yml`	The rankings: which stat counter, which period, which prizes
`modules/votes/votes.yml`	The vote sites, what a vote pays, the streaks and the vote party — the shipped site URLs are placeholders to replace

`ranks.yml`'s own header lists requirement types that do not exist

The comment lists money, playtime, kills and level. The real set is money, playtime, placeholder and permission. A requirement with any other type is dropped silently when the file is read, so the rank becomes free. See Progression.

A first look around

/sc reload from the console re-reads the configuration and the menus. Module switches need a restart, and the reload names the ones waiting for it.
/settings is what a player uses to turn off the broadcasts and requests they do not want.
Most admin commands open a menu: /minesadmin, /cratesadmin, /warpadmin, /kitadmin, /lootchestsadmin, /spawnersadmin, /powerupsadmin, /regenzonesadmin, /portalsadmin, /jumpadmin, /afkzonesadmin, /bountyadmin, /duelroomsadmin, /economyadmin, /shopadmin, /rewardsadmin, /itemupdater and /protections admin. /marketadmin, /auctionadmin, /missionsadmin and /vaultadmin print their subcommands instead.
Everything under menus/admin/ is rewritten from the jar on every start and every reload. Edit the player-facing menus under modules/<id>/menus/ instead: those keep your edits when the plugin updates.

Something missing on this page? Tell us on Discord