-
Notifications
You must be signed in to change notification settings - Fork 13
8 Modules
MaksyKun edited this page Jul 25, 2026
·
2 revisions
Every module has a settings.yml file. Content is beside it when the module supports content files.
| Page | Module | Main content |
|---|---|---|
| Arrows | custom projectiles | items/ |
| Combat Log | combat messages and logging | settings only |
| Consumables | food and potions | items/ |
| Custom Items | static items | items/ |
| Dismantle | break items into results |
items/, source/
|
| Drops | mob drop tables |
mobs/, tables/
|
| Essences | essence socketing |
items/, merchant.yml
|
| Extractor | remove sockets | items/ |
| Fortify | fortification stones | items/ |
| Gems | gem socketing |
items/, merchant.yml
|
| Identify | reveal generated item stats |
items/, tomes/
|
| Item Generator | procedural items | items/ |
| Item Hints | hints and glow | settings only |
| Loot | loot containers | settings only |
| Magic Dust | improve socket rates | items/ |
| Money | money items | items/ |
| Party | party play | settings only |
| Sell | sell GUI | settings only |
| Refine | refine item stats | items/ |
| Repair | repair durability | items/ |
| Runes | rune socketing |
items/, merchant.yml
|
| Sets | set bonuses | items/ |
| Soulbound | binding and trading | settings only |
- Enable and configure one module at a time on staging.
- Back up the plugin data folder and representative player inventories before changing item IDs, drop tables, socket rules, or failure behavior.
- Verify dependencies and permission nodes from each module page.
- Use module reloads for isolated content changes; restart after engine, storage, compatibility, or module-loading changes.
- Test success, failure, full-inventory, disconnect, death, and restart behavior before production use.
The shared command and permission model is documented in 06 - Commands and Permissions.