Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code
My View | View Issues | Change Log | Roadmap | All Projects Issue Support Ranking | Rules | My Account
  

View Revisions: Issue #4142 [ All Revisions ] [ Back to Issue ]
Summary 0004142: Support the Zandronum's segmented server query response
Revision 2023-06-25 13:46 by Zalewa
Description Zandroum is about to gain support for segmented server query response which should help with the response packets going into the jumbo category and getting dropped by the network equipment as a result.

See:'https://wiki.zandronum.com/Launcher_protocol#Segmented_challenge [^]'

Important: The default description points to a backward-incompatible query challenge that changes the packet tag to 200. We don't want that because it will break all previous Zandronum versions and handling this properly would be too convoluted. Keep using the challenge packet with tag 199, but only append the segmentation byte as described further down on the page in the'https://wiki.zandronum.com/Launcher_protocol#Old_protocol_challenge [^]' section.
Revision 2023-06-25 13:43 by Zalewa
Description Zandroum is about to gain support for segmented server query response which should help with the response packets going into the jumbo category and getting dropped by the network equipment as a result.

See:'https://wiki.zandronum.com/Launcher_protocol#Segmented_challenge [^]'

Important: The default description points to a backward-incompatible query challenge that changes the packet tag to 200. We don't want that because it will break all previous Zandronum versions and handling it properly is too convoluted. Keep using the challenge packet with tag 199, but append the segmentation byte as described further down on the page in the'https://wiki.zandronum.com/Launcher_protocol#Old_protocol_challenge [^]' section.




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker