-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Race Client / Server messages in the future (0.7.0) #4
Comments
maybe add a general method from the client to tell the server what he can do instead of inventing a msg for each client. |
@heinrich5991 that doesn't make sense to me, like NETMSGTYPE_CL_ISRACE=200, so that Race messages would not overlap DDRace messages at 100 and not over lap teeworlds at 0 but i'm no python expert and replacing it in the pythin code doesn't work |
and adding dummies in the python is not really cool @SushiTee do you have a super solution like always :) ? |
I don't think that messages like CL_ISRACE are a good idea, I think we should solve that problem more general. Like for example CL_CLIENTFEATURE, sending a list of client features in like: And then the server responds with the next message, specifying, which additional protocol it will use: Afterwards, not sure if this step is needed, the client will send the protocols actually used in the session. And then we create an additional protocol for those extensions, each one sending the hashed name of the module with it, so we don't have overlapping message IDs. |
jap overlapping message ids are a very bad thing. i had some problems with it before already. i have to admit i didnt really thought about this at all yet how to solve this better. what heinrich said sounds like a plan though. |
but still, we need to have them at a place far than teeworlds messages @heinrich5991 and @SushiTee i accept @heinrich5991 proposal |
We have to reach some kind of messages in networtk.py that works for both DDRace and race so that we can support eachother's client/server
The text was updated successfully, but these errors were encountered: