Sensible Telemetry Data

[GPeaky]

Divide F1PacketBatching and F1PacketCaching into 2 sections, one for general data and one for sensitive telemetry. The sensitive telemetry would have an update rate of 10 Hz, while the general data would be at 1.43 Hz (700 ms).

The sensitive data section will have telemetry from the drivers of all teams. This would have to be restricted, and the server should only send data that corresponds to that team.

[GPeaky]

To do this, we need to change how we receive and handle packets internally. The ideal approach would be to have an index for each player, with all related information contained within it: telemetry, historyLaps, carStatus, CarDamage, CarMotion, and send customized packets to the client instead of exactly what we receive from F1. To implement this change, we need to rethink the caching system, batching, etc. Alternatively, we could add a section to the current system where everything is parsed as I explained earlier to have local information about which index corresponds to each player.

[GPeaky]

You could take the opportunity to send only the data that have changed.