Category: RemConClient

Panic category used by Rem Con server to panic the client.

0	The client side has passed an illegal IPC value.
1	The client is already connection-oriented.
2	The client has called `GoConnectionless`, `ConnectBearer` or `DisconnectBearer` when the session is not connection-oriented.
3	The client called `GoConnectionOriented` with an unknown bearer UID. The given UID is not a known implementation of the bearer interface.
4	The client requested Send when there was already a Send outstanding on this session
5	The client requested Receive when there was already a Receive outstanding on this session.
6	The client has not had their type set.
7	The client has attempted to set the type of the session when it has already been set.
8	A client has used a bad or wrong session type.
9	A client tried to open a target session when there is already one in that client process.
10	A badly-formed descriptor or other lump of data was sent from the client side
11	The client requested NotifyConnectionStatusChange when there was already a NotifyConnectionStatusChange outstanding on this session.
12	The client has committed one of a number of abuses of the `ConnectBearer` or `DisconnectBearer` interface.
13	The client has tried to send a response to a command which does not exist in the logs as having been delivered to that client.
14	RRemConTarget::RegisterInterestedAPIs() is called on an undefined session.The client panics for misusing this API.
15	They client side has sent a corrupt set of supported operation ids.
16	RRemConTarget::RegisterInterestedOperations() is called on a non-target session
17	The client has not had their features set.
18	The client has tried to register the same interface in multiple sessions.
19	The client has tried to register different player information in multiple sessions.
20	This panic code indicates a programming error in RRemCon::GetConnections.