GuildWatch

Three fixes: guild rows that quietly stopped updating, a heroic key that counted as attuned before it actually worked, and one of the two reasons the guild bank kept announcing changes it had not made.

Fixed

• Guildmates' attunement rows could freeze for days. GuildWatch asks the guild for a catch-up when you log in, but it skipped that request whenever any single guildmate's data was recent. One person playing daily was enough to stop everyone else's rows from ever refreshing, so a guildmate who updated the addon or finished a chain could stay frozen at old progress indefinitely. It now tracks when you last asked, and asks again after six hours.

• /gw resync now asks as well as tells. It only ever pushed your own data out, which could never repair an out-of-date row you were holding for somebody else. That was exactly the case with no manual fix. It now does both, so if a guildmate looks stale you can settle it on the spot.

• A Communal heroic key no longer counts as attuned on its own. The account-bound Communal keys need Friendly with the faction before they work, but simply holding one marked the key as done whatever your reputation. Since the usual way to get one is to buy it on a main and mail it to an alt, the character most likely to be affected was the one least likely to be Friendly yet. Those characters now show the key in hand with Friendly still to go, and the reputation target on that step drops from Revered to Friendly, because Revered is only needed to buy the key, not to use it.

• The guild bank no longer counts scan time as part of its contents. Bank log times are reconstructed from the game's "how long ago" values, so they shifted on every scan even when nothing had changed, and the fingerprint that tells guildmates "my copy differs from yours" included them. Every scan therefore looked like new activity. This removes one of two reasons the bank re-announces itself. A second cause, where log rows are dropped and re-added between scans, is still being worked on.

Internal

• /gw bankscan no longer prints a transaction count before it has requested any, which always read 0 on a fresh session and looked like a failure.
• The bank's debug output now distinguishes an unread balance from a real zero instead of showing both as 0.
• The five account-bound Communal key item IDs are now also listed as debug probes, so a character holding one can confirm them against the client.