🧾v3.3.0 Preview: Transaction history and offline payment notifications
A player reports a missing payment. Where do you start? CoinSystem v3.3.0 adds a readable transaction history for your server and payment notifications for players returning from offline.
"I sent the coins, but they never arrived."
If you run a Minecraft server, that's the kind of report where a player's current balance only tells half the story. The v3.3.0 beta gives you more to work with: a record of balance changes you can actually follow, plus notifications for payments received while a player was away.
🧾 Follow the coins in ledger.log
CoinSystem records player payments, Vault transactions, API operations, admin adjustments, and more in a shared transaction ledger. You'll find a readable copy at plugins/CoinSystem/logs/ledger.log.
Here's a real payment entry from ledger.log:
[2026-08-13 22:53:40] TX-20260813-OO9FVQ PAY COMPLETED PLAYER:bevos -> PLAYER:Jens98 amount=500
That single line tells you:
| Part | What it means |
|---|---|
2026-08-13 22:53:40 |
When the payment happened. |
TX-20260813-OO9FVQ |
The unique ID for this transaction. |
PAY |
This was a player payment. |
COMPLETED |
The transaction completed successfully. |
PLAYER:bevos -> PLAYER:Jens98 |
Who sent the coins and who received them. |
amount=500 |
The amount transferred: 500 coins. |
Now you have a specific payment to investigate when a player opens a support ticket. Search the log for their name or a transaction ID to find the relevant entries.
It also covers coins moved into and out of items. These two entries show Jens98 withdrawing 4,000 coins as an item and redeeming 4,000 coins 16 seconds later:
[2026-08-26 19:33:55] TX-20260826-48H716 WITHDRAW_ITEM COMPLETED PLAYER:Jens98 -> ITEM amount=4000
[2026-08-26 19:34:11] TX-20260826-48H717 DEPOSIT_ITEM COMPLETED ITEM -> PLAYER:Jens98 amount=4000
The first entry records coins leaving the wallet for an item; the second records coins returning from an item to the wallet. You can see these movements alongside ordinary payments when investigating a balance change.
For custom admin tools: the same history is available through the API. Eligible transactions can also be reversed by ID using CoinApi.rollbackTransaction(txId). The original database entry is marked as rolled back, and a separate rollback entry links back to it. A transaction can only be reversed once; if the recipient can no longer cover the amount, no funds move. Direct balance assignments and resets aren't eligible.
📬 See who paid you while you were offline
If someone sends you coins while you're offline, the payment is credited immediately. CoinSystem saves the notification and shows it when you next join, so you can see who paid you and how much you received.
Pending notifications survive server restarts and appear in the order the payments arrived. On a server network, a notification delivered while you're online on another server won't appear again on your next login.
Getting started: both features are enabled by default. CoinSystem creates the required SQLite or MySQL tables automatically, and you can read ledger.log directly from your server's plugin folder. No extra log viewer or custom integration is needed to inspect the file.
These features are part of the v3.3.0 beta ahead of the final release.