VersionCheck

VersionCheck-1.0 — Cross-Guild Addon Version Check Library

VersionCheck is a shared LibStub library that other addons use to perform a single batched cross-guild version check at login. If a guildmate is running a newer version of an addon than you are, you get a one-time popup telling you to update. That's the entire end-user surface.

Do you need this addon?

Probably not directly. You need VersionCheck-1.0 installed only if another addon you use depends on it. CurseForge installs it automatically as a dependency when you install one of those addons. If you're not running any of these, you can safely uninstall VersionCheck and nothing else will be affected:

• TOGProfessionMaster
• Grouper
• TOGBankClassic
• FastGuildInvite
• (and any other addon whose .toc lists ## Dependencies: VersionCheck-1.0)

What you'll see in-game

• A small popup at most once per session, per outdated addon, telling you the highest version any guildmate is running and where to download it (CurseForge). Click OK and it's gone for the session.
• No popups mid-combat. If the check completes while you're in a fight, the popup waits until combat ends.
• No popups for the same version twice. If a host addon re-triggers a version check later in the same session (some addons do this periodically), you won't see the same alert again unless a strictly-newer version has surfaced.
• If GreenWall is installed and you're in a confederation, the check reaches every linked co-guild — not just your literal <guild> — so you'll catch updates from a wider pool of guildmates.

Slash commands

• /vcd — toggle debug logging
• /vcdon — enable debug logging (verbose log to chat)
• /vcdoff — disable debug logging

Debug state persists across /reload. You'll only ever need these commands if a host addon's author asks you to capture a debug log for a bug report.

For addon developers

Full integration documentation is in the README.md that ships with the addon. Short version:

1. Add ## Dependencies: Ace3, VersionCheck-1.0 to your .toc.
2. Call VC:Enable(self) from your addon's init code (where self is your AceAddon object, or a wrapper with :GetName() and .Version).
3. Make sure your .toc has a ## Version: line.

Enable is the only entry point. Get the library with LibStub("VersionCheck-1.0", true) and guard on VC.Enable. Three names that consumers reach for do not exist and never have: VC:RegisterCheck(...), the global VersionCheck, and VC.version / VC.minor. If your bootstrap tries RegisterCheck first and falls back to Enable, delete the first branch — it only works because it is dead, and it would silently stop your addon registering the day that name is defined.

If you embed VersionCheck-1.0 in your addon (rather than declaring it as an external dependency), also add ## SavedVariables: VersionCheck10_DebugEnabled to your .toc so end-users' /vcdon survives /reload.

Requirements

• Ace3 installed as a separate addon. VersionCheck does not embed Ace3; it uses the global AceComm-3.0 and AceSerializer-3.0 you already have if you run any Ace-based addon.
• Optional: GreenWall for confederation reach.

Recent Updates

v1.3.1 (2026-08-13)

• No longer shows as out of date on Retail. The supported-version list still named Retail 12.0.7, so after the 12.1.0 patch the addon list flagged VersionCheck as out of date. Refreshed. Nothing else changed — no new behaviour, no new settings, and the other supported clients are untouched.

v1.3.0 (2026-08-04)

• Fixed: some addons were never reported as out of date. When an addon registered with VersionCheck by name rather than by handing over its addon object, VersionCheck answered other players' version checks with "unknown" instead of that addon's real version. Because "unknown" sorts below every real version number, those addons could never be the newest version anyone saw — so nobody was ever prompted to update them, no matter how far behind they were. They now report their real version, read from the addon's own version info.
• Fixed: repeated "No version responses received" messages in chat. If nobody else in your guild ran one of your VersionCheck-using addons, VersionCheck printed a line to your chat window saying so — once per addon, and again every few minutes for the rest of your session. That is the normal situation for a less common addon and there is nothing you can do about it, so the message is now only shown when you turn debugging on with /vcdon.
• Marked compatible with the current Retail, Anniversary and Mists clients. The supported-version list had fallen behind — it stopped at Retail 12.0.1, Anniversary 2.5.5 and Mists 5.5.3, so the addon list was flagging VersionCheck as out of date on 12.0.7, 2.5.6 and 5.5.4. Refreshed, with the superseded duplicates dropped. Existing targets are unchanged. No behaviour change.
• No other user-visible changes. This release also adds an offline test suite covering the whole library, which is what found the fixes above. It is a development tool and is not part of the download.

v1.2.9 (2026-07-28)

• Marked compatible with the current Classic Era client. No behaviour changes — this release only stops the addon list from showing VersionCheck as out of date after the latest client patch.

v1.2.8 (2026-05-23)

• Fixed login crash on current Classic Era clients. A recent WoW client patch removed the global GetAddOnMetadata function VersionCheck was calling at login, causing an attempt to call a nil value error. VersionCheck now uses the new C_AddOns.GetAddOnMetadata entry point when available and falls back to the old global on older clients.

v1.2.7 (2026-05-23)

• No more repeat "you're out of date" popups every 10 minutes. Addons that re-check periodically (e.g. TOGProfessionMaster's scanner) were re-popping the same alert each cycle. Once you've seen the popup for a given version, you won't see it again unless a strictly-newer version surfaces.
• Popups now wait for combat to end. If the check completes while you're in a fight, the popup is deferred until PLAYER_REGEN_ENABLED fires. Multiple addons queued during the same fight all drain together when combat ends — none get lost.
• /vcdon now actually persists across /reload. Previously, in setups where both a standalone VersionCheck install AND an embedded copy in a host addon coexisted, a race between the two LibStub registrations meant the debug flag's cached value was read before the SavedVariable had been loaded, so the toggle silently reverted to off on every reload. The debug flag is now read lazily on every access; the SavedVariable's value takes effect immediately regardless of load order.
• GreenWall confederation reach (optional). If you have GreenWall installed and bridged, version checks now reach every linked co-guild, not just your literal <guild>. No setup required — VersionCheck detects GreenWall automatically. If you don't have GreenWall, nothing changes; the AceComm GUILD path is unaffected.

Older patch notes are in the addon's CHANGELOG.md file (ships with the addon).

Credits

Pimptasty — maintainer.

Source

Released under the MIT license. Bug reports and feature requests welcome on the CurseForge page.