Store refunds, community blocking, and date-based spin missions
Traders can request store refunds through an admin approval flow, block other members in community channels, and spin missions can now trigger on date fields.
01 ·Self-service store refunds with an approval flow
The store now handles refunds from request to settlement. Per category or product, admins set which order statuses are refundable, the status a refunded order moves to, and whether a refund needs approval. A trader opens an eligible order in Purchase History and submits a request, and the amount is always what they paid, with one request allowed per order. When approval is off, the refund goes through and the order moves to the refunded status. When approval is on, the request lands in Order History as Pending Refund Approval, where an admin approves it or rejects it with a reason. Each request holds the refund rules that applied at the moment it was submitted.
A store that sells rewards for coins needs a clean way to reverse a purchase without an admin adjusting balances directly. Refundable statuses and an optional approval step let store operators decide which orders can be returned and who signs off, and letting a trader start the request from their own Purchase History keeps the earn-and-spend reward loop straightforward on both sides of the counter.
02 ·Block another member in community channels
Members can block another member from the message actions in public and private community channels, next to Report. A block is one-directional and scoped to the community: the blocked member's messages are hidden for the person who set the block, while everyone else's view stays the same, and moderators are notified. Blocked members stay filtered as a channel loads more messages or updates live, and the block carries across the blocker's open tabs. Traders manage their own list under Blocked Users, and unblocking asks for confirmation. Community owners and users with moderation access get a User Blocks view that lists each block with its blocker, blocked member, reason, and status.
Giving members a way to hide someone they would rather not see keeps community channels comfortable to sit in without pulling a moderator into every disagreement. Because a block is directional and community-scoped, one member's choice never changes what anyone else reads, and the moderation view leaves owners a record to act on if a pattern shows up.
03 ·Spin missions that trigger on a date
Spin the Wheel missions can use date fields in their conditions, with two dynamic options that compare against the current day in the trader's timezone. Today's date (MM-DD) matches the month and day only, so a condition on a birthday field clears each year on that day. Today's date (YYYY-MM-DD) matches the full date including the year, for a one-time occasion such as a specific purchase date. The comparison re-checks each day as the date rolls over.
Date conditions let a broker tie a spin to a moment that belongs to each trader, like a birthday or an account anniversary, instead of one fixed calendar date for the whole community. Anchoring a reward to a trader's own dates gives the daily return-visit habit a personal reason to check back.
The leaderboard displays cleanly on mobile and iPad screens.
21 JulSearching user fields in the admin panel now returns existing custom fields.
21 JulA further round of custom widget fixes covering layout and responsiveness across embedded widgets.
21 JulContinued translation coverage across the leaderboard and store redemption conditions.
21 Jul