Hub.DenizenMCInstallation
Requirements, and getting EliteSpawner running on your server for the first time.
This page covers what EliteSpawner needs and walks through a first install. It takes a couple of minutes, and the default configuration is usable as soon as the server starts.
Requirements
No required dependencies
Everything listed under Integrations is optional. EliteSpawner runs standalone, with its own price list for selling and its own ownership protection.
Installing
Download the jar
Download the latest release from the store you purchased it on. Use the newest version unless a changelog tells you otherwise.
Add it to your server
Stop the server, place EliteSpawner-<version>.jar in the plugins folder, and start the server again.
Don't use /reload
Always do a full restart when adding or updating a plugin jar. Reloading plugin jars with /reload or a plugin manager isn't supported.
Check the generated files
On first start, EliteSpawner creates its folder with default configuration:
Each file is described on Configuration files.
Give yourself a spawner
Run the give command with any type defined in mob_spawners.yml to confirm everything works:
/esp give <your-name> mob <type>Tab completion lists every type defined in mob_spawners.yml, so you don't need to look them up.
Adjust and reload
Edit the configuration to fit your server, then apply the changes without a restart:
/esp reloadUpdating
Back up before updating
EliteSpawner is pre-1.0, so the configuration or database layout can change between releases. Read the changelog on the store page and keep a copy of plugins/EliteSpawner before updating a live server.
Missing configuration or language keys introduced by an update are appended to your existing files automatically, and a backup is made first. Your own changes are kept.
Last updated on