Define the Trade as One Specific Transaction First
A checkable agreement identifies item names, quantity units, payments or exchanges, delivery, and both game identities. Say you exchange your confirmed materials for those the other person explicitly agrees to, then add actual quantities. 'I'll give you a stack' is not a complete transaction when units and item types differ; later memories alone cannot easily resolve it.
Separate Shop Interfaces From Player Trades
In available interfaces such as /shop or /sellgui, check buying versus selling, quantity selection, and current prices. Player negotiations follow explicit agreement. Server-shop prices do not determine every player's quote or guarantee every material can be sold. Read scope before an unfamiliar selling command to avoid disposing of items you want to keep.
Check the Scope of /sellall Especially Carefully
The original table describes /sellall as involving inventory, held, or specified items, without complete branches or configuration. It is not a risk-free button for one unwanted item, and its name does not identify exactly what this server sells. Read actual help, organize items to retain, and confirm scope before deciding. No unverified selling arguments are added here.
Two Checks Before Transferring
The list includes /pay and /balance. Check the recipient's full game identity and agreement, then amounts and arguments in current help or interfaces. Group notes do not replace game identifiers. Do not repeat payments immediately when disconnection leaves results unclear. Payment feedback and balance changes should be compared; refer discrepancies for investigation rather than repeated retries.
A Complete Example Without a Fixed Price
Suppose two people exchange stone for timber. One states exact types, quantities, and delivery location; the other confirms the same understanding. Each prepares their own materials. Afterward, both confirm receipt and any undelivered part. No currency or universal price is assumed. The example makes the beginning, delivery, and conclusion understandable to both sides.
What to Keep After a Mistake
Keep agreement messages, actual recipients, times, interface feedback, and checkable balance records. Add locations and quantities for items, recipient identifiers for payments. Pause further trades when errors seem suspicious rather than publicly insult other players with similar names. Available records and corrective capabilities depend on actual conditions; an economy plugin does not guarantee full recovery.