VersionCheck-1.0

VersionCheck-v1.2.4 (2026-03-04)

Full Changelog Previous Releases

• fix: split RegisterComm from FireBatch, add 5s broadcast delay (MINOR 9)
  Two bugs causing "no responses received" when both clients have new code:
  1. RegisterComm was inside FireBatch, called at the same time as the
     broadcast. If another player's VC10_REQ arrived during the startup
     window (before FireBatch ran), we were not yet registered to receive
     it and silently missed it.
     Fix: RegisterComm now happens immediately at PLAYER_ENTERING_WORLD
     so incoming broadcasts are never missed.
  2. FireBatch was called directly from PLAYER_ENTERING_WORLD with no
     delay. The GUILD addon message channel is not guaranteed to be fully
     available at that exact moment in Classic Era - the broadcast was
     going out into nothing.
     Fix: 5s C_Timer.After delay before the broadcast only (RegisterComm
     still happens immediately).
• revert: move diagnostic prints back behind debug flag (MINOR 8)
• diag: add always-on prints for broadcast send and response receive (MINOR 7)
  Unable to diagnose "no responses" without visibility into whether the
  broadcast is going out and whether responses are arriving. Added two
  non-debug prints:
  • "[VersionCheck] Sending version check broadcast for N addon(s)."
    confirms FireBatch actually sent the GUILD message
  • "[VersionCheck] Response received from <sender> for <addon> v<ver>"
    confirms RSP whispers are arriving and being stored
    These will be removed once the flow is confirmed working.