About Who Will Win? Create a Battle

Who Will Win? Create a Battle takes the oldest argument on any playground — who would win, this side or that side — and turns it into something you can actually settle. You assemble two forces from a roster of more than 300 objects, arrange them on a battlefield, press play and let the fight resolve itself. The units act on their own once the whistle blows; your work happens before the first punch, in what you picked and where you put it.

The roster is broader than a simple soldier list. Alongside fighters it holds vehicles, weapons, armor and battlefield furniture — barricades, props, terrain pieces — and characters can be equipped before deployment, so a spearman behind a wall and the same spearman in the open are effectively two different units. Developed by JustPlay and built in Unity for the browser, it also lets you lay out your own map rather than using a ready-made one, which means the arena itself is one more thing you control.

What makes it worth more than a few minutes is treating it as an experiment bench. Any matchup is a question with a testable answer: how many light fighters equal one armored one, does a vehicle beat the crowd that swarms it, is high ground worth two extra bodies. The method that pays off is the fair test — hold everything constant, change exactly one thing, run it again. Swap a weapon, nudge a wall, add a single unit to the losing side, and the next result tells you precisely what that one change was worth. Change three things at once and the result tells you nothing.

Repetition is part of the method, because outcomes are not perfectly deterministic. The same setup can swing on how the melee happens to tangle, so a matchup decided by one run is an anecdote and a matchup decided by five runs is evidence. That habit — rerun before you conclude — is the difference between players who collect explosions and players who end up with a working theory of the whole roster.

The game is filed under Sandbox and Strategy, and each label covers half of it: the sandbox is the freedom to test anything, the strategy is what accumulates in your head as the tests pile up. A light unlock loop feeds the bench — finishing a battle pays out rewards that open new objects, so the pool of testable questions keeps growing. It suits players who like knowing why something wins rather than just watching it win.

Tips for Who Will Win? Create a Battle

• Establish baselines with duels before building armies. One-against-one results are the reference points that make every larger matchup interpretable.
• Change exactly one variable per rerun — a weapon, a wall, a single extra unit. If two things changed, you cannot know which one moved the result.
• Run close matchups several times before trusting them. Fights are not perfectly repeatable, so one run is an anecdote and five runs are evidence.
• Test equipment separately from numbers. Arming a character changes what it is, so an equipped unit deserves its own duels before it joins a bigger trial.
• Use walls and props as variables, not decoration. The same two armies can trade wins depending on whether a barricade splits the approach.
• Keep test armies small enough to watch. Twelve units produce a fight you can read cause and effect in; eighty produce a scrum where the lesson is lost.

Did you know?

• The roster runs past 300 objects — characters, vehicles, weapons, armor and battlefield props — and characters can be equipped before deployment, which multiplies the effective unit pool well beyond the raw count.
• Developer JustPlay built it in Unity for the browser, with full camera control during battles: rotate, pan and zoom, so a fight can be inspected from any angle rather than watched from a fixed seat.
• Battles pay out rewards that unlock new objects, giving the sandbox a light progression spine that most pure simulators skip.
• You can build your own battlefield instead of picking a ready-made map, which makes terrain a player-controlled variable rather than a fixed condition.