I wanted to make audio aid, something like second pilot warning you about stall etc,
however I didn’t find any information about vehicle’s weaponry or ammunition reserves in localhost/state nor /indicators.
Is there really no infomation about it there or i just didn’t find it?
If ammunition count and weapon state are not present in /state or /indicators for that vehicle, there is no documented generic localhost field that can be relied on for them. The localhost interface exposes only the telemetry selected by the client, and the available keys can differ by vehicle and mode.
For an accessibility/audio assistant, I would recommend:
- Treating missing keys as unsupported rather than trying to infer ammunition by reading memory or injecting into the client.
- Logging the complete JSON returned by /state and /indicators for several vehicle types to confirm which fields are consistently available.
- Building warnings only from exposed telemetry, such as speed, angle of attack or engine state, and clearly degrading when a field is absent.
- Submitting a focused feature request for read-only weapon-selection and ammunition fields if they are required.
A useful request should specify the minimum fields needed—for example selected weapon type, remaining rounds/rockets and reload state—and explain the accessibility use case. Avoid undocumented memory access or client modification, particularly with anti-cheat enabled.