GuildWatch

Polish round + diagnostic instrumentation after a multi-character sync test surfaced a stuck-comm scenario we couldn't see into clearly with just incoming-message debug. ### Fixed - **Self-pin no longer drawn on the world map or minimap.** Was covering the standard player-position arrow on the minimap; redundant on the world map. `/gw roster` still lists you with current coords. - **`/gw version` and `/gw status` now report the correct version.** The `VERSION` constant in `Core.lua` was hard-coded to `0.0.1` and didn't bump with the `.toc`. ### Internal - **Outgoing-message debug logging.** Every `SendCommMessage` site now emits a `sent: via ` line when `/gw debug` is on, mirroring the existing `recv:` lines. Lets future diagnostics distinguish "broadcast never left the client" from "broadcast hit the wire but didn't arrive." - **Defensive prefix re-registration in `OnEnable`**. Calls `C_ChatInfo.RegisterAddonMessagePrefix("GW1")` directly in addition to AceComm's internal registration. Cheap insurance against the Classic-client edge case where addon-channel subscription gets into a stuck state after `/reload`. ### Known limitation If a guildmate can't see your data after a `/reload`, have them log out to character select and back in. We saw one case during testing where `/reload` alone left the sending client unable to deliver addon-channel messages, while a full character-swap resolved it. v0.0.3's defensive prefix re-registration may help; the new `sent:` debug lines will confirm whether the broadcasts were attempted.