Wiki Release: 2026.09.8 · UltimateClans: 9.1.4 · Documentation branch: 9 · Levelup

Levelup#

Levelup adds clan level progression using points, requirements, patents/titles, configured costs and level actions. The pages in this section explain what players see in-game, what administrators need to configure, the normal setup flow, and the most common problems you may need to diagnose.

Compatibility#

Component version: 1.2
Documentation release: 2026.09.8
Minimum UltimateClans version: 9.0.0

What you can do with it#

Define level thresholds, requirements and actions in the level configuration
Earn/add clan points through supported gameplay/admin flows and verify the next level requirements
Trigger a level up and confirm actions/rewards/patent changes

How it works#

Level progression#

Levelup converts clan activity into points and level requirements. The configuration defines the points formula/base/exponent, level range, action point changes and per-level requirements/rewards. Actions such as clan creation, member changes, wars, ally/rival changes, kills/deaths and verification can add or remove progression points when configured.

Before enabling automatic progression, calculate a few sample levels from your formula and confirm the required points/rewards match the pace you want.

First setup#

Before enabling the feature for players, review these installed files:

commands.yml
config.yml
gui.yml
language/Lang_EN.yml
language/Lang_ES.yml

Recommended in-game workflow#

Define level thresholds, requirements and actions in the level configuration.
Earn/add clan points through supported gameplay/admin flows and verify the next level requirements.
Trigger a level up and confirm actions/rewards/patent changes.

This feature is mainly automatic or accessed through the parent plugin/GUI, so it does not need a large standalone command tree.

GUI areas#

The installed GUI configuration contains screens/sections such as:

General.levelup_home
General.levelup_confirm

What administrators should configure#

Keep thresholds ordered and test every transition around boundary values.
Do not rename live level identifiers without checking stored clan level data.

Configuration map#

config.yml — Config (date_format_short, Levelup, Permissions); Level (points, patent, actions, requeriments)

The Configuration page lists the available paths and defaults from the installed configuration, with notes on what each area controls.

Before going live#

Back up the component data/configuration.
Start the server and confirm the component is detected without startup errors.
Test with a non-OP player and the lowest clan role that should have access.
Exercise the complete flow once, including the failure/deny path, not only the happy path.
Restart the server and verify that persistent state survives.
If the network is multiserver, repeat the test from a second node and verify storage/synchronization.

Troubleshooting quick reference#

Symptom	Likely cause	What to check
Clan has enough points but does not level	Additional requirement/cost is unmet or auto progression is not enabled	Inspect all requirements for the next level, not only points.
Level action does not run	Action syntax/command is invalid	Execute the intended command manually and inspect level-up log.
Placeholder shows old level	Clan data/cache has not refreshed	Force the supported update/reload and verify storage value.

For a longer diagnostic flow, open the Troubleshooting page for this component.