Player Trading Safety

Use the protected trade flow

When SkaiaCraft provides a protected player-trade interface, use it instead of throwing valuables on the ground or splitting a deal across unclear manual transfers.

• Confirm the exact username before opening a trade.
• Read every item, quantity and currency amount before confirming.
• Do not accept renamed substitutes for protected currencies or high-value items.
• Wait for the completed trade state before moving away or starting another transaction.

Agree large deals clearly

Large item sales, building commissions and long-running services are easier to resolve when both sides agreed on the same outcome before payment moved.

• State the exact items, quantity, price and delivery expectation.
• For services, define what counts as finished work.
• Keep written terms in an appropriate forum or community channel when the value justifies it.
• Avoid vague promises such as 'I'll pay later' for high-value work unless you accept that risk.

Scams, mistakes and ordinary disputes

A deliberate attempt to deceive another player is different from buyer's remorse, a misunderstood price or a deal whose terms were never clear. Good evidence helps staff distinguish those situations.

• Do not retaliate by griefing, stealing or publicly targeting the other player.
• Keep screenshots or written terms that show what was actually agreed.
• Record the approximate time and exact players involved.
• Use the appropriate private report route for suspected scams.

High-value economy safety

• Treat Rare Item Tokens, spawners and scarce progression items as high-risk trades.
• Use current server menus to verify item identity and value where possible.
• Do not route a trade through extra accounts to bypass a limit or disguise ownership.
• If a protected trade duplicates, deletes or transfers the wrong item, stop repeating it and report the first abnormal result.

Why protected trading is safer than drop trading

Drop trading makes ownership changes difficult to prove and gives nearby players, despawn rules and inventory mistakes a chance to interfere. A protected trade flow can instead present both sides before value changes hands.

For ordinary item trades this reduces mistakes. For rare spawners, tokens or expensive services it also creates a much clearer record of what was intended.

• Use the supported trade interface where available.
• Do not introduce an unnecessary middleman.
• Check protected item identity rather than only visible names or lore.
• Finish one transaction completely before starting the next.

Building evidence for a genuine scam report

Useful evidence explains the agreement and the transaction without requiring staff to guess which part of a conversation mattered. Large deals are therefore safer when the item, price and expected delivery are written down before payment.

• Keep the exact usernames and approximate transaction time.
• Preserve the agreed item, amount or service outcome.
• Explain what was delivered and what was missing.
• Do not edit screenshots to remove context that changes the meaning of the agreement.
• Do not retaliate or move disputed items through other accounts.

Reducing ambiguity before value changes hands

Most avoidable trade disputes begin before confirmation, when the players have different assumptions about quantity, timing or what counts as finished work.

For higher-value trades, a short written agreement can be more useful than a long argument after the transaction.

• State the item or service precisely.
• State the exact quantity and currency amount.
• For services, define the completion condition.
• Use protected trade interfaces for the actual transfer where available.

Handling a disputed trade safely

• Preserve the agreement and transaction context before messages disappear or details are forgotten.
• Do not retaliate through griefing, theft or harassment.
• Do not move potentially duplicated or substituted high-value items through extra accounts.
• Report deliberate deception or a protected-trade fault privately with concise evidence.