Content generated with AI — it may contain mistakes.

ExyliaProtections/HelpUpdated in v1.1.0

Frequently asked questions

Short answers about licences, operators and bypass, missing buttons, refused cores, limits, reloading, WorldGuard and running several servers.

Page 20 of 256 min read

Is ExyliaProtections free?#

No. It is a premium plugin, bought on BuiltByBit and installed as a loader jar that checks the licence on every start. Bought there, the licence is embedded in the jar. See Installation.

I used the protections of ExyliaSurvivalCore. What do I do?#

Update ExyliaSurvivalCore to a release without the protections module, install ExyliaProtections next to it and follow Migration. Nothing is imported: since 1.0.2 the survival core's files, tables and old exyliasurvivalcore.protections* nodes are not read, so copy the settings you changed and grant the exyliaprotections.* nodes. /protections, /ps and /claims keep their names.

The plugin does not start#

It needs ExyliaLib 1.572.0 or newer; the loader installs it, or stages a newer one, and asks for a restart, so restart once more. If the console reports a licence error, check that Exylia-Protections-Loader.jar is the jar from your purchase, and contact support if it is. PacketEvents is optional: without it protecting by selection and raid replays are unavailable, and borders lose their corner pillars (particles still draw). See Installation and Common problems.

Players are told "Protections are still loading"#

The plugin could not read its protections from the database yet. Until it does it refuses building and other changes in every world where land can be protected, so an unreadable database never leaves land open. The console shows the error and it retries every 30 seconds: fix the connection in database.yml. Players with exyliaprotections.bypass are not held back.

As an operator I cannot build in other players' land#

That is intended: exyliaprotections.bypass defaults to nobody, operators included, so an operator can test their own land. Grant it to the staff who must build anywhere. exyliaprotections.admin, which operators have, lets them manage and enter every protection but not build in it. See Permissions.

The Shop button is missing#

The shop lists the tiers with a price above 0, and the hub hides the button when there is none or while cores.enabled is off. Give a tier a price in config.yml or in the tier editor. See Administration and Creating protections.

The Select land button is missing#

It shows only with selection.enabled on, which is off by default, and the exyliaprotections.select node, which everybody has by default. Turn it on in config.yml or from /protectionsadmin settings general. If it shows but answers "Protecting land by selection is not available.", one of the two changed since the menu opened. See Creating protections.

"You need … for that." although the player has the money#

Every price goes through ExyliaLib's economy. With no economy installed (ExyliaEconomy, Vault with an economy behind it, or PlayerPoints) every price above 0 is refused. A tier's or the selector's currency must also exist; blank uses the default one. To hand out cores without an economy, use /protectionsadmin give <player> <tier> [amount]. See Economy.

A core cannot be placed#

The core stays in the hand and the chat says why. The usual causes are the player's limit, another protection too close or overlapping, a disabled world, or a missing permission. See Creating protections.

Every refusal and its cause
MessageCause
Protection cores are turned off on this server.cores.enabled is off.
Land cannot be protected in this world.The world is in settings.disabled-worlds, world_the_end by default.
You already own n protection(s), your limit.The player's limit, counted on every server.
You already own n of this tier.The player's exyliaprotections.limit.<tier>.<n>, or the tier's own limit.
You already own n protection(s) in this world.settings.world-limits for this world.
That land overlaps another protection.Another owner's protection on this server. The player's own may overlap.
Keep at least n blocks from other players' protections.settings.min-distance, 8 by default, whatever heights both cover. The player's own protections may touch.
That land reaches past the world border.Part of the land lies outside the world border.
That land overlaps a protected server area.A WorldGuard region other than this plugin's own, the global region and settings.allowed-world-guard-regions.
You cannot use this protection tier.The tier names a permission the player lacks.
Your rank does not include that feature.The player lacks that feature's exyliaprotections.* node. See Permissions.

How do I let players own more protections?#

Grant exyliaprotections.limit.<n>, such as exyliaprotections.limit.10. The highest one a player holds is their limit; without one it is settings.default-limit, 3. exyliaprotections.limit.0 is a limit of zero, not a fallback. See Permissions.

The overview has only a few sections#

Economy, Growth and Extras appear only while one of their features is on, and Defense while raids or logs are. Raids, the bank, upkeep, the market, rent, plots, upgrades, warps, perks, time and weather and merging are all off after a fresh install. Turn them on with /protectionsadmin feature <name> on, from /protectionsadmin settings features, or in submodules followed by a reload. See Configuration.

I changed the roles in config.yml and old protections did not change#

A protection copies the roles section and its tier's flags when it is made, so editing them only changes protections made afterwards. Existing ones are edited from their People → Roles screen. See People and access.

A member cannot open chests#

A member can do what their role allows, plus any personal override. Open People → Roles, left-click their role and turn Containers on, or shift-click them in Members to give them alone access. See People and access.

How do I reload the plugin?#

Run /protectionsadmin reload (also /protections admin reload, or Reload in the admin hub): it reads config.yml, the messages and the menus again. /exylialib reload re-reads the menu files too. Edits under menus/admin/ never stick, because those screens are rewritten from the jar on every start. See Configuration.

Do I need WorldGuard?#

No. The default INTERNAL backend enforces everything itself. WorldGuard adds the WORLDGUARD backend, which mirrors each protection as a region other plugins can read and keeps new land off other WorldGuard regions, and it is needed for the ProtectionStones import. See Backends.

A protection made on another server is not protected here#

Each protection belongs to the server it was made on, and only that server enforces it. Other servers on the same database list it, count it towards limits and teleport members to it.

A protection made on one server does not show up on another#

Every server keeps the protections in memory. Without Redis in database.yml a server only learns of another server's changes when it restarts: turn Redis on in every server, with a different server-id on each. See Installation and the database page.

Can I bring over ProtectionStones regions?#

Yes, with /protectionsadmin import protectionstones, with WorldGuard installed. Run it with --dry-run first. See Migration.

/ps opens ProtectionStones#

Both plugins register /ps. Remove ProtectionStones once its regions are imported, or use /protections or /claims.

Something missing on this page? Tell us on Discord