Installation

AtlasSpawner runs on Paper or Folia, Minecraft 1.21.4 up to 26.2, on Java 21.

1. Download the jar

Download AtlasSpawner-<version>.jar for the build you want.

2. Drop it into /plugins

Copy the jar into your server’s plugins/ folder. No other file is needed — database drivers are fetched automatically the first time the plugin starts (see Database drivers are fetched automatically below).

3. Start the server

On first start, AtlasSpawner writes its default config.yml, messages.yml, spawners.yml, boosters.yml, database.yml and menus/*.yml into its own data folder. It also creates a shared plugins/AtlasLoader/ folder — used by every Oreades plugin on this server — with a template licence file, atlasspawner.yml, inside it. At this point the plugin disables itself with a message telling you to paste a licence key.

4. Activate your licence

Open plugins/AtlasLoader/atlasspawner.yml and paste your licence key into the license field, then restart the server:

plugins/AtlasLoader/atlasspawner.yml

license: ""
version: latest
channel: stable

license is the key you were given — the plugin stays disabled while it is empty. version and channel pick which build the server pulls; leave them at latest and stable unless you have a reason not to.

See Licensing & activation for the full contract, including the hardware id, channels, and troubleshooting.

5. First configuration pass

With the plugin running, look at:

• config.yml — settings: whitelist limits, selling, integrations, the engine, ownership limits, upgrades, boosters, and which currency pays for what. See config.yml.
• spawners.yml — the spawner types themselves: their drops, experience, upgrade axes, and prices. See spawners.yml.
• database.yml — SQLite by default, which needs no setup. Switch to MySQL or MariaDB only if you want several servers to share one database. See database.yml.

Database drivers are fetched automatically

AtlasSpawner ships with no bundled JDBC driver. Its Paper loader downloads HikariCP and exactly one database driver — SQLite or MariaDB, whichever database.yml’s storage.type asks for — from Maven Central and the Paper repository the first time the server starts. An unreadable database.yml is treated as SQLite. The server needs outbound internet access for this step.