Allow specifying Channel type with BufferLast parameter #581
Closed
Danon5
started this conversation in
Feature Request
Replies: 3 comments
-
I also agree that it should be reliable by default, even if no option to change it is given. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I agree it would make sense for the bufferlast to always send on reliable.
That's a super easy change I'll get it into next v3 and v4.
…On Sat, Dec 30, 2023, 3:25 PM Max Kratt ***@***.***> wrote:
I also agree that it should be reliable by default, even if no option to
change it is given.
—
Reply to this email directly, view it on GitHub
<#581 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGPJC3RCP6JXSBCYB76WGZDYMB2C7AVCNFSM6AAAAABBEJWHWGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TSOBQGM4TS>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Added in 4.0.7 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The BufferLast parameter for the ObserversRpc is cool, but the packet can be dropped since it gets sent on the same channel. This is pretty annoying for things like unreliable position updates. It would be very helpful if it was possible to set a custom reliability type for the buffered RPC. All that needs to be added is a
Channel BufferLastChannel = Channel.Reliable
variable into the ObserverRpc attribute.It should be reliable by default. I don't see why you would want to buffer an unreliable RPC just to have it be potentially dropped.
Beta Was this translation helpful? Give feedback.
All reactions