Step 4: Place bets and collect

Your session is up and the config is loaded. Now the round loop needs two more calls. placeBet starts or continues a round. collect banks winnings when the game offers that choice.

What to do

1. Restore the loaded round before enabling any money action. Apply effective stakes.
2. For a new player-requested round, call placeBet({ backendURL, token, stake, config }) under a request lock.
3. Render the scenario. Finish required timing, operator notifications, and animation reporting.
4. Inspect round status, canCollect, pending choices, and inProgress, in that order. Use the slot controller.
5. Wait for player input where a choice or cashout is offered. Continue only as the vertical permits.
6. Reconcile failed or lost responses through recovery. Never automatically retry a money request.

Partial collection can protect winnings inside an open round without crediting the wallet. Full collection omits the amount. See gamble and banking.

TIP

Use approved test outcomes to exercise wins, bonus triggers, and losses. See Cheating for test-environment controls.

Where to read more

• Getting Started with hizi engine SDK: the ordered implementation path and validated session setup.
• Game Flow: one worked, class-based implementation of the whole round lifecycle. Use it as a model for your client.
• Response Handling: the IGameResult shape, multi-step continuations, and progression counters.
• Error Handling: the response union, recoverable error codes, and what to do with each.
• Game Guides: the scenario shape for each game type, and any additionalData that type's rounds need.

Next: Step 5: Implement the Operator Interface.