halflife VS Xash3D-Emscripten

It's a part of C++ project https://github.com/ValveSoftware/halflife

I wonder if this is something you can amend in the actual code here: https://github.com/ValveSoftware/halflife

I know the most known issue about overbright on github already states that they will not fix it, but that was from 2013 and thoughts about overbright issue could've changed since then. Plus I am running HL on linux and this issue Infuriates me since I'm stuck using the OpenGL renderer (which is the only renderer that has this issue). We've known that valve really likes their linux oriented approach, and plus we know they love their Deckies that they updated HL2 with fixes and QoL stuff, what's stopping them from fixing overbright?

More info on texture scaling: https://github.com/ValveSoftware/halflife/issues/1650

Funnily enough, on Half-Life 1 engine-based games (i.e. the engine that came before HL2 - on which Team Fortress 2 runs; such as Counter-Strike 1.6), a different allocator problem exists -- glibc's malloc() just decides to fail miserably[0] on some setups.

[0] https://github.com/ValveSoftware/halflife/issues/3158

I guess you have to either modify the code https://github.com/ValveSoftware/halflife/blob/master/dlls/hgrunt.cpp

The original Half Life, including goldsrc, is source-available: https://github.com/ValveSoftware/halflife

And in fact even their Half-Life 1 bugtracker on GitHub is policed: https://github.com/ValveSoftware/halflife/issues

For the curious, this is based on the https://github.com/FWGS/xash3d-fwgs engine. Probably this fork: https://github.com/icrazyblaze/Xash3D-Emscripten/

I thought the error produced by following the link to the original author's site was related to the .ua domain and current events, but it turns out the story is evidently more complicated, and seemingly also unresolved since 2018: https://github.com/iCrazyBlaze/Xash3D-Emscripten/issues/1