Explanation
A closer look at selected parts of STORM. Pick a topic in the contents and jump straight to it.
First launch after installation
The first launch lets you create a standalone game (without features such as setting up missions, etc.) or simply join a game.
Own game (Single)
A quick game with no organizer — for a group of friends.
- Anyone can create the game without an organizer; the game expires after 36 hours.
- The creating player picks “Own game (Single)”, enters an Access code and their name, and confirms “Create and show QR”.
- Everyone else joins via the join link or QR code shared by whoever created the game.
- The game has a single faction and you cannot create missions or groups in it — it is meant for playing with friends.
Join a game
Joining a game created by an organizer or by someone via Own game (Single).
- The event is created either by an organizer — who sets the number of factions, groups and missions/tasks.
- …or the game is created via the “Own game (Single)” option.
- The player then taps “Scan QR” and scans the code. Or taps a join link from email / WhatsApp / Facebook, etc., shared by the game creator.
Player aggregation on the map
At a larger event there can easily be fifty or more players in a small area. Rendering fifty separate dots needlessly strains the phone, the map slows down, and the commander gets nothing useful out of that clutter anyway — what they mainly need to know is how many people are where.
That is why STORM can aggregate positions: instead of individual dots, the player marked as the group commander carries a single marker with a number showing how many players are in their team.
Example: Five groups of ten players = fifty people. Without aggregation, fifty dots on the map. With aggregation, five markers, each showing “10”. The commander instantly sees there are fifty players on site, the map stays readable and rendering stays smooth.
What you need for it
For a team to collapse into a single marker on the map, two things must be in place:
- Mark the team commander On one player in the team, open Settings → Player in the app and tick “Commander” in the “TEAM” section. That player then represents the team on the map.
- Turn on the map filter On the map open Filter and, under “Team display”, tick “Commanders only”. In each team you then see only the commander with a numeric badge; your own position is always visible.
What the “Team player count” field does
The number shown on the commander is driven by the “Team player count” field in Settings → Player:
- 0 = automatic count: only real players who are alive and online (with the app running) are counted. The commander on the map then carries a number equal to the sum of active players.
- A specific number (e.g. 10) = manual override: the commander shows exactly this value regardless of how many people actually run the app. Handy when a team has ten people but only one or two have the app — the map still shows “10”.
- The value applies to all team members; you only set it once.
What you gain
- Less map-rendering load — smoother operation even on weaker phones.
- A clearer map — the commander sees force distribution, not a cloud of dots.
- The number on the marker matches the current player count of the group.