Skip to content

This check prevents fragment reconstruction for unreliable messages. Is this intentional? #9

@niuk

Description

@niuk

https://github.com/KillaMaaki/ReliableNetcode.NET/blob/c5a7339e2de70f52bfda2078f1bbdab2ec9a85c1/ReliableNetcode/Utils/IO/PacketIO.cs#L116-L117

The check here will fail if the channel ID written into the most significant two bits of the prefix byte at https://github.com/KillaMaaki/ReliableNetcode.NET/blob/c5a7339e2de70f52bfda2078f1bbdab2ec9a85c1/ReliableNetcode/ReliablePacketController.cs#L302 is anything other than Reliable. But when I changed the condition to allow any channel ID and sent dozens of unreliable greater-than-FragmentThreshold-sized messages per second, everything still seemed to work. Is there a reason that this feature is disabled?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions