Skip to content
This repository was archived by the owner on Aug 3, 2026. It is now read-only.

v1.9.1 — Single-Target enforcement + whisper-spam fix

Choose a tag to compare

View all tags
@Defcons Defcons released this 25 May 10:05
· 4 commits to main since this release
v1.9.1
54fd33b

v1.9.1 — major release. Single-Target-Only dummy enforcement + a chat-spam bugfix that was hitting users in the wild.

1. Single-Target-Only dummy parses (Project Epoch)

epoglogs.com recently introduced a server-side rule (v0.86.6+) that rejects combat-log uploads where you damaged 2+ training dummies in one pull. The leaderboards at epoglogs.com/dummy-stats are single-target only — Expert's (L60) vs Heroic (L63) dummies have very different EHP curves, and AoE rotations would pollute the rankings.

The addon now mirrors that rule locally so you find out before you upload, not after.

What you'll see in-game:

  • Dummy frame title now reads EpogLogs · Dummy Parse · Single-Target Only (the trailing tag is greyed so it sits as a quieter subtitle).
  • The moment a second dummy GUID appears in the combat log, a red warning appears under the state badge: "Multi-target damage detected — fight invalidated".
  • The fight is flipped to INVALID in real time — the end-of-fight verdict matches what SaveFightRecord does, no "showed CLEAN locally but rejected on upload" surprise.
  • On Project Epoch realms, the fight is not saved at all to dummyFights[] so it doesn't pollute your history. A red chat line + popup explain why.

Realm-gated. Only Project Epoch realms (Project Epoch / Epoch / ProjectEpoch) enforce the skip. CoA-style realms where AoE training is valid content keep the save but tag the record with aoe=true for offline analytics. Override list in EpogArmoryDB.skipAoERealms for any exact-string mismatch.

2. Fix: "No player named X" chat-spam

The bug. Some users were seeing dozens (up to 200) lines of No player named 'X' is currently playing. system errors flooding their chat. Reported to me via Onrehab → me: "this happens a lot and i think it's from your armory addon when it's trying to communicate with an offline player".

Root cause. When another player asks your client for a sync (background catch-up of gear data), your client queues up to 200 WHISPER addon messages back to them — one per gear set. If they log off mid-burst, every remaining chunk fires the system error.

Fix. Each WHISPER send now checks if the target is still online before firing. If they're offline, the chunk is silently dropped AND all remaining queued chunks targeting that same offline player are drained in one pass. Zero spam, zero behavior change for online targets, zero protocol impact.

Backward Compatibility

  • New SavedVariables fields are additive: EpogArmoryDB.dummyFights[].aoe, .aoeExtraDummyCount, .aoeExtraDummyName (only set on AoE-tagged records).
  • EpogArmoryDB.skipAoERealms is optional override; absent means use the built-in Project Epoch list.
  • Wire format unchanged — no mesh-protocol impact. Mixed-version meshes work fine.
  • Mesh peers running v1.8.x will receive the auto-update notification pointing here.

Install

  1. Download EpogArmory.zip below.
  2. Extract into World of Warcraft\Interface\AddOns\. You should end up with Interface\AddOns\EpogArmory\ containing five files: EpogArmory.toc, EpogArmory.lua, EpogArmoryUI.lua, EpogArmoryDummy.lua, EpogArmoryDungeon.lua.
  3. /reload (or restart the client) — no new files in this version, so /reload is sufficient.
  4. Verify with /epogarmory status or just open the dummy frame on your next training dummy session.
Assets 3
Loading