askbot auth
in Factorio chat (or /spectator-chat askbot auth during captain games) to get a token,
then paste it on BB Bets to unlock trading, coins, profile, tournament, etc.
Everything the website does, how the in-game askbot fits in, and how to log in. Click any section to expand.
askbot authMost website features (BB Bets trading, BB Coins transfers, admin actions on markets, future features) require being logged in as your in-game player. There are no passwords on the website — auth happens through the in-game chat bot.
Steps:
askbot auth (or /spectator-chat askbot auth during a captain game).Requires 1+ day of total playtime. The token is one-shot and expires fast — get a fresh one if you take too long.
BB Coins are a soft currency earned passively for time spent on the winning team. They power the BB Bets prediction markets and can be tipped peer-to-peer.
askbot coins — your balance.askbot coins tip <player> <amount> (alias: send) — peer-to-peer tip, no fee, min 0.1c.askbot data <player> — public profile (PnL, last 10 transactions, win/loss bets).Polymarket-style binary & multi-outcome markets paying 1c per winning share. Mid-price = market-implied probability. Fully on-chain (BB Coins).
askbot auth can resolve / cancel any market directly from its page.askbot market list · info <mid> · orders <mid> · shares · myorders · burnedaskbot market preview buy|sell <mid> <opt> <amt> — fee breakdownaskbot market create winner|duration|custom … · cancel <mid>askbot market lp add|remove <mid> <amt|all>askbot auth first, then trade with fee preview.askbot market help trade|lp|fees|create|info|admin — section-specific help.Organised PvP: two volunteer captains pick teams one by one, fixed rosters, larger coin bonus rates. Most Saturdays at 1700 CET. Streamed weekly with Ghostie on twitch.tv/og_gh0stie. Captains have ultimate authority on team strategy — listen to them or get booted.
captain_win_bonus.php, ~30s–2 min after game-end.@name.To register, watch the captain-game lobby in-game / on Discord. Community-picks games happen when no one volunteers — every non-spectator ranks every player and teams are auto-balanced.
The Draft analytics section on the captain page surfaces who is over- or under-drafted relative to their actual win contribution. Three numbers do the work:
DRAFT_MIN_PICKS picks are scored.Tiers T1–T5 are pure APP quintiles over the qualifying pool — nothing to do with win rate, skill, or PVAP. Computation:
floor(N×1/5), floor(N×2/5), floor(N×3/5), floor(N×4/5).Tiers are then mapped onto every player (including small-sample ones) using the same cutoffs, so the broader table uses the same buckets. Sleepers are flagged when tier ∈ {4, 5} (picked late) and PVAP > 0; reaches when tier ∈ {1, 2} (picked early) and PVAP < 0.
Captain Draft IQ = per-captain average of the PVAP of every player they ever picked. Positive → consistently spots sleepers; negative → consistent reaches. Independent of which side of the draft was theirs — it's measured against the league slot baseline.
The most-trafficked pages on the site — over 200k hits per category every 100 days.
askbot science topscore · science <player> · challenge · challenge topThe "online" count is the canonical source: refreshed every 60s via RCON, stored in the po table. Used by the homepage counter and by the status page.
Status page — auto-refreshes every 30s.
Visible only when logged in via askbot auth as a player in the Factorio admin list:
The flagship competitive event. Organisation, brackets, schedule and replays live on the dedicated site:
Past BB Champions tournament site (bbchampions.org) is now offline.
REST + WebSocket access to the BB Bets engine for scripts and bots. Same fees, slippage caps and balance checks as the web UI — no parallel implementation.
Visit /science/api-tokens (after askbot auth) and click "Generate". Token shown once; cap 10 active per player.
Authorization: Bearer bb_<64-hex>
Default scopes: read,trade. No admin scope yet (resolve/cancel stay web-only).
Uniform envelope:
{"error": {"code": "INSUFFICIENT_BALANCE", "message": "..."}}
Codes: UNAUTHENTICATED, FORBIDDEN, INVALID_ARGUMENT, INSUFFICIENT_BALANCE, INSUFFICIENT_SHARES, NOT_FOUND, MARKET_CLOSED, SLIPPAGE_EXCEEDED, OUT_OF_RANGE, COOLDOWN, RATE_LIMITED, CANCEL_FORBIDDEN, METHOD_NOT_ALLOWED, TRADE_REJECTED, INTERNAL.
/api/v1/me — auth check + balance./api/v1/balance — earned/lost/locked breakdown./api/v1/markets — list. Query: status, category, limit, cursor./api/v1/markets/{id} — full detail (pools, prices, k, fees, my_shares, my_orders, my_lp)./api/v1/markets/{id}/orders — public order book (no player names)./api/v1/orders — your orders./api/v1/transactions — your tx history./api/v1/pnl — per-market PnL · /api/v1/pnl/summary — aggregate./api/v1/game-state — live round snapshot: running, started_at, age, difficulty, players (online/active with freshness), open_winner_market./api/v1/buy — {market_id, option_index, coins, max_slippage_pct?}/api/v1/sell — {market_id, option_index, shares, max_slippage_pct?}/api/v1/orders/place — {market_id, side, option_index, price, amount}/api/v1/orders/cancel — {order_id}/api/v1/markets/create — {category, lp, options?, initial_prices?, title?, duration_minutes?, production_meta?} · 1 market / 15 min cooldownOptional Idempotency-Key header (any string ≤128 chars) — replays within 24h return the cached response with the original status code. Rate limit: 60 req / 60 s per token (HTTP 429 + Retry-After).
wss://biterbattles.org/bb-events
Token is sent as the first text message after connect (never appears in proxy logs):
ws.send("auth bb_<your_token>");
// → {"kind":"auth_ok","player":"...","scopes":["read","trade"]}
// or {"kind":"auth_error","reason":"..."}
ws.send("sub 0"); // firehose: every game / market / trade event
ws.send("sub 391"); // per-market: only events for market 391
// Event payload:
{"id":N, "kind":"new_trade", "market_id":391, "player":"X",
"data":{...}, "at":"YYYY-MM-DD HH:MM:SS"}
ws.send("ping"); // → {"kind":"pong"}
ws.send("unsub 391");
Caps: 50 connections / IP, 10 / authenticated player, 20 subs / connection. Pre-auth idle > 30s → close.
TOKEN="bb_..."
# Buy 1c worth of option 0 (e.g. North) on market 391
curl -X POST -H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"market_id":391,"option_index":0,"coins":1.0}' \
https://biterbattles.org/api/v1/buy
# Get market detail
curl -H "Authorization: Bearer $TOKEN" \
https://biterbattles.org/api/v1/markets/391
# Place + cancel a limit
curl -X POST -H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"market_id":391,"side":"buy","option_index":0,"price":0.4,"amount":2}' \
https://biterbattles.org/api/v1/orders/place
curl -X POST -H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"order_id":47}' \
https://biterbattles.org/api/v1/orders/cancel
# Create a custom market
curl -X POST -H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"category":"custom","lp":5,"options":["Yes","No"],"title":"Will North win?","duration_minutes":60}' \
https://biterbattles.org/api/v1/markets/create
Tokens leaked? Revoke from /science/api-tokens — instant; existing WS connections drop on next heartbeat.
Type these in the in-game chat. During a captain game, prefix with /spectator-chat to whisper the bot privately.
askbot auth — get a one-shot token to log into the website.askbot data <player> — public PnL / coins / bets summary.askbot vs <playerA> <playerB> — head-to-head over the last 90 days: games together, games faced, who won. Full top-10 allies / rivals on the player profile.askbot coins — your balance.askbot coins tip <player> <amount> (alias: send) — tip, min 0.1c.askbot market list · info <mid> · orders <mid> · shares · myorders · burnedaskbot market preview buy|sell <mid> <opt> <amt>askbot market help trade|lp|fees|create|info|adminaskbot market create winner|duration|custom … — open a market.askbot market cancel <mid> — cancel (creator if no trades, or admin).askbot market lp add|remove <mid> <amt|all> — provide / withdraw liquidity.askbot market resolve <mid> <opt> — admin-only force resolve.askbot auth then the website.askbot science topscore · science <player>askbot challenge · challenge topaskbot elo` (backtick) — open chat / command window./help — list of all chat commands./admins — list admins online (ping politely if you need trust)./spectator-chat <msg> — whisper spectators only (also used to message askbot privately during a captain game). Tab-complete: /spe[tab]./nth <msg> · /sth <msg> — chat to north / south team only (available to spectators too)./shout <msg> — message both teams./calc-send force=<n|s> color=<sci> count=<n> — preview evolution / threat impact of sending science. Auto-fills evo, difficulty, players from current game state. Color aliases: red=automation, green=logistic, gray=military, blue=chemical, purple=production, yellow=utility, white=space. Full form: /calc-send evo=20 difficulty=30 players=4 color=green count=1000./i <category> — scan inventories for items by category (e.g. /i ammo, /i defense). Great for finding who's hoarding./where <player> · /follow <player> — locate / spectate-follow a player./clear-corpses — wipes biter corpses (run after big fights to reduce lag)./crafting-list — toggle the personal crafting-queue window./inventory-costs [all] — top players by inventory value (all = both forces)./jail <player> · /suspend <player> — admin-only. Suspend = forced spectator for 10 min./announce · /announce-append — admin-only, posts text on spectator island./difficulty-revote · /difficulty-close-vote [<name|%>] — admin-only, re-open / close difficulty vote./scenario restart|shutdown|restartnow — admin-only, soft-reset / shutdown control./instant-map-reset [seed] — solo-mode (or admin), force a reset; pass a seed (341–4294967294) or omit to print current./current-map-seed — print the current map seed./set-pathfinder bb-default|bb-new|default — admin-only, switch pathfinder preset at runtime.biterbattles.org:34197.%appdata%\Factorio\scenarios\Factorio-Biter-Battles doesn't auto-update — delete the folder and reconnect to refresh.Quick reference focused on what you actually do in-game: rules, strategy, builds, combat. For the full wiki — pictures, blueprints, deeper articles — head to freebb.miraheze.org. Click any section below to expand.
Biter Battles is a scenario ("soft mod") originally written by M3wM3w at Comfy Factory. Two teams (north / south) face off across a central river. You win when the enemy silo dies. You make the enemy biters stronger by feeding science flasks to your own team's scoreboard — those flasks raise the enemy biters' evolution and threat. It's an indirect-PvP speedrun: build fast, build compact, every tile you defend is a tile you have to wall.
Use the in-game /calc-send command to preview how a given send affects evo and threat — it auto-fills evo, difficulty and player count from the live game.
"Difficulty" is how effective science sends are, not how fast biters get strong on their own. Exact values from tables.lua:
| Level | Short | Mutagen |
|---|---|---|
| I'm Too Young to Die | ITYTD | 20% |
| Have a Nice Day | HaND | 35% |
| Piece of Cake | PoC | 50% |
| Easy | Easy | 75% |
| Normal | Normal | 100% |
| Hard | Hard | 200% |
| Fun and Fast | FnF | 500% |
On Normal, lower-tier sciences (green, military) readily bring opponents to 50% evo (big biters → flamers required). On ITYTD, mutagen is only 20% as effective — those games typically run to multiple rocket sends. Effectiveness slowly rises after 3 hours so games eventually end.
tables.lua / ai.lua)Each science type contributes "mutagen strength" per flask. Bigger sciences punch ridiculously harder than reds:
| Science | Mutagen / flask | vs red |
|---|---|---|
| Automation (red) | 9 | 1× |
| Logistic (green) | 23 | 2.6× |
| Military | 95 | 10.6× |
| Chemical (blue) | 292 | 32× |
| Production (purple) | 1050 | 117× |
| Utility (yellow) | 2205 | 245× |
| Space (white) | 4375 | 486× |
Threat farmers: each kill removes a fixed amount of threat from your team's pool:
| Target | Threat removed |
|---|---|
| Small biter / spitter | 1.5 |
| Medium biter / spitter | 4.5 |
| Big biter / spitter | 13 |
| Behemoth biter / spitter | 38.5 |
| Small / medium / big / behemoth worm | 8 / 16 / 24 / 32 |
| Biter / spitter spawner | 32 |
health_multiplier_boss = 20 × 1.3). Half of late-game waves are bosses.threat_scale_factor_past_evo100).ceil(48 / difficulty_value): ITYTD = 240, HaND = 138, PoC = 96, Easy = 64, Normal = 48, Hard = 24, FnF = 10. Fish always allowed.biterbattles.org:34197.#announcements if unsure.You join as a spectator on the central island. Spectating is the best way to learn; especially in 3+ vs 3+ games. Spectators see only the union of what both teams see — fog of war still applies if neither team has radars.
By default, spectator chat goes to both teams. Ask questions, but don't dominate the chat.
%appdata%\Factorio\scenarios\Factorio-Biter-Battles (delete the folder + reconnect to the server to refresh it — it doesn't auto-update)./instant-map-reset.BP libraries / imports are disabled by design — copy-pasting intricate builds would kill the game. New players also can't use in-game blueprints until they're "trusted":
` (backtick) — open chat./help — full command list./admins — list admins online. Be polite. Especially do what Fordeka tells you./spectator-chat, /nth, /sth, /shout — see the askbot cheatsheet section above.If you're new and don't know what to do, take a defense role while learning the build patterns. Defense is what keeps the silo alive long enough to win.
Each player starts with 10 burner miners. Most teams expand to cover at least one iron, copper and coal patch. Burner miners are more cost-effective than electric in the early game (1 coal of input pays itself back). Don't remove burners while there's still iron in main — counts as soft-griefing. Many players prefer left-to-right placement (mouse motion + burner coal hunger).
Patches typically run a 6:5:2:2 iron:copper:stone:coal ratio (not guaranteed). Pros: all ores in one place, cheap basic intermediates. Cons: unbalanced consumption clogs the system. Strategies:
Three flavors: intercepting waves, extraction (killing spawners — fast threat dump but hard with worms), and proper farming (killing biters near spawners, optionally killing worms). Goal: keep team threat ≤ 0 so no waves spawn against you.
Worms / standing spitters lead their shots. Dodge by changing direction after they shoot. The trick:
For captain-games scoring, picking strategy and roles see the Captain Games section above. This section covers the special-game variants admins can spin up.
Variant rule sets — restricted/unrestricted tech, free items, threat tweaks, etc. — set up by admins, often voted by the players online. Announced in #bb-special on Discord.
Most common addition. Lets thin teams reach late-game faster. Typical: armor + power + personal roboport + bots in infinity chests near each silo. You can't interact with the chest directly — drop an inserter onto it.
Belt trick to grab tons quickly: two belts facing each other create jitter; you can grab items off an inserter as soon as it picks one up (before the place animation completes). Holding mouse on the inserter's edge while jittering between the two belts → hundreds of items in seconds.
Most Saturdays at 1700 CET (check Discord events). Captains pick teams one by one, hold final say on strategy. Listen or get booted. Often 50+ players, well-balanced into late-game; experienced players in main and outposts → great place to learn building. Community-picks games happen when no captains volunteer (every player ranks every player; teams auto-balanced).
automation → military → gun-turret → logistic-sci → steel-processing → military-2 (handcraft 20 green) → stone-wall → heavy-armor → logistics → electronics → fast-inserter → steel-axe → PPD-1 → WSS-1 → automation-2 → mil-sci → stronger-explosives-1 → PPD-2 → WSS-2 → adv. material processing → engine → fluid-handling → oil-processing → flammables → flamethrower → refined-flammables-1 → refined-flammables-2.
Same path, slightly different early ordering: automation → military → gun-turret → logistics → logistic-sci → steel-processing → military-2 → stone-wall → electronics → fast-inserter → steel-axe → heavy-armor → PPD-1 → WSS-1 → automation-2 → mil-sci → stronger-explosives-1 → PPD-2 → WSS-2 → adv. material processing → engine → fluid-handling → oil-processing → flammables → flamethrower → refined-flammables-1 → refined-flammables-2.
Most of these are not absolute rules, but if you're new the chances you're applying the exception correctly are slim. Default to following them.
Main owns the team's research. Changing builds without asking, deconstructing, building into reserved space → fastest way to lose friends and get jailed. Before you change anything: understand it, ping the builder with @name, mark the location with Ctrl+Alt+left-click. If it's an obvious mistake (missing pipe / inserter on an otherwise complete build) you can fix it; if you're unsure, ask. Stay in Discord at least to listen — the community can't teach you if you refuse to communicate.
A typical mall supports 2–3 players (usually the lead builders). Sweeping its belts wastes their time waiting for refills. If you're not in a location-bound critical role, use the burner city or spin a small mall outpost on a nearby ore patch — you'll get more resources faster anyway.
Yellow: 15 items/s for 1.5 iron (10/iron). Red: 30 items/s for 11.5 iron (2.6/iron). Red belts cost ~4× more iron per throughput, and almost never run 100% full. Sole exception: a specific smelter design that uses red belt instead of undergrounds. Many top players delay red-belt research deliberately.
Sending lab sci slows your own research. Even sending outpost-grown sci can backfire — threatfarmers are most efficient between 20–50% evo, so raising enemy evo while they have negative threat just helps them farm faster.
Outposts belong to whoever started them. Ask. Once invited, follow their rules. Don't be salty if rejected.
Bots will repair walls and die in the process. Walls are cheap; bots aren't. Let walls break and have bots replace them — much faster, fewer bot losses. Exception: special games with free bots.
Bots are scarce; queueing a giant wall hogs them. Use a separate small bot network with a chest of walls right next to the roboport, or build a "wall belt" feeding chests near the wall. Both rebuild walls much faster anyway.
Speed-1 in particular is a power glutton. Save modules for pump jacks and judicious main-builder placements. More assemblers usually beat speed-modded fewer.
Flamers, roboports etc have a natural cap. Unlimited chests will plow iron+steel into items you'll never place. Mall throughput depends on intermediate chests filling up to free room downstream — limit yellow inserter chests to ~2–4 stacks. Always-unlimited: lasers, steel buffers, rocket-part buffers, one yellow-belt chest.
You'll die, lose your corpse, and the resources are gone. Take only what you need; refill from the mall when you survive.
Something missing or out of date? Ping us on the Discord, or contribute to the community wiki directly.