Back to changelog
vAOMS v0.5.4-beta

A Picture of the Month contest, network verification you can see and trust, one-click fixes for unlinked VATSIM/IVAO accounts, and weekly Discord digests.

What's new

  • Picture of the Month

    A monthly screenshot contest, opt-in per airline under Settings → Features. Pilots submit from the new Picture of the Month page in the sidebar or by posting in a dedicated Discord channel, and vote with the 📷 reaction — web voting can be turned on as well. Staff get a review queue and a new "Manage Picture of the Month" permission, and entries can be held for approval before pilots see them. Cycles open on the 1st and close at 23:00 UTC on the last day of the month on their own, and the winner rides the pilot dashboard banner for the whole of the following month. Discord submissions are mirrored in as they are posted by a background listener, with a short catch-up poll for anything missed while it was down. The Discord channel is chosen on the Discord Settings page.

  • The network audit shows how each flight was confirmed

    A new Basis column marks every flight as Feed — matched against the live VATSIM or IVAO data feed while airborne — or ACARS — flown through an ACARS client and declared on the network, but never matched to the feed, which usually means an unlinked network ID. The summary cards now separate feed-verified flights and pilots from every flight recorded, and the header copes with airlines that fly under more than one callsign prefix.

  • Nudges when a network account is not linked

    Choosing VATSIM or IVAO on a booking without that account linked now warns that the flight may not be verified and links straight to the connect flow. The Integrations page goes further: when the feed has seen one of your callsigns flying under a CID or VID you have not linked, it shows "Seen as CID … on a recent flight" and pre-fills the connect form, so a single click ties the account to your profile.

  • Backfill command for historical network verification

    A new network:backfill-verification command re-links older ACARS pilot reports to their VATSIM and IVAO sightings and fills in the verification state for flights recorded before the current logic existed.

What's improved

  • The Discord VA digest can run weekly

    With the digest cadence set to Weekly, the digest now covers the last seven days rather than only the previous calendar day — approved pilot reports, flight time and active-pilot counts all follow the wider window.

  • Feed sightings keep an audit trail

    The VATSIM and IVAO feed polls now record the observed CID or VID and a first-seen timestamp for every sighting, so a flight can still be attributed to a pilot who linked their account only after flying it.

  • Scheduled route length reads as HH:MM everywhere

    The timetable, the booking screen and the focused-flight page all show a route's scheduled length as HH:MM. Routes brought in through an import stored the length as a raw number of seconds and were showing that number unformatted.

What's fixed

  • Corrected the grammar in the network audit page description.