NoDownload and Panzerwar work with ET: Legacy again

[Mystik]

Hello!

Some time ago the ET:L file system issue with .pk3 files with the ~~~ charcater (used to make paks load last) in their names was fixed on TWC by renaming the files. This fixed the filename error, but still users connecting to the servers experienced instant crashes with ET: Legacy clients above version 2.75 on TWC's Jaymod servers.
I noticed the same problem was applicable to our servers, which makes sense since we have a VERY similar setup on our Jaymod servers compared to TWC. I was bored so I began wondering why this was happening.

After a bunch of debugging, I found the problem and asked Zone to mitigate it for TWC as well. The TWC Jaymod servers (NoDownload and Panzerwar) are now working again with ET: Legacy Windows clients. (Tested with ET:L 2.80.2)

Further explanation for those that care:

This problem has been present since at least ET:L 2.77.x up to 2.80.2. This has only affected Windows clients, while Linux (and assuming Mac also) clients have been able to connect just fine. No error was provided on ET: L on crash, and nothing useful was found in verbose logs using the +set logging 2 launch option either. In there it seemed like a somewhat clean exit, with no errors. This also seemed to ONLY happen on TWC and EA Jaymod servers, or at least I couldn't find any more servers that experienced this issue.

TWC was running the 2.6 linux binary before, and then updated to 2.6b binary, and the problem persisted. Our Jaymod servers are running the ET 3.00 TB 0.7.4 binary, so this should pretty much rule out the binary being the problem.

Things I tried:
- Disabled the auth QMM plugin
- Disabled the Bugfixes QMM plugin
- Disabled the TWC Scumbuster QMM plugin
- Disabled the whole QMM mod
- Disabled ENHMod

None of these steps of course did nothing.

The problem lies in the jaymod .pk3 file, and both TWC and EA were using some custom jaymod .pk3 called jaymod-2.2.0_reds_v102.pk3. I didn't catch this right away because both this and the normal pk3 were present in our servers installation. Comparing this file to the vanilla jaymod-2.2.0.pk3 reveals that only one file is changed between them, the Windows .dll library:

So this explains why the crash only happened on ET:L Windows clients.

Replacing jaymod-2.2.0_reds_v102.pk3 with the normal jaymod-2.2.0.pk3 fixes the issue.

[ZonElax]

Hey Mystik,

in the name of whole TWC we are grateful for your efforts. This is a big step for increasing activity. Thank you!

Much love <3

[SadNesS]

Fck great work Mystic