From 7bab3b9d7c882e56d6f6f45e06f4b98f88e6e93d Mon Sep 17 00:00:00 2001 From: James Frowen Date: Fri, 3 Jul 2020 23:02:20 +0100 Subject: [PATCH] Update Deprecations.md --- doc/General/Deprecations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/General/Deprecations.md b/doc/General/Deprecations.md index 30f1be416..bdf39a590 100644 --- a/doc/General/Deprecations.md +++ b/doc/General/Deprecations.md @@ -49,7 +49,7 @@ Use `SyncList` instead. In classic UNet, QoS Flags were used to determine how packets got to the remote end. For example, if you needed a packet to be prioritized in the queue, you would specify a high priority flag which the Unity LLAPI would then receive and deal with appropriately. Unfortunately, this caused a lot of extra work for the transport layer and some of the QoS flags did not work as intended due to buggy code that relied on too much magic. -In Mirror, QoS flags were replaced with a "Channels" system. While the default transport, [Telepathy](../Transports/Telepathy.md), does not use channels at all because it's TCP-based, other transports, such as [Ignorance](../Transports/Ignorance.md) and [LiteNetLib4Mirror](../Transports/LiteNetLib4Mirror.mb), do support them. +In Mirror, QoS flags were replaced with a "Channels" system. While the default transport, [Telepathy](../Transports/Telepathy.md), does not use channels at all because it's TCP-based, other transports, such as [Ignorance](../Transports/Ignorance.md) and [LiteNetLib4Mirror](../Transports/LiteNetLib4Mirror.md), do support them. The currently defined channels are: - `Channels.DefaultReliable = 0`