BC.Game Crash Script: Simple Step-by-Step Guide

Short answer: a BC.Game crash script is JavaScript that places your Crash bets by rules you set. It does not change the house edge or the odds of any round, and no betting system guarantees a profit. Over enough rounds, expect to lose about the house edge on what you stake. Set a loss limit first and put it in the script.

Key facts · Before you start · The steps · Your odds · Where it goes wrong · No-KYC notes · FAQ

Written by Noki, lead reviewer at the NoToKYC desk. Last updated 2026-11-06. See our methodology. We may earn a commission if you sign up through links on this page; it never changes a rating.

You need three things to run a BC.Game crash script:

• A BC.Game account with a balance. Every scripted bet is a real bet.
• The currency you'll bet in, selected. The script reads its bet limits from currency.minAmount and currency.maxAmount, per a 2022 post on BC.Game's forum by staff member Skele that documents the script API.
• A loss limit. See step 1.

Skip any guide that has you paste code into the browser console, including this page's old version.

How a Crash round is decided

BC.Game's How to Play Crash article gives you 6 seconds to bet before each round. A multiplier then climbs from 1.00x. Cash out before it crashes and you get your bet times that multiplier. If it crashes first, you lose the bet.

The result isn't drawn while you watch. BC.Game's white paper page on provable fairness says:

"We have generated a total of 10 million hashes (the generation chain is verifiable), and each hash corresponds to a Crash multiplier." (BC.Game white paper)

How to check a round is provably fair

BC.Game's provably fair explainer says each round is decided by a server seed "generated before the round begins". For Crash, the white paper adds that "the crash number of each turn already exists and is not calculated after the game starts."

For Crash, check the round's hash:

1. Log it from your script. BC.Game's API exposes the last round as game.history[0], with hash and crash values.
2. Paste it into BC.Game's crash verifier, linked from the white paper.
3. The multiplier it shows should match the one you saw.

Six steps. The first happens before you open the game.

Step 1: Set your loss limit

Pick the most you'll lose this session, in the currency you'll bet in. That's your loss limit. The script won't start without it and refuses any bet that could take your losses past it. Set it now. A limit picked mid-streak tends to move.

Step 2: Open Crash and add a script

Open Crash. BC.Game's 2020 write-up of the game puts scripts behind an Add A Script button on the game screen, with three built-ins: Simple, Martingale and Payout Martingale. The label and the built-ins may differ today. Add your own, so the loss limit sits in code you can see.

Step 3: Paste the code

Paste this in. Every call comes from BC.Game's script API post. We have not run this script with real money; it is built only from the functions that post documents.

var config = {
baseBet: {
label: "Base bet",
value: currency.minAmount,
type: "number" },
cashOut: {
label: "Cash out at (x)",
value: 2, type: "number" },
onLoss: {
label: "On loss, multiply bet by " +
"(2 = Martingale, 1 = flat)",
value: 2, type: "number" },
maxLosses: {
label: "Stop after this many " +
"losses in a row",
value: 6, type: "number" },
lossLimit: {
label: "Loss limit for " +
"this session",
value: 0, type: "number" }
};

function main() {
// Read the form here, inside main(),
// so changes you type are picked up.
var base = config.baseBet.value;
var cashOut = config.cashOut.value;
var step = config.onLoss.value;
var maxLosses =
config.maxLosses.value;
var lossLimit =
config.lossLimit.value;

var bet = base;
var losses = 0;
// running result since start;
// currency.amount does not update
// mid-run
var net = 0;

game.onBet = function () {
if (lossLimit <= 0) {
log.error("Set a loss limit " +
"above 0, then start again.");
game.stop();
return;
}
if (bet > currency.maxAmount) {
log.error("Next bet " + bet +
" is over the maximum of " +
currency.maxAmount +
". Stopping.");
game.stop();
return;
}
if (bet - net > lossLimit) {
log.error("Next bet could take " +
"losses past " + lossLimit +
". Stopping.");
game.stop();
return;
}
game.bet(bet, cashOut).then(
function (payout) {
if (payout > 1) {
net += bet * (payout - 1);
log.success("Cashed out at " +
payout + "x. Net " +
net.toFixed(8));
bet = base;
losses = 0;
} else {
net -= bet;
losses += 1;
log.error("Loss " + losses +
" in a row. Net " +
net.toFixed(8));
if (losses >= maxLosses) {
log.error(losses +
" losses in a row. " +
"Stopping.");
game.stop();
return;
}
bet = bet * step;
}
});
};
}

Step 4: Fill in each setting

The form shows these settings:

• Base bet. Your first stake, and the stake after every win. It defaults to currency.minAmount.
• Cash out at (x). The auto cash-out sent with each bet. 2 means 2.00x. Higher pays more, less often.
• On loss, multiply bet by. 2 is Martingale, 1 is flat staking.
• On win. No setting. The stake resets to the base bet.
• Stop after this many losses in a row. Default 6.
• Loss limit for this session. Your step 1 number. At 0, nothing runs.

The script also stops before any bet above the currency maximum, which doubled stakes reach sooner than you'd think.

Step 5: Choose Martingale or flat stakes

Martingale doubles after each loss and resets after a win. Flat staking bets the same 1 unit every round. A losing run from a 1-unit base bet:

At a 2.00x cash-out, one Martingale win recovers the run plus one base bet. By round 11 you're risking 1,024 to win that one unit. Flat staking loses slowly and never recovers a run in one go. Neither changes the odds.

Step 6: Run it and watch the log

Start it and watch the log. Each round prints the result and your running net, and the last line says why it stopped.

A BC.Game crash script automates bets. It doesn't change the house edge or the odds of any round, and no betting system guarantees a profit.

BC.Game publishes two figures. Its How to Play Crash article says "the house edge is 1%". Its house edge and RTP article says:

"We recently adjusted the Return to Player (RTP) percentage for our original games, changing it from 99% to 96%." (BC.Game Help Center)

A 96% RTP is a 4% edge. That article uses Crash to show where to look: widen the game table with the arrow below it and the RTP appears. Use that figure. A 2.00x cash-out wins the RTP divided by two: 49.5% of rounds at 99%, 48% at 96%.

Now run Martingale to the end. Balance 100 units, base bet 1, cash-out 2.00x, loss limit 100. Each win nets one unit. Six losses in a row cost 63 and trip the streak stop. Without it, the loss limit blocks the next stake of 64. One bad run wipes out 63 wins. It comes about once in 60 sequences at a 99% RTP, once in 51 at 96%, so over a couple of hundred rounds it's more likely than not.

Over enough rounds, expect to lose about the house edge on what you stake: roughly 10 units per 1,000 at 1%, or 40 at 4%. Martingale doesn't change that rate. It takes the loss in rare, large chunks.

Most BC.Game crash script problems are one of these.

• The pause is gone. A script removes the pause between bets, which is often when you'd notice you're chasing losses. The coded loss limit does that job, so pick a number you won't override.
• A stale balance. BC.Game's API post says currency.amount is your starting balance and doesn't refresh mid-run, so the script tracks net itself.
• Settings that don't stick. A regular in a script thread on BC.Game's forum warned that editing the config declaration "is only going to change the default value". This script reads the form inside main().

A BC.Game crash script doesn't change your privacy either way: scripted bets are ordinary bets, under the same terms and checks. Verification policy is a casino question, covered in our no-KYC casino reviews. If privacy starts at the deposit for you, see our privacy coins rundown.

One rule does follow the script: BC.Game's general terms bar "software-assisted methods" and reserve the right to "invalidate any wager". See the FAQ.

The same general terms state that BC.Game operates under License No. ALSI-202410011-FI1 from the Government of the Autonomous Island of Anjouan, Union of Comoros.

• All our gambling script guides.
• The BC.Game Hash Dice script guide.
• How each casino handles verification: no-KYC casino reviews.

Affiliate disclosure: NoToKYC may earn a commission when you sign up through links on this page. This never affects our ratings, rankings, or what we report — see our review methodology.

Play responsibly (18+): Gambling can be addictive. If it stops being fun, get free, confidential help — US: National Problem Gambling Helpline, call/text 1-800-MY-RESET (1-800-697-3738), 24/7. UK: National Gambling Helpline (GamCare) 0808 8020 133, 24/7. Outside the US/UK: GamblingTherapy.org. Free blocking tools: BetBlocker, Gamban. Self-exclusion (GB): GamStop.

Availability: You must be of legal gambling age in your jurisdiction (18+, or 21+ where required). Online gambling is restricted or illegal in some countries and regions — check your local laws before playing. No-KYC availability and terms can change without notice.

Note on GamStop: it only covers operators licensed in Great Britain. It does not block sites outside that scheme.