Install NoxBoosters
Este conteúdo não está disponível em sua língua ainda.
This guide targets NoxBoosters 0.1.0, source aeea4cd. The plugin is compiled for Java 21 against Paper 1.21.4. The API module’s Java 17 target does not make the server plugin Java 17 compatible.
Requirements
Section titled “Requirements”| Component | Requirement |
|---|---|
| Server | Paper 1.21.4 is the reviewed build target; verify your exact server version before use. |
| Java | Java 21 bytecode support. |
| Required plugins | NoxCore, LuckPerms, SuperiorSkyblock2. All three are declared hard dependencies. |
| Storage | A reachable MariaDB database and an account able to create and update its plugin tables. |
| Consuming plugins | Required for useful boost keys; for example the reviewed NoxHoes, NoxPickaxes, or NoxGens integration. |
| Optional plugin | PlaceholderAPI, for the placeholders in the integration reference. |
The plugin descriptor declares HikariCP and the MariaDB JDBC driver as server-loaded libraries. Allow the server to resolve those dependencies.
Install and configure
Section titled “Install and configure”- Back up the server’s existing plugin data and database before replacing an installed build.
- Install the required plugins and put
NoxBoosters-0.1.0.jarinplugins/. The plugin JAR includes its API; the separate API JAR belongs in developer dependencies. - Start the server once to create
plugins/NoxBoosters/. If the default database connection fails, NoxBoosters disables itself; the configuration files are still created. - Stop the server and set your MariaDB connection in
plugins/NoxBoosters/config.yml. This example uses a dedicated account; replace its credentials:
database: host: 127.0.0.1 port: 3306 name: noxboosters user: noxboosters password: 'replace-with-your-password' pool-size: 4- Start the server again. NoxBoosters creates its tables. Wait for
Booster storage readyin the log before activating boosters. - Run
/nbadmin keyswith admin permission. Only keys registered by enabled consumers appear. ResolveUnknown keymessages before using the corresponding examples.
Database connection changes require a server restart. /nbadmin reload does not reconnect the connection pool.
Check your first personal booster
Section titled “Check your first personal booster”With NoxHoes loaded and hoes.money registered, run:
/nbadmin give Steve player farm_money_2x_30m/nbadmin inspect Steve hoes.moneySteve must be online and have an empty inventory slot. Right-click the issued item in the main hand, then inspect again. With the supplied defaults and no other modifiers, the central multiplier becomes ×2 for 30 minutes of real time. The consuming plugin determines the actual payment.
Open /boosters to inspect the value, then test a real reward through the consuming plugin on your test server. A correct displayed multiplier does not by itself verify the final payout.
Storage and recovery
Section titled “Storage and recovery”Real-time boosters keep expiring while players or the server are offline. Personal ONLINE_TIME boosters pause on quit and clean shutdown; online progress is checkpointed every 30 seconds at normal tick rate. A hard crash can restore time since the last successful save.
Failed or rejected item activations use the local refunds.properties queue. Delivery is retried on player load or /boosters; an offline player, full inventory, or missing booster type can keep an item queued. Reused serials are rejected and consumed. Back up the plugin data folder along with the database.