Content generated with AI — it may contain mistakes.

ExyliaSurvivalCore/HelpUpdated in v1.2.2

FAQ

The questions that come up: menus that get overwritten or updated, modules that moved to other plugins, what needs a restart, and the settings that do nothing.

Page 24 of 382 min read

My admin menu edits keep disappearing#

Everything under menus/admin/ is regenerated from the jar on every start and every /survivalcoreadmin reload. Edit the owner menus under lang/<code>/ instead: those keep your edits.

A menu I edited did not get the new button#

Your edits win. When a new version changes a default you had left alone, the change waits in /exylialib updates for you to apply or keep; only keys that did not exist before are added on their own. A menu whose shipped menu-version went up is replaced whole, and your previous file is kept beside it. See Menus.

I turned a module off and nothing changed#

Module switches need a restart. /survivalcoreadmin reload re-reads the configuration files, the module settings and the menus, but never enables or disables a module; it names the ones still waiting.

Where did crates, the shop, protections and the rest go?#

They are their own plugins now, with their own data and commands. The list, with a link for each, is on the Modules page. A leftover modules/blocked-items/rules.yml is read by ExyliaWarzone, not by this plugin.

Why are jumppads, join messages and portals off?#

When ExyliaLobby is enabled, jumpads, join-leave and portals stay off and defer to it. This is the defer-to-exylia-lobby setting in the core configuration. See Configuration.

Stacked items and mobs look wrong next to ExyliaSpawners#

Spawner stacking belongs to ExyliaSpawners; the optimization module yields to it. See Optimization.

Missions never finish, or seasons rank nobody#

stats is off. Missions measure progress against the stat counters and seasons rank them, and only the stats module keeps those counters.

A permission does nothing#

Check the prefix. A few older administration nodes start with survivalcore. rather than exyliasurvivalcore.; grant them exactly as spelled on the Permissions page. Players' nodes default to true and administration nodes to op, so you only grant what you want to change.

%exyliasurvivalcore_stats_value_streak% shows nothing#

streak is not a stat id. Use %exyliasurvivalcore_stats_value_current_streak% or %exyliasurvivalcore_stats_rank_best_kill_streak%, and see Placeholders for the ids that exist.

Two players in the same repair group pay different prices#

They are not in the same group. Repair groups resolve in file order, not by price: the first group in groups.yml whose node a player holds is the one that applies. Write the best group first.

What does the plugin need to run?#

Paper 1.21.1 or newer (Folia 1.21.4 or newer) and ExyliaLib. PacketEvents is optional. See Installation.

Can two servers share this?#

Yes. Point them at the same database and homes, warps, kits, ranks, statistics and the other stored data are shared; homes and warps carry the server they were set on, so /home and /warp cross the network, and TPA requests reach players on another server. See Database.

Something missing on this page? Tell us on Discord