BotsWhat the generated players are allowed to do, per site

Judged against — minimum and — maximum — this site's own player limits, not a number typed here. The page refuses to save a value that breaks them, which is the whole reason it exists rather than a script somebody has to remember to run.

Each site is judged against its own limits, so saving to every site can succeed on some and be refused on others. It will tell you which.

The crowd

How many appear on the board each round. These are not accounts and they are not money: they are worked out in the browser from the round number, so the same crowd appears for everybody in that round and the server does no work at all. Two hundred or a thousand costs the same — nothing.

What they never touch. No balance, no bet row, no transaction, and nothing in total_bets, total_payouts or actual_profit. The board can be busy; the books stay true.

Set in the look, alongside the skies — crowd_min, crowd_max, and crowd_source, which is client for the derived crowd or server to fall back to whatever the API sends, without a deploy.

Still owed, and it is not this page. The API writes the old simulated stakes into each round's total_bets and actual_profit. Those figures are read back as if they were takings, and switching the board to the derived crowd does not clear them — that is a change in the Laravel app, not here.

Every site

Drift is the point of this table. The estate has been running two different settings-table shapes and seven sites without a switch.