The server’s answer to one chat send (SendChitChatMsgReply), raised by IChat.SendResult — for sends made through IChat.Send/SendSticker AND sends the player makes in the game’s own chat box (see ViaFramework). The send cooldown is SERVER-driven (no client config): World/Current reply with a cooldown end (observed 5 s), Party/Guild reply with none.
The server’s answer to one chat send (SendChitChatMsgReply), raised by IChat.SendResult — for sends made through IChat.Send/SendSticker AND sends the player makes in the game’s own chat box (see ViaFramework). The send cooldown is SERVER-driven (no client config): World/Current reply with a cooldown end (observed 5 s), Party/Guild reply with none.
True when the send was issued through IChat.Send/SendSticker (by some plugin); false when the player sent it from the game’s own chat box (the game shows its own error tip for those).
Framework-made code (never a server one): the send NEVER LEFT THE CLIENT — no live chat connection, an unsupported target, or the send threw. Ok is false and ViaFramework true. Raised before IChat.Send/SendSticker returns when they are called on the main thread (so a chat box can keep its draft instead of clearing it), otherwise on the main thread right after. No server reply follows.