DIM

1.11.7 - 2026-04-29

Safety

• SendBNetTell hook never trusts an unresolved K-token. 1.11.5 fell back to BNet_GetBNetIDAccount(token) when BNTokenFindName couldn't resolve the K-token; if that returned an ID, DIM trusted it. The mapping is almost certainly correct, but "almost" isn't good enough for routing a private message. Now: if target is a K-token AND BNTokenFindName can't resolve it, DIM bails. The whisper still goes through Blizzard's path (we hooksecurefunc — Blizzard's logic always runs); we just don't open a DIM tab. Trade-off: in the rare case where a token can't be resolved, the user falls back to /w Friend … or the recents panel.

Fixes

• SendBNetTell decline now prints a notice. Previously the hook bailed silently when it couldn't safely resolve the recipient (unresolvable K-token, missing bnetID, or missing battleTag), so the user just saw "Whisper from Contacts didn't open DIM" with no signal. Now DIM prints [DIM] Couldn't open whisper tab — <why>. Blizzard's chat will still send. to the chat frame, with a hint to use /w <BattleTag> or the recents panel.