Issues with EGL and AprQ2 / anticheat after the new R1Q2 release

[R1CH]

R1Q2 client/server recently introduced a new protocol35 change, AprQ2 and EGL do not yet support this change and *should* have dropped to protocol 34 and continued working. However, this does not appear to be the case.

AprQ2 seems not to fall back properly, and gets stuck reconnecting over and over. To work around this until a new AprQ2 is released, set cl_protocol 34 manually before connecting in the console.

EGL falls back to protocol 34 properly, but after doing so, will not load anticheat again. I have supplied Echon with an updated version of EGL, but until it is posted on his site, you can use the .exe from this file to fix the issue: http://r-1.ch/egl-0.3.1-r1.zip

[starttimartti]

Ouch. That just killed half of the people that play on my server. Could you make previous versions of server binaries available again?

And I do hope that future server versions will not do this again. If it does, I'm going to have to keep using the old version.


Edit: Do I assume correctly that if a person joins a server, that is not up to date, with the latest r1q2 client, the connection between the server and the client will be over protocol 34 (or if a person joins a server that is up to date with outdated r1q2 client)?

Would it be impossible to make this latest protocol 35 to another new protocol like "protocol 35b" or "protocol 35.1"? That way server and the client would first try to make the connection over 35b and if that fails over 35 and if that fails 34. Maybe.

I'm guessing that currently transfer byte savings that latest protocol 35 would gain are going into waste, since 95% of people are reverting back to protocol 34 or are unable to join the server at all (well latter case actually saves _a lot_ of bandwidth  ).

I'm hosting an aq2 server and the most downloaded aq2 installer uses aprq2 (my own r1q2 using installer from http://makimiehet.mine.nu never gained much popularity), so I have to maintain my server compatible with it.

[R1CH]

I'd rather not release old server binaries, the problem is with the clients EGL and AprQ2, both of which should be updated very shortly. This should not happen in the future as all further protocol 35 changes are versioned similar to how you suggested, so only features that the client/server agree on are used.

[QwazyWabbit]

It's always a good idea to backup the existing version before updating. Sometimes I don't take my own advice on this but most of the time I remember it.

[gammaray]

is really necesary update to the last version? im using the b7322 to run the servers and works perfect with aprq2 egl.

[R1CH]

If you want the bug fixes and new features from the latest release, yes. I always recommend you use the latest version, support is not provided for old versions.

[gammaray]

where are the cvars of this new version? i cant find it. what are the new features.....
i upgrade my servers, but im using cl_protocol !=34 im the anticheat-cvars  to make compatible with aprq2 and egl.

[hAnS!!]

with aprq2 i change the cl_protocol on the game to 34, but when i conect to the server send a message of i dont have anticheat...

i have the last anticheat version ( whit r1q2 dont have a problem)

i think.. the anticheat module is not working on aprq2, because more playeras have this problem on my mod (dday)

sorry for my inglish :S

[R1CH]

I check the AprQ2 code, it should still load anticheat even at protocol 34. I tested this with AprQ2 1.20 on an anticheat optional server and I was still anticheat valid.

[hAnS!!]

i prove aprq2 on my pc and work perfect

is problem of the players of my mod

lol Noobs >,<

but i have a dude... if in the server force to use cl_protocol 34 maybe they dont have problems ?

thanks...

[gammaray]

read my other post, i force cl_protocol to 34.

avispate po wn! xD y visita www.q2chile.com

[R1CH]

EGL 0.3.1-R1 was released to fix this. http://egl.quakedev.com/

[gammaray]

and aprq2, any news?

[R1CH]

<Maniac-> well i added the support, only thing that i need to fix is async mode, for some reason after while it start to studder for about one minute

So... soon hopefully .

[starttimartti]

This should not happen in the future as all further protocol 35 changes are versioned similar to how you suggested, so only features that the client/server agree on are used.

So does this mean that Aprq2 1.20 will again be able to connect normally with original protocol 35 at some point in the future?

or just that Aprq2 1.21 (and egl and others) will not break as badly if/when protocol 35.2 is released?