Notes |
|
(0020732)
|
Pol M
|
2019-06-06 16:26
|
|
Okay, the issue is caused by a new fork of srb2: SRB2Kart.
Now, about what should be done, I'm not that sure. The empty players can be ruled out without problems due to these having absolutely all values set to 0, but I'd say that first we should notify the developers that they are not marking the players as non-existent (for reference, src/plugins/srb2/srb2server.cpp:275, the check is failing due to the node not being 0xff). Also, this is a fork, not the main engine, and leaving as is does not feel right: it requires its own program, and based on the fact that this ticket exists clearly the internet communications may change. Hoping to hear from you on whether we should rule them out, create a new plugin, or else. |
|
|
(0020734)
|
Zalewa
|
2019-06-09 19:06
|
|
If they don't follow packet compatbility and yet report to the same master server they basically screwed themselves over.
Is there something in the packet that would allow us to recognize that it is from a different game and interpret the packet differently? |
|
|
(0020737)
|
Pol M
|
2019-06-09 20:57
|
|
Quote from Zalewa
Is there something in the packet that would allow us to recognize that it is from a different game and interpret the packet differently?
Appart from the fact that the players are pretty much empty (score is 0, name is "", seconds in server is 0, etc...) nothing rellevant, the player structure is the same. Maybe they have done a change somewhere that is backwards-compatible? I think that the best idea is to ask. If you're okay with it, I'll contact them. |
|
|
(0020759)
|
Zalewa
|
2019-06-13 15:04
|
|
Sure, go ahead and contact them :) |
|
|
(0020763)
|
Pol M
|
2019-06-13 17:52
(edited on: 2019-06-18 09:33) |
|
I posted on their bug report thread: post
Issue fixed by Sryder in this PR
I'll also ask if there is an easy way to distinguish both engines, and I'll create a ticket to discuss what should be done with this new engine.
|
|
|
|
Since we didn't do anything in Doomseeker code (in this reported issue) to resolve the issue with non-compat packets from pre-PR servers, I'm changing this to "no change required". |
|