NoxBoosters integrations and placeholders
Esta página aún no está disponible en tu idioma.
The central service below is NoxBoosters 0.1.0, source aeea4cd. A boost only changes gameplay when another plugin reads and applies its key.
Reviewed consumers
Section titled “Reviewed consumers”| Consumer / reviewed source | Registered key | Payment paths found in source |
|---|---|---|
NoxHoes 5637a9a | hoes.money | Harvest sale bonuses, inventory AutoSell, and MONEY rewards. |
NoxPickaxes 5a96bf3 | pickaxe.money | Inventory AutoSell and MONEY rewards. |
NoxGens 8386416 | gens.sell_price | Inventory selling, sell wands, stored-drop sales, pickup/upgrade settlement, and AutoSell. |
NoxGens manual paths use the seller’s value; AutoSell uses the gen owner’s UUID. Its sale total includes the boost when items are taken, and a deferred Vault deposit retries that stored amount without applying the multiplier again. An offline owner receives the central global/event value, without personal, rank, island, or pet sources.
The consumer’s own dependencies and economy provider must also be available. These are source-reviewed paths at the listed commits, not certification of every installed build or server configuration.
No reviewed consumer registers hoes.essence_chance. A commented cap or a pet config entry with that name does not enable essence chance. Other keys, including farming-yield effects, require a consumer that actually registers and applies them.
LuckPerms rank bonuses
Section titled “LuckPerms rank bonuses”Set metadata on the user or group using noxboost.<registered-key>. Example with an existing vip group:
/lp group vip meta set noxboost.hoes.money 0.10The effective meta value is a nonnegative ADD_PERCENT bonus. This example requests +10% for hoes.money; source and final caps still apply. NoxBoosters reads LuckPerms’ effective metadata, rather than summing every group entry itself, and refreshes online users after LuckPerms user-data recalculation.
Pet and custom sources
Section titled “Pet and custom sources”The reviewed NoxPets source f693f20 sums configured modifiers from equipped pets and writes them as ADD_PERCENT under source ID pets. Unknown keys are logged and skipped. Its bonuses still need a registered consumer key and are subject to the pets source’s default additive cap of 1.0.
Developers can register consumer keys and contribute a named source through BoostService, obtained from Bukkit Services. Registration and source changes run on the server thread. setSource replaces that producer’s complete key map; the producer owns cleanup and refresh. Personal producer state is discarded when a player quits. Use a unique source ID instead of a built-in one.
PlaceholderAPI
Section titled “PlaceholderAPI”Install and enable PlaceholderAPI before NoxBoosters starts. The expansion identifier is noxboosters.
| Placeholder | Value |
|---|---|
%noxboosters_multiplier_hoes.money% | A registered MULTIPLIER key’s value, such as 2.00; no × suffix. |
%noxboosters_global_count% | The number of active global booster rows; scheduled events are not included. |
%noxboosters_personal_time_farm_money_2x_30m% | An online player’s remaining personal time in whole seconds, rounded up; 0 when absent or offline. |
%noxboosters_chance_<registered_key>% | A registered CHANCE key’s value as a fraction, such as 0.05 for 5%. Replace <registered_key> with a real key. |
An unknown key or a key of the wrong type returns no expansion value (null), not a working effect. Chance display in /boosters is a percentage, while the placeholder is a 0..1 fraction. The personal-time placeholder reads online session data; an offline 0 does not mean a paused booster was deleted from storage. After enabling a new consumer at runtime, run /nbadmin reload to validate its configuration references again.
What has been verified
Section titled “What has been verified”This reference comes from source and shipped configuration at pinned commits. NoxBoosters’ testing record reports earlier automated and server smoke checks, and lists further gameplay, island, failure-recovery, and load checks before release. Those server checks were not rerun for this wiki update. Test final payments and behavior with your exact plugin builds before publishing compatibility claims.