Rewatch any draw, and run fixtures from your own system
Ended raffle draws replay for anyone, Match Predictions run over the public API, milestone widgets gain tile and tab layouts, and custom teams can be retired.
01 ·Raffle draws you can rewatch
An ended raffle opens its draw replay when the card is clicked, and a trader can watch it as many times as they like. The replay reads the stored draw result, so nothing about the raffle, its tickets or its winners moves while it plays. From any active raffle, a Previous draws control beside How to Play lists past draws across the whole community with their run timeframe and draw time, and any of them replays on the spot. There is no participant-only gate, so someone who never bought a ticket can still watch. Closing or skipping returns to wherever the replay was opened from.
A draw is the moment the programme is most worth watching, and it was previously visible only to whoever happened to be present. An archive open to everyone turns each draw into something a broker can point newcomers at, which is cheap proof that prizes get given out.
02 ·Match Predictions over the public API
Match Predictions can be run from the public API, and not only from the admin screens. An integration creates, retrieves, updates, publishes, settles, voids and bulk-updates fixtures, reads back winners and every participant with their prediction and payout, and updates up to a hundred matches in one request. The API key alone decides which community a call touches. Create, settle and void take an idempotency key, so repeating the same request returns the original answer and never a second match or a second settlement. An update carries the version last read, which stops an API write from overwriting an admin edit.
Settlement answers straight away with a settling state and reports progress while it runs, so an integration reads the result back once it finishes. Every documented failure returns a stable machine-readable code.
A broker running fixtures around real sport keeps the schedule in another system. Driving the match from that system keeps the two in step, and the idempotency key is what makes a retry safe when the network was the problem and not the request.
03 ·Milestone widget settings, rebuilt
The milestone widget's display settings are reorganised around what they configure: the group, the stage, its conditions, its rewards and the progress card. Groups and stages gain a Tile layout alongside horizontal and vertical, each with its own maximum per row from one to six, defaulting to three. Stage conditions can be shown as tabs as well as in full or in a dropdown. The progress stepper takes a pixel size between 24 and 56, and older small, medium and large values resolve without a migration. Leaving every checkbox in a section unticked hides that section in the widget, and nothing re-ticks itself.
Milestone widgets sit on a broker's own page next to their own components, so the layout that fits one portal rarely fits the next. Tiles and tabs give the widget a shape for a narrow column and a shape for a wide one.
04 ·Custom teams can be renamed and retired
A custom team can be edited or retired from the same dropdown that creates it. Renaming one or changing its logo updates every match in that community that references it, whatever state the match is in, while scores, attempts, rewards and settlement stay where they are. Removing a logo falls back to the team's first letter. Retiring a team archives it: it leaves the picker for new matches, saved matches keep rendering the name and logo they stored, and the name becomes free for a new team to take.
A team named wrong in the first week of a bracket is otherwise wrong in every round after it. Editing the catalog entry once and having the matches follow is the difference between a typo and an afternoon.
Milestone Webhook is now Custom Webhook, with its configuration panel rebuilt on the custom widget layout.
24 AugThe Earning Overview widget holds the coin icon's space while it loads, then paints the community's own icon once.
24 Aug