Install ExyliaClasses
Dependencies, the files ExyliaClasses writes on first start, and how to update.
At the end of this page ExyliaClasses is running and the six default classes are ready to wear.
Before you start#
A Paper server on 1.21.1 or newer with Java 21. ExyliaLib is required; packetevents and PlaceholderAPI are optional.
Steps#
Drop in the jars
Put ExyliaClasses.jar, plus ExyliaLib and packetevents, into plugins/. PlaceholderAPI is optional and only needed if you want the placeholders outside Exylia plugins.
Start the server
It writes config.yml, a messages.yml per language under lang/ and the six class files under lang/<language>/classes/.
Put the armour on
Nothing else is needed. A full leather set makes a player an Archer after a five-second warmup.
Edit or add classes
Every class is a file. Change one, add one, delete one, then run /classesadmin reload.
Without ExyliaLib the plugin still loads, says where to get it in the console and stays off until it is installed. Without packetevents it runs normally and only its packet-drawn extras stay off.
Check that it works#
The console shows ExyliaClasses enabled with no error. In game, put on a full leather set: a countdown appears in chat, then "You are now ARCHER!". Run /classesadmin reload as an operator and every step reports on its own. If it does not, see Common problems.
Going further#
Follow Your first class, then Edit or add a class.
Updating. Replace the jar and restart. /classesadmin reload re-reads config.yml, messages.yml and every class file, and re-checks every online player's armour against the new definitions.
Loading. Every .yml file inside lang/<language>/classes/ is loaded, whatever it is called. The file name, lowercased, is the class id: Archer.yml is the class archer. A file that fails to parse is logged and skipped; the rest still load.
Requirements
| Requirement | Notes |
|---|---|
| Paper 1.21.1 or newer | Folia needs 1.21.4 or newer. |
| Java 21 | The jar is compiled for 21. |
| Paper, or Folia | It uses Paper's armour-change event, so Spigot alone is not enough. Folia is supported. |
| ExyliaLib | Configuration, text, effects, tasks, placeholders and the clan bridge. |
| packetevents | Optional. Only the packet-drawn extras need it. |
| PlaceholderAPI | Optional. Only for exposing the placeholders to other plugins. |
Files it writes
| File | Contents |
|---|---|
config.yml | The language, the debug flag and the two boss bars. |
lang/<language>/messages.yml | Every message the plugin sends, and the two bar titles. en, es, pt, fr, ru and tr ship. |
lang/<language>/classes/Archer.yml | The Archer, and the mark weapon. |
lang/<language>/classes/Bard.yml | The Bard, energy and the clan buffs. |
lang/<language>/classes/Miner.yml | The Miner and its below-Y passive. |
lang/<language>/classes/Rogue.yml | The Rogue and the backstab weapon. |
lang/<language>/classes/Sorcerer.yml | The Sorcerer and the enemy debuffs. |
lang/<language>/classes/Tank.yml | The Tank. |
There is no database. Nothing about a player is written to disk.
The six defaults are kept up to date, never overwritten. On every start and every /classesadmin reload the plugin checks those six files. One that is absent is written back: delete Bard.yml and it comes back; rename it and you get a new file next to your copy. A key a release adds is added to your file; a default a release changes on a key you never touched is offered in /exylialib updates rather than applied; anything you edited is left alone.
Something missing on this page? Tell us on Discord