0.3.0
Don't forget that the transport is still in preview state, so it may not be stable. Please report any bugs to me.
In version 0.3.0
- Stability Improvements and fix bugs related to connection state changes #13
- Improved support for UnityTransport 2.0 with versionDefines in Assembly Definition #13
- Fix the multiple client failure by in #12
In version 0.2.0
This version adds support for UnityTransport 2.0.
New FishyUnityTransport configuration have been added:
- DebugSimulator (UnityTransport 1.0 only) - Can be used to simulate poor network conditions.
- UseWebSockets (UnityTransport 2.0 only) - Per default the client/server will communicate over UDP. Set to true to communicate with WebSocket.
- UseEncryption (UnityTransport 2.0 only) - Per default the client/server communication will not be encrypted. Select true to enable DTLS for UDP and TLS for Websocket.
- ConnectTimeoutMS - Timeout in milliseconds indicating how long we will wait until we send a new connection attempt.
- MaxPacketQueueSize - The maximum size in bytes of the transport send queue.
- MaxSendQueueSize - The maximum amount of packets that can be in the internal send/receive queues
- MaxConnectAttempts - The maximum amount of connection attempts we will try before disconnecting
- DisconnectTimeoutMS - Inactivity timeout after which a connection will be disconnected.
- Many overloads for methods SetRelayServerData() and SetConnectionData().
Breaks:
- FishyUnityTransport.UseRelay replaced by FishyUnityTransport.Protocol
- FishyUnityTransport.RelayServerData setter removed. Use FishyUnityTransport.SetRelayServerData() methods