Hi everyone / moderation team,
I’m planning a small companion tool for Ground Realistic Battles and would like to
check its compliance before I invest time in building it.
The tool reads ONLY from the official localhost HTTP API (port 8111) that the game
exposes while a battle is running. It does not read game memory, inject code,
modify game files, or hook into DirectX/OpenGL or any anti-cheat path.
Planned features:
- A separate window / second-screen map that shows information already visible on
the in-game minimap: my own position, friendly positions, and currently spotted
enemies (i.e. only enemies that the official minimap already reveals). - Distance labels (in meters) from my vehicle to each currently spotted enemy,
computed from the map bounds returned by /map_info.json and the normalized
object coordinates from /map_obj.json. - Detection of my own squad marker (the yellow marker I place myself) on the map.
- A log that parses kill/death messages from /hudmsg to count which vehicle types
(e.g. SPAA) appeared in the kill feed during the battle.
I’ve read the thread “Tools using data provided on port 8111”, where the moderation
team stated that displaying localhost data as overlays is generally considered fine
and not a bannable offense, while enemy markers presented as a compass/ESP-style
overlay in markerless modes would cross the line.
My questions:
- Are the features above considered acceptable use of the 8111 API?
- Specifically, is computing and displaying the distance to currently spotted
enemies acceptable, or is that treated as information that gives an unfair
advantage? - Does the official map data (map_obj.json) include the player-placed squad
marker, and may a tool display it? - Is there any official policy statement or document I can reference when
deciding what to build?
Thank you for your time. I’m happy to provide more details or source code if that
helps.
Best regards