Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Incomplete TASSERVER implementation: Compflags u and b #284

Open
MasterBel2 opened this issue Apr 27, 2024 · 1 comment
Open

Incomplete TASSERVER implementation: Compflags u and b #284

MasterBel2 opened this issue Apr 27, 2024 · 1 comment
Labels
feature request Not broken but something we want added low priority

Comments

@MasterBel2
Copy link
Contributor

MasterBel2 commented Apr 27, 2024 •
edited
Loading

Clients (most notably SpringLobby & my personal client(s) built on UberserverClientCore) that have implemented the b compat flag will fail to connect, due to expecting additional data in the BATTLEOPENED command from the server.

The lack of support for u is less consequential - since it is only an optional message sent to hosts when a user joins to let them decide whether the user may join the battle.

For reference: Spring lobby protocol description
@L-e-x-o-n
Copy link
Collaborator

Currently only Chobby is officially supported, while this would be nice to have, it is a low priority issue.

@L-e-x-o-n L-e-x-o-n added feature request Not broken but something we want added low priority labels Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request Not broken but something we want added low priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MasterBel2 @L-e-x-o-n