Settings & Help
Display preferences and the integration contract for a future authorised PTFS telemetry source.
Telemetry connection
NOT CONNECTEDNo authorised source configured
The app is not reading Roblox aircraft or private/VIP servers. Realtime delivery is available, but it is not itself an aircraft feed or proof of authorisation.
Secrets belong in backend Secrets only. Public realtime messages and shared storage cannot establish a trusted source.
Connection state rules
- NOT CONNECTED
- No authorised feed or no aircraft received.
- LIVE CONNECTED
- Trusted, validated aircraft received within 30 seconds.
- STALE DATA
- Last trusted observation is older than 30 seconds.
- CONNECTION ERROR
- Trusted feed transport or validation failed.
Display preferences
Saved on this device. Map layers can be changed directly on the radar.
Payload validation
LOCAL ONLYCheck a prospective feed’s structure. Validation does not authorise a source, store data or enable live tracking.
Required aircraft fields
id, callsign, x, y, heading type, username, flightNumber origin, destination, altitude, speed verified, alert, phase, squawk, route[] Missing optional values: null x: 0–1050 · y: 0–730 heading: 0–359.99° altitude: ft · speed: knots
Operator help
How do I use the radar?
Drag the map to pan. Use + and − to zoom, the crosshair to reset, and layers to toggle labels, routes and grid. Select an aircraft to inspect its information. Search matches callsign, type, username and flight number.
Does this track my PTFS VIP server?
No. This stage has no authorised Roblox telemetry source. Private/VIP access must be verified before any live-tracking claim is made.
What is real and what is demo data?
Aircraft positions, pilot names, routes, verification and alerts are labelled sample data. Published community flight plans are real public submissions saved in built-in storage. The device watchlist and practice checklist are local preferences.
Why do some fields say unavailable?
Information that was not supplied is not inferred. Actual pilot identity, telemetry timestamps and authority require a verified source.
What should be added next?
Source authorisation and protected telemetry ingestion first; then authentication, controller roles, flight verification, clearance acknowledgements and a durable operational audit trail.