Going off-topic here but...
[me@mypc Desktop]$ inxi -S
System:
Host: censored Kernel: 5.10.15-1-MANJARO x86_64 bits: 64
Desktop: Xfce 4.16.0 Distro: Manjaro Linux

I will respond in PM.

In regards to Crysis - most if not ALL mods are 32-bit only as this game was primarily 32-bit.
I do own it on GOG (I also have it on Origin) so it sucks for me that 32-bit executable is missing for presumalby stupid reasons (laziness? The question is whois).

So how about some of you, who own the game(s) here on GOG, do a support request and point out the mod problem?

I'm surprised anyone would want to use 32 bit OS anymore considering the limitations it puts on your system specs.

Yes but as per a few posts above this, there are 32bit only mods. I myself did not think of those at first.

You can run 32bit programs/apps in a 64bit operating system (with some exceptions, Apple among them).

MODS.
Almost all (if not all) for Crysis 1 are for 32-bit version.
The GOG-introduced incompatiblity is a sore.

Several actually...

1) I use security software which I consider essential (System Safety Monitor and Process Guard) which are not available for 64-bit Windows. Since they function by hooking the SSDT, which PatchGuard/KPP blocks, it is unlikely a comparable x64 version would ever exist. The closest equivalents I have found on x64 run in user mode (less secure) and require online activation (unacceptable).

2) I have a wide variety of hardware for which drivers aren't available under x64 (including, ironically, a Microsoft Sidewinder Strategic Commander though some third party drivers may help out there.).

3) I have a strong dislike for the architectural bodginess of Win x64 (requiring applications to be split between Program Files and Program Files (x86) - and the Microsoftie who thought it was a good idea to have 64-bit DLLs in \System32 and 32-bit ones under \SysWOW64 should be steamrollered - slowly). Compare this to the way 16-bit applications were handled under 32-bit Windows, which was almost invisible from the user perspective (you'd need a sharp eye on Task Manager to catch ntvdm starting up with 16-bit software).

4) As B1tF1ghter has noted, switching to x64 means getting Win10 which raises a further load of issues (effectively compulsory spyware, a crippled UI with looks taken from Windows/286, compatibility problems with older software, significantly worse performance, greatly increased code bloat and more onerous online activation requirements).
Done, but GOG's recent support response times have grown from days to weeks to months. I wouldn't be surprised to be posting in this thread in 2022...

And here I'm still reading this wondering what kind of greatness I missed after all this time...

I doubt the 32 bit versions will ever come back. lol

It's alright, though. The 64 bit version runs fine, at least if you download the modified .dll from PCGamingWiki (or just use the c1-launcher mod on Github) which removes the framecap. Runs buttery smooth.

Gee - what's this I see on my cumbersome list of subscribed to threads on the ancient forum CMS under GOG . com name? - 3 YEAR necro you say?... PERFECT....

But alas...

There were 32-bit only mods - to kick the same bush of a point again - and I'd imagine some of them were never updated for the 64 bit executable... so you know...
You definitely cannot use those ¯\_(ツ)_/¯

Thanks for the info.
Imagine retro PC's going for sale with "Includes the working modded version of Crysis :D" title xD
Probably would pay something for that haha.