Skip to main content
NxShards configuration is split across a few YAML files inside plugins/NxShards/. config.yml holds the database backend, transfer limits, wand material, and messages; shop.yml defines the GUI shop and its action-based purchase flow.

File Location

After editing config.yml, run /shards reload to apply changes without restarting the server.

Database

Choose between MySQL (multi-server sync) and SQLite (local storage):
SQLite stores data in plugins/NxShards/database.db. Use MySQL when you need a shared Shards balance across multiple servers.

Transfer Limits

Protect the economy by capping how many Shards a player can send through /shards pay:

Selection Wand

Customise the wand material and visual feedback used by /shards wand:

Shop

The GUI opened by /shards shop lives in a dedicated shop.yml file. Each item defines its icon, slot, and a list of actions that run sequentially when a player clicks it. The most common action is [shards] <amount> which charges the player; other actions execute console commands, send messages, play sounds, or show titles.

Available Actions

Messages

Every user-facing string is editable in the same file. Use legacy & colour codes:

AFK Zone Defaults

Set fallback values used when admins don’t supply an interval or amount on /shards zone create:

Reloading

Apply changes with:
This reloads the configuration, messages, and the in-memory AFK zone registry without disconnecting players.