config.yml
kits:
max-slots: 9
| Key | Type | Default | |
|---|---|---|---|
kits.max-slots | integer | 9 | Kit slots per player, 1 to 99. A value outside that range is , not rejected. |
Changing
kits.max-slots needs a full server restart. A does not register the new commands.What changes when you raise it
| Above nine slots | Effect |
|---|---|
The /kit menu | Splits into pages with next and previous buttons |
| Commands | /k10 to /k<max> and /ec10 to /ec<max> register at startup |
/k12
/perplayerkit:k12 # the same command, no ambiguity
Before you change it
| Lowering the value | Hides kits, does not delete them. A kit in slot 15 stays in the database and returns when you raise kits.max-slots. /purgeitem always scans all 99 slots, so a banned item cannot hide in a disabled slot |
| Servers on one database | All need the same kits.max-slots. A kit in slot 12 does not exist on a server that allows 9 |
| Stored data | Each slot is one saved inventory: 99 slots is up to 198 per player. Watch this on SQLite or YAML with many players |