Skip to content
Version 2.32.0
↓ Get the launcher

ChatSendResult structure

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.

public struct ChatSendResult : IEquatable<ChatSendResult>
parameter description
Channel Channel the send went to.
Ok True when the server accepted the message (ErrorCode = 0).
ErrorCode The game’s EErrorCode; 0 = accepted. ErrorTooFrequent = sent before the channel’s cooldown ended.
CooldownEndUtc When the channel may be posted to again (server clock, whole seconds), or null when the reply carried no cooldown.
name description
ChatSendResult(…) 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.
Channel { get; set; } Channel the send went to.
CooldownEndUtc { get; set; } When the channel may be posted to again (server clock, whole seconds), or null when the reply carried no cooldown.
ErrorCode { get; set; } The game’s EErrorCode; 0 = accepted. ErrorTooFrequent = sent before the channel’s cooldown ended.
Ok { get; set; } True when the server accepted the message (ErrorCode = 0).
ServerTimeUtc { get; set; } The server time stamped on the accepted message (show_msg.timestamp), or null when the reply carried none (typically a rejected send).
ViaFramework { get; set; } 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).
const ErrorNotSent 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.
const ErrorTooFrequent ErrChatSendCdNoEnd — “Message too frequently, please try again later”.