I also have this issue. No idea how to fix either.
I've tried tweaking all those obscure looking position settings in the mod config menu to no avail.
In addition, it seems that changes made to the settings only take affect on newly spawned units (such as cloned codexes and psi zombies), which makes it incredibly hard to customize/check if text wonkiness comes from default settings.
I don't think the text issue is affected by changing the settings though, as said newly spawned units also had the issue even with all values turned up to max.

I am fairly sure I figured out this bug. In TacticalStatOverhaul.uc there the following line:
ActiveStats = ActiveStats++;
Should be replaced with
++ActiveStats;

I would test it out but I will have to revive my Windows install and download the game and SDK. This will take a few days.

My guess is that according to C++ spec postincrement has lower priority than assignment and the increment is not applied. The compiler/interpreter used to execute the scripts (probably gcc) is stricter than MS C++.

Same problem here. Any way to fix it without recompiling the whole game?

kscherer 님이 먼저 게시:

I am fairly sure I figured out this bug. In TacticalStatOverhaul.uc there the following line:
ActiveStats = ActiveStats++;
Should be replaced with
++ActiveStats;

I would test it out but I will have to revive my Windows install and download the game and SDK. This will take a few days.

My guess is that according to C++ spec postincrement has lower priority than assignment and the increment is not applied. The compiler/interpreter used to execute the scripts (probably gcc) is stricter than MS C++.

Thanks for investigating this. The "ActiveStats = ActiveStats++;" statement is indeed the problem (although it seemed to me that UnrealScript byte code does not actually have pre- and postincrement, just one increment whose behaviour is appearantly inconsistent between platforms).

PumpkinHead 님이 먼저 게시:

Same problem here. Any way to fix it without recompiling the whole game?

It is indeed possible to fix the mod with just a hex editor (I used biew).
In ~/.local/share/Steam/steamapps/workshop/content/268500/1630804593/Script/TacticalStatOverhaul.u find all five occurrences of
and change them to

This changes the byte code from the result of compiling
to the result of compiling
The second statement, which is a no-op aside from the variable reference, is necessary for technical reasons to avoid having to recompile. Omitting it would change the script's memory layout and cause a crash on startup.

So just tried it and it works like a charm now! Thanks a lot!

Sorry to open this up after so long, but I'm encountering the same bug on my machine, but the above hex editor fix doesn't seem to be working. When I brought it into windows, it looks like the


got replaced with


instead of


could that be the reason? I'll see if I can fix that in the hex editor on my end, but if anyone has a working TacticalStatOverhaul.u file on Linux, would they be willing to post it so I could check if the issue is with my specific file, or something else? I understand if not.

DI Wayfinder 님이 먼저 게시:

Sorry to open this up after so long, but I'm encountering the same bug on my machine, but the above hex editor fix doesn't seem to be working. When I brought it into windows, it looks like the

ActiveStats = ++ActiveStats;

got replaced with

ActiveStats++; ActiveStats

instead of

++ActiveStats; ActiveStats

could that be the reason? I'll see if I can fix that in the hex editor on my end, but if anyone has a working TacticalStatOverhaul.u file on Linux, would they be willing to post it so I could check if the issue is with my specific file, or something else? I understand if not.

So I ended up solving it, just wanted to post here in case anyone else has the same issue. It turns out, the hex editing did fix the problem, but when ALL stats aren't turned on in the MCM, the ones that are turned off will bunch up to the left of the health bar in a similar fashion to the initial error.