How the Game Randomizers Work: Rosters and Fair Picks

By BoltQuickTools team · May 18, 2026 · Updated November 8, 2026 · 4 min read

The game randomizers on BoltQuickTools are small pages with a fixed list of options and a rule for picking one. This post describes how that works, based on the code the pages run, and where the approach has limits.

Rosters are static lists

Each tool's roster is an array written into the page itself. The tools do not call a game API or a community data service, so a picker keeps working regardless of whether anyone else's service is up, and there is nothing to rate-limit.

The cost is that a static list changes only when the page is edited. When a game adds a character or moves a map location, the tool is out of date until the roster is changed, and nothing updates it automatically. Treat any "current season" list as a snapshot.

The Hot, Medium, and Quiet labels on the Fortnite picker are editorial judgments, not measured drop rates. The tool has no match data to measure from.

What the fair-pick logic does

A plain random pick from a list repeats itself more than people expect. Roll a fair 10-sided die 30 times and the chance of at least one immediate repeat is about 95% (1 - 0.929). For a drop picker, that means landing at the same place twice in a row.

The fair-pick logic prevents this with a simple rule: it keeps a count of how many times each option has been rolled, finds the lowest count in the current pool, and picks at random among the options tied at that count. This is the function from the shared randomizer.js:

function fairPick(pool) {
  let min = Infinity;
  for (const a of pool) {
    const c = state.picks.get(a) || 0;
    if (c < min) min = c;
  }
  const cs = pool.filter(a => (state.picks.get(a) || 0) === min);
  return cs[Math.floor(Math.random() * cs.length)];
}

The effect is close to dealing from a shuffled deck. On the Fortnite picker, the first 25 rolls are 25 different locations. Only after every option has come up once does any option repeat, and then the cycle starts again.

A few details follow from that code:

Counts are stored in your browser

Counts are saved to localStorage on your device and are not sent anywhere by this code. They persist between visits, even though the page labels them as session counts. Each player has their own counts, so a squad cannot share a cycle.

Keyboard shortcuts on the shared tools are Space or R to roll, U to undo the last roll, and C to reset all counts. After a reset every option is back to zero, so the next roll is a uniform random choice from the pool.

Which tools use it

Eight tools share randomizer.js, and the Apex Legends page has its own copy of the same fairPick logic. The Elden Ring and Helldivers 2 generators are different: they build a whole build or loadout from uniform random picks and do not keep counts.

Roster sizes at the time of this update:

Reporting a stale roster

If a location or character is missing or renamed after a patch, send the details to [email protected]. Saying which game and which patch helps.

Related