You were redirected here from sockchat:s2c:packet-3.

S2C Packet 3: User Remove

Informs the client that a user has left the server.

Format

Index	Type	Description
0	`3`	User Remove packet ID
1	string	User ID of the removed user
2	user name	User name of the removed user
3	string	Reason string as to why the user was removed, listed below
4	timestamp	Timestamp at which the user was removed
5	string	Message ID associated with this event

Reason strings

String	Description
`leave`	User gracefully left, e.g. “xyz logged out”.
`kick`	User got banned, kicked or otherwise unvoluntarily had their session terminated, e.g. “xyz has been kicked”.
`flood`	User got kicked for exceeding the flood protection limit, e.g. “xyz has been kicked for spam”.
`timeout`	User lost connection unexpectedly after not sending pings in a timely fashion, e.g. “xyz timed out”. ¹⁾

Examples

A user with ID 181 named saikuru0 leaving at Sunday, 13 April 2025 22:18:53 GMT with message ID 39988514246140:

3\t181\tsaikuru0\tleave\t1744582733\t39988514246140

A user with ID 11 named Satori being kicked at Sunday, 13 April 2025 22:24:37 GMT with message ID 39988602271681:

3\t11\tSatori\tkick\t1744583077\t39988602271681

S2C Packet 1.#: User Add - A new user is added to the current context.
S2C Packet 10: User Update - A user is updated.
S2C Packet 7.0: Context User List - List of users already present in the current context.
S2C Packet 5.0: Channel User Add - A user has joined the channel.
S2C Packet 5.1: Channel User Remove - A user has left the channel.

¹⁾

The original PHP Sock Chat implementation did not support this and was added later by SharpChat. Support could be added by modifying the language file, so we’re letting this slide.

Railgun

Table of Contents

S2C Packet 3: User Remove

Format

Reason strings

Examples

See Also