Trace an unexpected EssentialsX command charge
An action can cost money through EssentialsX command-costs, a shop menu or another plugin. Identify which component charges the player before changing the economy provider.
Before you start
EssentialsX economy settings affect player money and the plugins that use its economy service. Keep player UUIDs, the active provider and the exact EssentialsX build in your change record. Use a normal test account rather than an operator.
Work through the check
- Record the exact command or clicked menu action and the player balance before using it once.
- Inspect the EssentialsX command-costs section and compare the command name with the installed release’s format.
- Check the account’s effective permission for cost exemptions, then repeat with a normal test user and a staff test role.
- Review wrapper menus or scripted commands for a second charge and compare the total deducted amount with each configured cost.
What to compare
Check whether the player repeated the charged command or whether an alias invokes another command. Keep one command attempt per test so the total debit can be matched to a single action.
Confirm the result
One allowed action should produce only the intended charge. An exempt role should behave according to the documented permission without needing operator access.
If the result differs
If the debit occurs only through a menu, its action list may contain a separate payment. If the command fails but still charges, inspect that plugin’s failure handling before changing prices.
Recover safely
Revert the single command-cost entry or menu action you changed and refund only the reproduced excess. Preserve the original permission state; a blanket exemption can hide rather than solve duplicate charging.
Documentation and related help
Check the EssentialsX Economy maintainer documentation and EssentialsX Economy maintainer reference against your installed release before applying changes.