ApplicantScout: LFG & Party Overlay

Warcraft Logs + RaiderIO overlay for LFG applicants and current party/raid rosters, helping you pick invites and read groups fast.

File Details

v0.1.6

  • R
  • May 16, 2026
  • 130.20 KB
  • 6
  • 12.0.7+1
  • Retail

File Name

ApplicantScout-v0.1.6.zip

Supported Versions

  • 12.0.7
  • 12.0.5

Changelog

0.1.6 - 16-May-2026 - Companion 0.2.4 live Mythic+ hardening

This paired addon + companion release improves live Mythic+ key detection, Warcraft Logs retry behavior, and fallback applicant sorting during active group listings.

Improved

  • The addon now uses the hosted owned-keystone activity and level when Blizzard exposes the active listing as generic Mythic+, so the companion can receive the real hosted key level instead of +0.
  • /apscout status now prints the active listing quest ID, resolved activity name, owned-keystone activity/level, whether that fallback is being used, and the final derived key level.
  • The companion now keeps sorting generic Mythic+ listings by visible M+ log evidence, with higher completed key levels ahead of low-key percentile spikes.
  • Temporary Warcraft Logs server errors and read timeouts are now retryable, so applicants are less likely to stay stuck as ? after transient WCL failures.

Fixed

  • Fixed hosted Mythic+ listings sometimes being treated as unknown +0 keys when the Blizzard active-entry payload did not expose the concrete key level.
  • Fixed WCL HTTP 5xx responses and network timeouts sometimes behaving like permanent applicant failures.

Notes

  • No wire-format changes since 0.1.4; the companion still supports ApplicantScout payloads through v4.
  • ApplicantScout remains the in-game data-source half of the setup; the desktop companion renders Warcraft Logs / RaiderIO context.
  • Recommended companion version: 0.2.4 or newer.

0.1.5 - 15-May-2026 - Companion 0.2.3 lifecycle hardening

This paired addon + companion release tightens the QR screenshot pipeline, update install flow, and live-panel suppression behavior.

Improved

  • The in-game addon now recomputes QR suppression immediately after hooking a newly loaded Blizzard info panel that is already visible. First-opening panels such as Encounter Journal, Achievements, Collections, or Settings should no longer leave the QR visible until a later event.
  • The companion now surfaces marker-bearing screenshot decode failures directly in the overlay footer as shot failed, with the file path and parse/CRC reason in the tooltip.
  • Companion Settings and tray update actions now share an update-in-progress state, so repeated clicks cannot start duplicate installer/download workers.

Fixed

  • Fixed corrupt ApplicantScout QR screenshots being deleted after a parse failure without any visible companion feedback.
  • Fixed stale screenshot watcher signals after changing the Screenshots folder; old-path snapshots and clears are ignored after a replacement watcher becomes active.
  • Fixed no-system-tray sessions so the companion does not disable last-window-close quitting when no tray control surface exists.
  • Fixed pending overlay geometry saves being lost on tray/control quit paths immediately after moving or resizing the window.

Notes

  • No wire-format changes since 0.1.4; the companion still supports ApplicantScout payloads through v4.
  • ApplicantScout remains the in-game data-source half of the setup; the desktop companion renders Warcraft Logs / RaiderIO context.
  • Recommended companion version: 0.2.3 or newer.

0.1.4 - 15-May-2026 - Companion 0.2.2 scoring and update flow

This paired addon + companion release focuses on making Mythic+ fit scoring more trustworthy and making companion updates easier to notice and install.

Changed

  • Reworked the companion's Mythic+ fit formula so relevant Warcraft Logs bracket performance is the primary signal.
  • Key level, same-dungeon evidence, profile consistency, and RaiderIO still matter, but they no longer turn weak logs into a good-looking score.
  • Sparse coverage is now treated as weaker evidence instead of a free score bonus.
  • Low-key farm parses no longer inflate scores for much higher hosted keys.
  • Very high-key evidence still helps, but low parses at very high keys are bounded so they do not look better than they should.
  • Fit labels now line up with the visible WCL-style color bands:
    • 0-49: RISK
    • 50-69: OK
    • 70-84: FIT
    • 85+: TOP

Improved

  • The companion update install action now uses a clearer title-bar download icon.
  • When the companion starts with WoW and finds an installable update, Settings can open with a direct update prompt instead of staying quietly hidden.
  • Self-updates now return the user to the visible companion Settings flow after installing.

Fixed

  • Fixed cases where applicants with all-grey or mostly-grey Mythic+ logs could show as blue or overly positive.
  • Fixed high current or main RaiderIO from rescuing weak WCL evidence into an inflated Mythic+ fit.
  • Fixed poor extra dungeon logs accidentally reducing sparse-evidence penalties.
  • Fixed mixed-bracket cases where old low-key farm logs could distort the fit for the hosted key.
  • Fixed a visual contradiction where a blue-range numeric score could still be labelled RISK.

Previous paired update included

  • Added the compact Ko-fi support heart in companion Settings.
  • Added the in-app update install icon that appears only when a valid companion update is available.
  • Added companion version text to Settings and first-run window titles.
  • Refreshed the CurseForge overlay screenshot for the addon page.
  • Defaulted first-run Warcraft Logs data scope to Mythic+ only.
  • Simplified companion Settings: close hides to tray, full quit lives in the tray menu, and secondary actions moved into a cleaner footer/menu layout.
  • Matched Mythic+ parse colors to Warcraft Logs buckets.
  • Split group applicant rows into package fit and individual member fit so group score and player score are no longer visually mixed.
  • Hardened the updater repository target, installer metadata checks, installer error visibility, and duplicate install boundaries.
  • Fixed Test WCL status being overwritten by Saved.
  • Hardened Warcraft Logs cache, quota handling, stale worker lifecycle, and group scoring edge cases.

Notes

  • No Lua runtime or wire-format changes since 0.1.3.
  • ApplicantScout remains the in-game data-source half of the setup; the desktop companion renders Warcraft Logs / RaiderIO context.
  • Recommended companion version: 0.2.2 or newer.

0.1.3 - 15-May-2026 - Companion 0.2.0 release train

Changed

  • Refreshed the public addon release for the paired Applicant Scout Companion 0.2.0 release.
  • Updated public install copy to point users at the latest companion release without pinning a companion version in the addon README.

Notes

  • No Lua runtime or wire-format changes since 0.1.2.
  • ApplicantScout remains the in-game data-source half of the setup; the desktop companion renders Warcraft Logs / RaiderIO context.

0.1.2 - 14-May-2026 - Wago publishing

Added

  • Added Wago Addons release metadata and automated Wago upload support.

0.1.1 - 13-May-2026 - CurseForge publishing polish

Changed

  • Added CurseForge project metadata so automated uploads target the public ApplicantScout project.
  • Updated public copy to use stable companion release links and the current public addon/companion repository names.
  • Refreshed the marketplace logo to match the in-game applicant parse overlay.

Fixed

  • Fixed the Windows release workflow Lua compiler lookup used by tag preflight.

0.1.0 - 12-May-2026 - First public release

Added

  • Added the in-game ApplicantScout addon for Mythic+ applicant capture.
  • Added QR screenshot transport for Applicant Scout Companion.
  • Added support for grouped applicants, playstyle selection, QR movement, manual sync commands, and diagnostic status output.
  • Added optional RaiderIO main-score transport when RaiderIO exposes the data.

Notes

  • ApplicantScout requires Applicant Scout Companion for the external WCL/RaiderIO overlay.
  • The addon uses normal WoW screenshots for transport. It does not read memory, inject code, automate gameplay, or use chat messages as a data channel.