Content generated with AI — it may contain mistakes.

ExyliaPracticeCore/Getting startedUpdated in v1.4.0

Installation

Put ExyliaPracticeCore on a Paper or Folia server, set the lobby spawn, and see which files it generates and which of them you can edit.

Page 2 of 354 min read

This page puts ExyliaPracticeCore on your server and sets the lobby spawn. It takes about five minutes. Nothing is playable afterwards: there is no arena and no kit yet, which Play your first match covers.

Before you start#

RequirementDetail
ServerPaper 1.21.1 or newer, or Folia 1.21.4 or newer
Java21
RequiredExyliaLib, FastAsyncWorldEdit, packetevents
OptionalPlaceholderAPI, ViaVersion, Worlds, Apollo, FeatherServerAPI, floodgate

Configure the database in ExyliaLib first: the plugin reads its arenas, kits, seasons and settings from it. See the ExyliaLib database docs. The 18 tables are created for you and are listed in Database.

FastAsyncWorldEdit and packetevents are hard dependencies

Both are listed under depend, so the server refuses to load the plugin without either. Cloning an arena is a schematic paste and regenerating one is a schematic restore; neither has a fallback. ExyliaLib sits under softdepend only so the loader orders the plugins correctly. In practice it is required too.

Install it#

Drop in the dependencies

Put ExyliaLib, FastAsyncWorldEdit and packetevents in plugins/. ExyliaLib must be the one copy every Exylia plugin sees: never shade it into another jar and never run two.

Drop in the jar

Put ExyliaPracticeCore in plugins/ and restart. The plugin ships through the Lukittu loader, so the file you install is the loader jar. Bought on BuiltByBit, the licence is embedded in that jar: there is no key to enter.

Let it generate

The first boot writes the files listed below and prepares the clone world. Check the console for the plugin enabling without errors.

Give yourself the admin node

exyliapractice.admin is the only node an operator needs. With it, /epc opens the admin menu.

Set the lobby spawn

Stand where players should arrive, run /epc and press Set lobby spawn. Until it is set, sending a player to the lobby does nothing and they stay wherever they logged in.

Check that it works#

  • The console shows ExyliaPracticeCore enabled and no missing-dependency error.
  • /epc opens the admin menu for you.
  • Joining the server puts you at the lobby spawn with the lobby hotbar in your inventory.

If the server refuses to load the plugin, one of the three required plugins is missing or failed to load. See Common problems.

What gets generated#

PathWhat it is
config.ymlEvery setting: language, arenas, queue, ELO, party, duel, lobby, jumpads, web API, chat, borders, replays. Reference
ranks.ymlThe nine ranks, their divisions and their K-factors. Reference
lang/<language>/messages.yml33 sections of player-facing text, titles, action bars and boss bars included
lang/<language>/scoreboards.yml20 sidebars. Reference
lang/<language>/items/lobby.ymlThe lobby hotbar
lang/<language>/items/party.ymlThe hotbar while in a party
lang/<language>/items/queue.ymlThe hotbar while queued
lang/<language>/overlays/replay.ymlThe hotbar a replay viewer drives the playback from
lang/<language>/menus/admin/**34 admin screens
lang/<language>/menus/player/**31 player screens
screens/practice_hub.html, screens/theme.cssThe HTML and styles of the practice_hub screen menu
lang/<language>/screens/practice_hub.ymlThe text of that screen

<language> is what language in config.yml resolves to. English, Spanish, Portuguese, French, Russian and Turkish ship complete; see Configuration. The screens/ files only matter when ui.menu-style is set to SCREEN.

Which files you can edit

config.yml, messages.yml and scoreboards.yml are generated from typed records and keep your values. The admin screens are rewritten from the jar on every start, so a screen added or changed in a release always reaches the server: do not edit them. The player screens, the hotbar items and the replay controls are yours: a file you have not touched is updated, one you edited is kept and the new version is offered next to it.

Going further#

The clone world

Clones are pasted into ExyliaLib's shared temporary world, exylialib_temporary: void, no structures, no mobs, no weather, frozen at noon, no random ticks and no autosave. It is created the first time a clone is needed, every plugin that pastes arena copies shares it, and its folder is deleted when ExyliaLib starts and again when it stops. It holds nothing worth keeping: every clone is re-pasted from the arena's schematic on demand.

On Folia the world comes from the Worlds plugin

Folia cannot create a world through WorldCreator, so the library asks Worlds instead. Without it there is no temporary world: no arena can be cloned, and a match that finds every copy of its arena busy sends its players back to the lobby. Install Worlds on Folia.

Upgrading from a pre-season database

On the very first boot with an existing pre-season database, a one-shot migration copies every row of practice_player_stats into season 1 and into the lifetime tier. It runs in the background, is resumable, and only ever reads the legacy table.

Something missing on this page? Tell us on Discord