Hunger Games Simulator

Guide

Hunger Games Simulator Custom Characters & Events

Everything you can change before the first cannon: your own tributes, the district pairings, and event lines the simulator will mix into the arena.

Customising is the whole point of a hunger games simulator. A fixed cast gives you the same handful of seasons; your own cast gives you one you actually care about — your class, your group chat, a set of characters you already argue about.

Everything below is set up before the first cannon fires. None of it needs an account, and none of it leaves your device.

Custom characters: adding your own tributes

Switch the Names dropdown to “My own list”. A text box opens. Type one tribute per line, then pick a headcount from the Tributes menu (8 to 48) or leave it alone — the simulator will use as many lines as you typed, up to 48.

The rules that matter

  • Two tributes per district. Names are paired in the order you type them: lines 1 and 2 are District 1, lines 3 and 4 are District 2, and so on. If you paste in an odd number, the last tribute still gets their own district number.
  • 24 characters per name. Long enough for “President Snow”, short enough that the event log does not wrap on a phone.
  • Blank lines are ignored, and so is leading or trailing whitespace. Copy-pasting a column out of a spreadsheet just works.
  • Duplicate names are allowed but painful to read: two tributes called Sam make the log ambiguous, and the fallen list cannot tell you which one died.
  • Your list is saved in your browser. Close the tab and it is still there next time; it is never uploaded to a server.

Where to get a good list

A class roster is the classic: 24 names, two per district, and the whole room has a stake in the outcome. A group chat works the same way, so does a Discord server (paste the member list, one name per line). For fan seasons, type the characters yourself — the built-in book pool is there for speed, but a hand-picked cast of twelve villains playing against twelve heroes is a much better watch.

The Shuffle button regenerates the roster preview without changing any settings, which is useful when you want a random cast but the first draw put three people you know in the same district.

Districts and the victor banner

Districts are cosmetic in the sim — they do not change the odds, the events or the death rate. They matter for the story: the victor banner reads “District 7 · 3 kills · survived 12 rounds”, and the district number is what people quote when they retell a season. If you want an all-District-1 final, type the names you care about in pairs at the top of your list.

Custom events: writing your own arena

Below the roster there is a collapsed panel called Add my own events. Open it and write one event per line, using {A} and {B} where the names should go:

  • {A} steals {B}'s sleeping bag and runs.
  • {A} finds a bow in the rubble and does not tell anyone.
  • {A} and {B} agree to split the district's supplies, then both lie about it.

Lines without {B} are single-tribute events; lines with both placeholders will only be used in rounds where two tributes are available. Your line list is capped at 40 and saved in your browser.

How custom events get mixed in

Each day and night round the simulator fills six or more narrative slots before it rolls the deaths. When you have custom lines saved, roughly two in five of those slots draw from your list instead of the built-in pool. You are adding flavour, not replacing the engine — the pacing, the death rate and the win condition stay exactly the same.

Custom events never kill anyone

This is deliberate. If a typo in your event line could end a tribute's season, a broken sentence would break the game. All deaths still come from the built-in pool, so the worst case of a bad custom line is a strange sentence in the log. Write freely.

What makes a good custom event

  • One sentence, present tense. It is a log line, not a paragraph.
  • Something visible happened. “{A} sits quietly” is a wasted slot; “{A} lights a fire and immediately regrets it” is not.
  • Keep it inside the fiction. Injuries, weather, sponsors, supplies, arguments — not memes from outside the arena.
  • Write eight to fifteen lines, not forty. A small set that fits your cast reads like a theme; forty lines read like noise.

Good starting sets: inside jokes for a class season (the physics teacher's tent, the school bus), callbacks for a streamer season, or relationship drama for a fanfic cast — an alliance that keeps almost breaking is more fun than a clean victory.

How the cast size changes the season

Eight tributes gives you a short season — the bloodbath takes about a fifth of the field, so you are down to six in round one and finished in under ten rounds. Twenty-four is the default and the pacing most people expect. Forty-eight is chaos: longer rounds, a crowded fallen list, and a much higher chance that the tribute you were rooting for dies in a round you skipped past.

What to do with the result

Every season can be copied as plain text with Copy the story — the full log, round by round, with the victor and their kill count at the end. Paste it into a group chat and people will read it. The seed in the page address also means a friend who opens your link gets the identical season, which is the only fair way to settle an argument about who would win.

Custom characters and events FAQ

How many custom tributes can I add?

Up to 48, with a minimum of 8 for a sensible season. The simulator uses as many names as you type, so a 30-name list gives you a 30-tribute arena.

How are districts assigned to custom characters?

Two per district, assigned in the order you type them. Lines 1 and 2 become District 1, lines 3 and 4 become District 2, and an odd final name still gets its own district number.

Can my own events kill a tribute?

No. Custom events are narrative only — they fill the flavour slots in a round, never the death slots. All deaths come from the built-in pool, so a typo can never end a tribute's season.

Is my custom list uploaded anywhere?

The names and event lines are stored in your own browser's local storage. Nothing is sent to a server, and clearing your browser data removes them.