The map system should be an easy way of defining various zones with different actions that influence the gameplay.
Such zones could be safe-zones, respawn zones, damage zones, capture regions etc.
Each zone would have a unique identifier and a type, as well as an arbitrary shape (circular, convex polygon, potentially concave polygon).
Each map would contain a list of zones, as well as a definition of types, which then dictate what team is influenced how by the zone, how it should be displayed, etc.
It would also contain information about how to convert GPS data into map x and y coordinates.
Each player's app would handle identifying which zone the player is currently in, and simply send the zone-id and zone type back to the server, thereby offloading those calculations.
To determine:
How flexible the system should be. Should zones be configurable (i.e. the respawn speed, damage speed etc.), or should custom zone types be made for this, simplifying things but potentially making it harder to generate complex games?
What data to store. Is a per-player list of zone-id's enough, or a per-zone-id list of contained players? Both have their own use-cases.
The map system should be an easy way of defining various zones with different actions that influence the gameplay. Such zones could be safe-zones, respawn zones, damage zones, capture regions etc. Each zone would have a unique identifier and a type, as well as an arbitrary shape (circular, convex polygon, potentially concave polygon).
Each map would contain a list of zones, as well as a definition of types, which then dictate what team is influenced how by the zone, how it should be displayed, etc. It would also contain information about how to convert GPS data into map x and y coordinates.
Each player's app would handle identifying which zone the player is currently in, and simply send the zone-id and zone type back to the server, thereby offloading those calculations.
To determine: