7 min read

Auto bet repeats entries; cash out settles an entry
Auto bet is a control for submitting further entries according to selected settings. Auto cash out is a control for settling an active entry when its stated condition is met. They answer different questions: whether another stake is submitted, and how an accepted stake exits. A heading such as “Auto” is not enough to tell you which actions are enabled. Read each switch and field separately before treating the panel as one instruction.
The official TrustDice guide describes auto betting for its own Crash game and requires an auto-cashout setting before that feature starts. SmartSoft lists advanced autoplay and auto cashout for JetX. These examples show why the actual game matters: controls can be connected, restricted or named differently. They do not confirm the controls in Master Crash. Our manual-versus-auto guide explains exit triggers; this page focuses on the additional records and limits needed when entries repeat.
Check what the counter counts and which stake repeats
A field labelled “number of bets” needs a scope. Does it count submitted requests, accepted entries or completed entries? Does one panel have its own count? Does restarting reset that count? The help text or recorded sequence should answer these questions; the label alone cannot. Do not assume that zero means zero entries: some interfaces use special values for an unlimited run. If the interface does not explain a value, leave the automated run off until it is clear.
The stake also has a scope. A fixed example of six accepted entries at 10 units each creates 60 units of turnover, even if some returned units are used again. Two independent panels each making those entries would create 120 units, provided both complete the assumed count. Settings such as “on win” or “on loss” may change the next stake, so multiplying the first stake by the count is then insufficient. Add the actual accepted amounts rather than relying on the first field.
Invented fixed-stake sequence: six accepted entries of 10 units each use 60 units of turnover. Settled total returns of 0, 15, 0, 20, 0 and 10 add to 45. The complete net result is 45 minus 60, or −15 units. No fees, bonuses, refunds or other activity are assumed.
A six-entry ledger: 60 staked, 45 returned, −15 net
Take an invented sequence of six completed entries, each with a 10-unit accepted stake. Their settled total returns are 0, 15, 0, 20, 0 and 10 units. Total stake is 60; total return is 45; the net result is 45 − 60 = −15 units. Returns include any stake returned within that payment. The 15-unit return therefore contributes +5 to the net result of its own 10-unit entry, not +15. The table shows each contribution.
Assume this sequence has no deposits, withdrawals, bonuses, fees, refunds or other active entries. A starting balance of 100 would then finish at 85 once all six settle. Remove that assumption and a balance change alone no longer measures this sequence: a deposit or another game could affect it. Use the multiplier calculation guide for one entry, then add complete records for the session. These selected results teach bookkeeping; they are not a forecast, return rate or suggested betting plan.
Swipe across to see all columns.
| Entry | Accepted stake / total return | Entry net / running net |
|---|---|---|
| 1 | 10 / 0 units | −10 / −10 |
| 2 | 10 / 15 units | +5 / −5 |
| 3 | 10 / 0 units | −10 / −15 |
| 4 | 10 / 20 units | +10 / −5 |
| 5 | 10 / 0 units | −10 / −15 |
| 6 | 10 / 10 units | 0 / −15 |
| Complete example | 60 staked / 45 returned | 45 − 60 = −15 units |
A stop condition needs a value, a basis and a checking time
A stop-after-count control, a maximum-next-stake control and a stop-on-session-loss control are different instructions. The first limits a count, the second compares a stake and the third compares a defined result. TrustDice documents count and bet-amount stop controls for its own implementation. If another game offers a profit or loss field, read whether it uses net settled results, balance change or something else. Do not transfer the meaning of a similarly named field from another title.
When a condition is checked matters too. In a hypothetical system that checks net loss only after each entry settles, suppose the session stands at −12 units and its stop value is 15. One more accepted 10-unit entry returning zero would leave −22 before that check stops future submissions. This is an illustration of a checking rule, not a claim about any named product. A stop label does not by itself guarantee an exact maximum loss or cancel an already accepted entry.
Stopping future entries is separate from settling the current one
If an automated sequence is running, identify the control for stopping future submissions and check the resulting state. Then inspect any entry already accepted. A stop request, a queued cancellation and a completed cash out can refer to different events. Closing a tab, changing a setting or leaving the page should not be treated as proof that every active entry has ended. Follow the game’s documented behaviour and use the entry record to establish what actually happened.
Before comparing the result with your settings, note the session’s start and stop times, timezone, panel if relevant, and whether a stake-changing rule was enabled. Match the completed entries to those times. Our round-history guide explains why the public round endpoint is separate from your personal return. If the counter and your list disagree, preserve the missing or unexpected entry IDs for support. Starting another automated sequence does not resolve an incomplete record from the first one.
Automation changes the workload, not the evidence for a future result
Automation can submit entries more quickly than a person notices their combined turnover. Reading the settings is therefore an accounting task as much as an interface task. Check the repeated stake, any rule that changes it, the counter’s meaning and the condition that stops new entries. A series of losing or winning entries does not make the next result known. Increasing the stake after a loss adds exposure; it does not verify that the next round will recover that loss.
For Master Crash, confirm the available controls and their exact wording inside the actual game before applying an example from this guide. There is no universal auto-bet preset to recommend across Crash products. If the settings cannot be understood, keep automation disabled. When reviewing a completed sequence, describe it with accepted stakes, settled returns and the resulting net total. That record remains useful even when a product’s colours, control names or layout change.
Sources and scope
- TrustDice Help — documented controls for its own Crash auto-betting feature
- SmartSoft — JetX product page: autoplay and auto cashout availability
- Master Crash — multiplier calculations and net results
Product-specific controls remain subject to the installed app. Illustrations are explanatory and do not represent measured game results or genuine app screenshots.
How we edit and correct these guides
Quick questions
Does auto bet also switch on auto cash out?
Do not assume so. A game may link the controls or require one before enabling the other. Check the actual settings and game rules; the functions still describe different actions.
Is total return the same as session profit?
No. For a completed sequence without other adjustments, subtract the accepted stakes from settled total returns. The six-entry example returns 45 from 60 staked, so its net result is −15.
Does a stop-loss field guarantee the exact most I can lose?
The label alone does not. Its calculation basis, checking time and treatment of existing accepted entries must be established from that game’s rules. Do not treat a future-entry stop as a refund or an active-entry cancellation.




