Market moderation
Player reports, listings hidden for review, and what staff can remove, restore, ban, refund and pay out.
Players report listings; enough open reports hide one until a moderator looks at it. Staff with
uxmbuilders.admin.market decide from two menus or from commands: remove a listing, take back what it
sold, put it back, ban a seller from the market, refund a buyer or pay a seller by hand.
Reports
A player with uxmbuilders.market.report reports a listing with /builders market report <code> <reason> [note], or with the Report button of the listing's menu, which is not shown on their own
listing. The reasons:
| Reason | Typed as |
|---|---|
| Copied build | copied_build |
| Offensive content | offensive_content |
| Misleading | misleading |
| Spam | spam |
| Other | other |
A dash works in place of the underscore, and the note is the rest of the line, cut to
reports.noteMax characters. The command without a reason, or with one it does not know, prints its
usage and the reasons.
The Report button asks for the reason and an optional note on one screen: a dialog on Java, or a
Bedrock form with the reason as a dropdown. Where neither can be shown, chat lists the reasons with
numbers and takes a number, the reason as typed in the command, or its name as listed; then the note,
- for none. The note is not asked with reports.noteMax: 0, and cancel stops. Both ways file the
same report, with the same checks:
| Refused when | Setting |
|---|---|
| It is your own listing | |
| You reported this listing before | Once per player and listing, ever |
| Your last report was too recent | cooldowns.reportSeconds |
You made reports.dailyLimit reports in the last 24 hours | 0 is no limit |
You have played less than reports.minPlaytimeMinutes | The server's own playtime statistic; 0 lets anyone report |
Staff online on that server with uxmbuilders.market.notify are told at once, with an [Inspect]
link. The REPORTED post goes to moderationUrl in webhooks.yml when
one is set, so the reporter's name stays out of the players' channel.
Under review
The report that brings a listing's open reports to reports.autoHideThreshold hides it: it leaves the
market, nobody can buy it, and only its seller still sees it, marked Under review. The seller cannot
put it back on sale. A report only ever hides; what happens next is a moderator's decision. 0 turns
hiding off.
Closing a report, dismissed or acted on, takes it off the count, so a single new report after a dismissal does not hide the listing again. Closing reports never shows a hidden listing again: it stays under review until it is restored, which starts the count again from nothing.
The menus
/builders admin market reports [page] lists the reported listings, the one waiting longest first.
Clicking one opens its inspection, also reached with /builders admin market inspect <code>:
| Button | Does |
|---|---|
| Seller | Their earnings owed and held, and their market ban |
| Reports | The reports, open and closed, with reason and note |
| Licences | Prints the active licences in chat, each with a refund link |
| Teleport | To where the design was captured, above the build |
| Restore | Shown while the listing is hidden or removed |
| Dismiss the reports | Closes every open report and takes them off the count; the listing stays as it is, hidden or not |
| Remove | Asks for a reason, which the seller reads |
| Remove and revoke (shift-click) | Also takes back every licence |
| Ban the seller (shift-click) | Asks for a reason; the ban lasts until it is lifted |
| Lift the ban | Shown while the seller is banned |
Commands
| Command | Does |
|---|---|
/builders admin market remove <code> [--revoke] [reason] | Takes the listing down; --revoke also takes back every licence |
/builders admin market restore <code> | Puts it back |
/builders admin market reports [page] | The reports menu |
/builders admin market resolve <report> dismiss|action | Closes one report, by the id the reports list shows, and takes it off the listing's count |
/builders admin market inspect <code> | The inspection |
/builders admin market tp <code> | Teleports to where it was captured |
/builders admin market ban <player> [duration] [reason] | Bans a seller; a duration is 30m, 12h, 7d or 2w, none or never for good |
/builders admin market unban <player> | Lifts the ban |
/builders admin market refund <purchase> [--revoke] | Takes back one licence |
/builders admin market payout <player> | Pays what the market owes a player now |
Every action works from the console except tp; reports and inspect print to chat there. A player
is found by name if they have played on the server, online or not.
Removing and revoking
A removal closes the listing's open reports as acted on, frees the design to be listed again, and tells
the seller why, now or when they next join. The REMOVED webhook post names the moderator and the
reason.
Without --revoke buyers keep their licences: they paid, and the stored design does not change. With
it, each licence is taken back on its own:
| Step | What happens |
|---|---|
| The licence | Closed: it starts no new build, while a build already running carries on |
| The seller | Charged the net back through their earnings. Already paid, they owe it, and their next earnings pay it off first |
| The commission account | Charged its commission back, when it received one for that sale |
| The buyer | Refunded the price with moderation.revokeRefund: FULL; with NONE the licence is taken without a refund |
revokeRefund: NONE does not let the seller keep the money: they are still charged back what those
sales earned them, and the commission account its commission. The buyer gets nothing either, so the
server keeps that money.
refund <purchase> does the same for one licence and always refunds the buyer; refund <purchase> --revoke refunds only as revokeRefund says. The purchase id is the one the Licences links fill
in. A refund the economy refuses is written to the audit log for staff to pay by hand. A limited copy
taken back is not put on sale again.
Restoring
A restore puts a hidden or removed listing back in the status it left, sold out if every copy went meanwhile, dismisses its open reports, and tells the seller. It is refused as a duplicate when another listing took the same design in the meantime. Licences a revoke took back stay taken back.
Bans
A market ban stops a player from capturing and listing. In the same moment:
market.yml | |
|---|---|
| What the market owes them is put on hold, as are sales made during the ban | moderation.holdEarningsOfBanned |
Their listings are hidden (HIDE) or removed (REMOVE) | moderation.onSellerBan |
Buyers keep what they bought. Banning again replaces the earlier ban. unban releases the held earnings
to be paid; the listings stay hidden until a moderator restores each one.
When a timed ban runs out, the player may sell again at once. The ban is lifted, as unban would, at
their next payout: their own claim or Earnings button, the payout when they join, the retry every
minute while they are online with economy.payout: INSTANT, or a moderator's payout. That releases
the earnings it held, which are paid with the rest. payout refuses while a ban runs. Either way the
listings the ban hid stay hidden until a moderator restores them.
A player banned from the server is treated as blocked whatever the market says: their listings are left out of the market, cannot be bought, and they are not paid until the server ban ends.
Notes
- Moderators act without the player checks: no cooldowns, limits or fees. Every decision is written to
the audit table when
logging.auditis on. - The seller and buyers a decision touches hear of it live, or from their mail when they next join.
- What a moderator types as a reason is shown to players as plain text.
Related: Player market, Selling a build, Permissions
Was this page helpful?