To form random teammates in Arena Breakout: Infinite, paste your roster of gamer tags into a browser-based Random Team Generator, set the squad count to a positive whole number that does not exceed the roster size, and press Generate teams — the tool partitions the list into balanced groups whose sizes differ by at most one player, all without uploading a single name to a server. The whole process happens locally in your current browser tab, randomness is drawn from the browser's own cryptographic source at the moment you click the button, and the previous grouping is not quietly reused. For a tactical extraction shooter like ABI, where squad balance affects how quickly a team reaches an extraction point, even rosters of two, three, or four make a noticeable difference in how fair a custom match or community event feels.
Arena Breakout: Infinite, published by Morefun Studios in 2024 and playable on PC through Steam, Wegame, and a standalone client, is built around coordinated squad play in maps such as the Valley, the Farm, and the Frontline Fortress. Most lobbies expect two-, three-, or four-player teams, and community events or local meetups often need to split a larger signup list into several balanced squads at the start of an evening. Doing that by eye tends to favour whoever gets chosen first, and asking people to pick sides can leave the awkward leftovers on the smaller team.
What "Random Teammates" Means in Arena Breakout: Infinite
In the ABI context, the phrase usually refers to one of two situations. The first is filling out your own squad from a friends list or Discord channel — you have a few names and you want a quick fair draw of who joins, who sits out, or who leads. The second is running a community event: an esports club night, a streamer charity squad, a university society meetup, or a Discord community tournament, where you have a signup sheet of between six and forty gamer tags and you need to split them into a fixed number of squads in one shot.
Both cases share the same core requirement: every gamer tag appears in exactly one squad, squads stay close in size, the draw is transparent enough that no one can claim the result was rigged, and the names are not leaked to a third party. A browser-based partition tool satisfies all four points because it operates on the text you paste and produces groups immediately, with no intermediate account or upload step.
Why a Random Team Generator Fits ABI Squad Building
Several characteristics of an ABI-friendly team draw line up with how the Random Team Generator is built. It accepts one gamer tag per line or comma-separated names, which matches the way most people keep a friends list or a signup sheet. It lets you set any positive whole number of squads up to the roster size, which covers everything from a 2-squad scrim to a 6-squad community tournament. It balances headcount by design, putting the leftover players into the larger squads so the smallest and largest teams differ by at most one member.
The partition is also private. According to the tool's contract, the roster is not posted to a server, not saved to an account, and not sent to an organizer — every step runs in your browser. That matters when the list includes usernames you would rather not share, minors playing under family accounts, content creator handles, or just friends who expect you not to repost their tags. Randomness is generated with the browser's cryptographic source at the moment you press the button (the same approach documented at the MDN Crypto.getRandomValues reference), the page does not choose a squad while it is loading, and it does not quietly reuse a previous result.
How to Pick Random Teammates in Arena Breakout: Infinite
Open the Random Team Generator in the same browser you use for ABI and follow these steps with a roster of gamer tags ready to paste.
- Gather the roster. Collect the gamer tags in a document, a Discord channel, or the signup sheet for the evening. Decide how many squads you want before you open the tool, so you know the number to type into the team field.
- Paste the names. Paste the gamer tags into the roster field — one name per line, or comma-separated if the list already came out of a spreadsheet or an email. The tool trims leading and trailing spaces, ignores blank lines and stray commas, and treats each non-empty entry as exactly one player.
- Set the squad count. Enter a positive whole number of squads that is no larger than the number of pasted names. The tool blocks empty teams, so a request for ten squads from six names cannot be entered since the squad count must not exceed the roster size.
- Generate the teams. Click the Generate teams button. The tool runs an unbiased shuffle, randomly distributes the leftover names across the randomly selected squad labels, and slices the shuffled list into groups whose sizes differ by at most one. The result appears immediately on the page.
- Review and share. Read each squad aloud in the lobby, copy the displayed tags into your ABI party chat or a Discord channel, or screenshot the result. If attendance changes, edit the roster and generate a fresh grouping rather than moving people between the old squads by hand.
Generating once for the room is usually enough. The draw is fair by construction — every non-empty entry is placed into one squad, and the squad sizes are as close as the numbers allow — so nobody has a credible reason to ask for a reroll unless the roster itself has changed.
How the Balanced Split Actually Works
Behind the single button click, the Random Team Generator follows a four-step partition. It first trims spaces and removes blank lines from whatever was pasted, then performs an unbiased Fisher–Yates shuffle of the cleaned roster using random values drawn from the browser's cryptographic source, as outlined in the standard Fisher–Yates shuffle overview. Next, it decides which squad labels should receive any leftover names when the roster size does not divide evenly, then slices the shuffled list into non-empty groups in squad order.
A concrete example, taken straight from the tool's documented behaviour: seven gamer tags split into three squads produces squad sizes of three, two, and two — the largest squad has exactly one more player than the smallest. The same seven tags split into two squads produces sizes of four and three. The same seven tags split into seven squads produces seven solo entries, one tag per squad. None of the seven names is repeated or dropped in any of these draws; they are simply regrouped.
Different ABI situations pull on the tool in different ways, and the table below shows how a typical roster maps to a sensible squad request.
| ABI scenario | Typical roster | Squads requested | Why a random partition fits |
|---|---|---|---|
| Solo fill-in for a 4-stack | 4–8 friends | 1–2 | Decides fairly who plays tonight and who sits the next match out |
| Discord community night | 12–40 signups | 3–10 | Replaces awkward side-picking with one transparent draw |
| Charity or creator stream | 6–12 volunteers | 2–4 | Tags stay local to the host's browser |
| University society tournament | 16–32 signups | 4–8 | Regenerate quickly when a player drops out mid-bracket |
For the exact squad sizes on your actual signup list, run the tool itself — these scenarios describe the relationship between a roster, a squad count, and the kind of result you should expect, not a calculated answer for a specific roster.
Privacy and Trust When Handling ABI Gamer Tags
Even for what looks like a low-stakes draw, the roster you feed in can be more sensitive than it feels. Friends list screenshots, signup sheets with real names next to gamer tags, and minor accounts all carry some weight. The tool's contract is explicit on this point: the roster is not posted to a server, not saved to an account, and not sent to an organizer. The grouping is computed on your machine and stays on your machine.
This is also why a deliberate duplicate matters. The tool preserves repeated names as repeated entries, which is useful when you want, say, two chances for a streamer who asked to be in a higher-tier squad, but it also means an accidental paste of the same tag twice adds that name to the roster as a second entry. Skim the pasted list once before pressing Generate teams and remove repeats that are not on purpose.
A practical workflow for ABI sessions is: pick the number of squads before sharing your screen, paste the roster, confirm the visible player count looks right, generate once for the room, and screenshot the result for your records. Keep the original list elsewhere so that if a player arrives late or drops out, you can edit and re-generate rather than trying to shuffle people between squads by hand.
Tips for Fair and Replayable Squad Generation
A few small habits make a draw run smoothly in a busy ABI lobby. Cap the squad count at the roster size during the event briefing so nobody stalls mid-click. Read each squad aloud rather than sharing a long screenshot, because the format is friendlier to follow in voice chat and the silence around a tag lets people flag mistakes in real time. If you want the draw to feel ceremonial, use a second pass where each squad captain picks their second from a hat, but treat the first pass as the authoritative roster for matchmaking.
Finally, remember the limits of any random draw. Balanced headcount is not the same as balanced skill, compatible schedules, accessibility-aware pairings, or safe groupings. For casual lobbies, study sessions, icebreakers, and informal community nights, balanced random groups usually work well and remove the awkwardness of choosing people manually. For matches that affect ranking, paid roles, or someone else's wellbeing, layer human judgement on top of the generated squads rather than trusting a button alone.
For a faster walkthrough focused on filling a squad on the fly during a live match, see the companion guide on getting random teammates in Arena Breakout fast. Once you have your squads pasted back into ABI, the rest of the evening is just kit, callouts, and extraction timers.