XenoTokensXenoTokens
Supported Plugins
Review the integrations that matter around XenoTokens and its multi-currency shop flow.
XenoTokens can power a server on its own, but its real value grows when you connect it to placeholders, permissions, and reward ecosystems.
Main integrations
| Plugin | Purpose | When it matters |
|---|---|---|
| PlaceholderAPI | Publishes %xtk_*% values, including currency-prefixed placeholders | when you want to display balances, ranges, or transaction data outside the plugin |
| Vault or VaultUnlocked | Exposes XenoTokens as an economy source to the rest of the server | when another plugin expects a Vault-compatible provider |
| LuckPerms or another permission manager | Keeps xenotokens.command.* nodes manageable across staff and donor groups | on almost any production server |
Reward and display ecosystem
| Plugin type | Why it helps |
|---|---|
| Scoreboard, chat, and hologram plugins | They can show %xtk_balance_formatted%, %xtk_token_range%, or currency-prefixed values like %xtk_main_balance%. |
Custom item plugins (ItemsAdder, Oraxen, etc.) | XenoTokens does not hard-hook them, but shop rewards can call their commands through console-commands or player-commands. |
| Admin dashboards or DB clients | Helpful when you run several currencies and want to inspect balances and transaction history directly. |
Internal systems used by XenoTokens
- A per-currency event engine powers
events.yml. - A GUI shop loader powers
currencies/<id>/gui.yml. - Currency aliases are resolved from the currency ID, configured name, and display name.
Indirect integrations count too
XenoTokens often integrates with third-party plugins through shop reward commands instead of explicit hard hooks. That still makes those plugins part of your deployment plan.
Getting Started
First steps for understanding XenoTokens, its currency folders, and its shop-ready economy model.
Frequently Asked Questions
Common XenoTokens questions about currencies, placeholders, shops, and operator workflows.
Last updated on