Configure AuraSkills progression and test player rewards

AuraSkills adds skills, stats and abilities. It was previously named Aurelium Skills, so older tutorials can refer to different names and configuration formats. Start with default progression on a small test account, then change rewards and world policies one at a time.

Prepare compatible files and storage

Check the current AuraSkills release against your Minecraft and server platform. Read migration notes if replacing an older Aurelium Skills or AuraSkills installation. Do not assume that renaming a directory converts its data. Use official download links and follow plugin installation.

Stop normally and keep a completed backup containing configuration, player progression, worlds and any external database. If another plugin awards money or items when a skill level changes, preserve that integration's data too. Keep the old JAR and matching configuration until the new build has passed a clean save and restart test.

Check experience and persistence

1. Start and read Console for loading or storage errors.
2. Join with an ordinary test account and run /skills to inspect the skills overview.
3. Use /sk sources mining to inspect the documented sources menu for that skill. Check the installed help if your language or release changes the presentation.
4. Perform a small, permitted activity in an enabled survival world. Record the skill's progress and compare it with the intended source.
5. Reconnect, then complete a normal stop/start cycle and confirm progress persists.

Do not use an administrator set-level or reset command as a first test of natural experience gain. Those commands intentionally alter progress and may trigger separate reward behaviour. Work with a disposable account so a test does not change an established player's progression.

Set world and experience policies

Review disabled_worlds in the generated main configuration and use the exact world names. The documentation notes that menus and commands can remain available even where gameplay progression is disabled, so seeing a menu does not prove a world should award experience.

Inspect block-replacement checking before changing mining behaviour. Allowing placed blocks to repeatedly grant experience can create a progression loop. Check spawner and other source multipliers deliberately, and compare permission-based bonuses with group membership. Keep player access narrow; administrator skill manipulation is not needed for normal progression.

Add one reward and test its boundaries

Use the version's reward format to configure a small reward at a known level. Check the recipient, amount, required integration and whether the action executes as console. If a reward has a reversal command, test both gaining and losing the level on an isolated copy before relying on it.

Run a full-inventory test for item rewards and inspect the documented claim-items route rather than assuming missing items were deleted. Do not repeatedly grant levels to investigate a reward without tracking whether it has already been delivered.

If a skill stops progressing, record the skill, world, source, permission context and log time. A display conflict can hide progress without changing storage. See group permissions. Further reading: commands, main configuration and rewards.

Looking for another plugin? Browse the Minecraft plugin guide directory.