DisconnectReason

Remarks

Reported from the point of view of the half that observes it, so the same disconnection is Requested on the side that asked and RemoteRequested on the side that was told. A game that reconnects on Timeout but not on Kicked needs exactly that distinction, and a single "disconnected" event without it is what makes reconnect logic guesswork.

Fields and properties (7)

• Requested

  This side asked for it — StopClient, or a server disconnecting a client.

• RemoteRequested

  The peer asked for it.

• ServerStopped

  The server stopped listening, taking every connection with it.

• Kicked

  The server closed this connection specifically, and the client is the one told.

• ConnectionRefused

  Nothing was listening, or the listener refused the connection.

• Timeout

  The peer stopped answering.

• TransportError

  The transport itself failed — a socket error, a relay that went away.

Used by (20)

• CountingEventsVixen.Net.Fuzz
• EventRecorderVixen.Net.Tests
• ITransportEventsVixen.Net
• InjectingTransportVixen.Net.Fuzz
• LocalTransportVixen.Net.Transport.Local
• LocalTransportTestsVixen.Net.Transport.Local.Tests
• NetworkSessionVixen.Net
• PeerVixen.Net.Transport.WebSocket
• QueuedVixen.Net.Transport.Local
• QueuedVixen.Net.Transport.Udp
• RecordedEventVixen.Net.Tests
• ReentrantPollerVixen.Net.Transport.Local.Tests
• RouterVixen.Net.Transport.Composite
• SessionTestsVixen.Net.Tests
• TransportConformanceVixen.Net.Tests
• UdpReliabilityTestsVixen.Net.Transport.Udp.Tests
• UdpTransportVixen.Net.Transport.Udp
• WebSocketTransportVixen.Net.Transport.WebSocket
• FakeBuildVixen.Editor.Debugger.Tests
• RemoteInspectorClientVixen.Editor.Debugger