Inspect the composition
See how the play area, supporting information and controls share the browser space.
Dice game · Barbut
Inspect the table.
Follow the visible round.
Open the Barbut guest demo to review its current table layout, available controls and dice-result feedback. Rules and control behaviour should be taken from the playable client rather than inferred from this page.
Dice games · BarbutA dice-table client on screen
Review layout, action and result as one flow.
The demo gives product teams a direct way to assess the visual hierarchy and changing state without relying on undocumented descriptions.
Start from the client
Use the controls currently exposed by the demo and watch the round advance.
Read the dice feedback
Observe how the completed state is presented before another round becomes available.
Delivery responsibilities
Barbut uses the shared RGS while the wallet remains operator-owned.
When Barbut is included in an agreed rollout, the FastGamesAPI RGS handles the game session, round state and result record. The operator remains responsible for player authentication, account balances and the wallet ledger.
Use sandbox testing for approvals, declines, duplicate requests, timeouts and reconnection. Public demo access does not confirm a production game set.
- Inspect the current table client on relevant devices.
- Confirm the sandbox identifier before integration testing.
- Test wallet failure and recovery paths.
- Confirm production scope through the written proposal.
Read the shared integration flow or compare titles in the game hub.