Andrey Akhmichin

[This changes](https://github.com/MacSourcePorts/xash3d-fwgs/commits?author=tomkidd) not in upstream and i'm not sure how it must work. You can try to set path via `XASH3D_BASEDIR` environment variable. Or need to ask @tomkidd about his...

> I'm running through the supported mods list but most of the mods are precompiled for win-x86 and can't open on my daily driver (arm64-linux) I'm guessing due to the...

> For example They Hunger, I got the Trilogy crossplatform from moddb, compiled they branch from hlsdk-portable which gave me client_arm64.so and hl_arm64.so, put those in cl_dlls and dlls respectively....

waf scripts was not updated in mod branches. I recommend to use cmake for hlsdk. And waf needed for engine builds on specific platforms at first.

> So could this list be considered the one to use for non-x86 platforms? Yes. > The one on xash3d-fwgs/Documentation just says dump the folder and launch with -game which...

> it certainly is rocket science if you have 15 different instructions for compilation, and the project declares its moving to waf but then pulls the rug by not updating...

> Is it possible to disable the creation of the CFG.BAK files whenever the engine is run? For what? > Also, a lot of maps in the multiplayer maps list...

You need to use [old engine](https://github.com/FWGS/xash3d/releases/tag/v0.19.2) and [separate launcher](https://github.com/nekonomicon/AzureSheep-android/releases/tag/1.0)

May be use fresh libbzip2 versions from gitlab? https://gitlab.com/bzip2/bzip2/-/tags

Yep, you're right. And I didn't see any critical fixes or additions in new releases. One small thing which annoying me - there yet another crc32 table.