Expanding the HUD with optional Dummy values

[alpi182]

This Expands the HUD that shows the Players Position, Speed & Angle to also optionally show these values for the Dummy.

Checklist

• Tested the change ingame
• Provided screenshots if it is a visual change
• Tested in combination with possibly related configuration options
• Written a unit test (especially base/) or added coverage to integration test
• Considered possible null pointers and out of bounds array indexing
• Changed no physics that affect existing maps
• Tested the change with ASan+UBSan or valgrind's memcheck (optional)

[SollyBunny]

same as g_Config.m_ClDummy ? 0 : 1, 1 - g_Config.m_ClDummy also works, im not sure what's best so don't change it

[SollyBunny]

also fix CI and squash

[alpi182]

also fix CI and squash

i dont even know what this is supposed to mean. i have never worked with github

[SollyBunny]

Removed line for no reason?

[SollyBunny]

i dont even know what this is supposed to mean. i have never worked with github

The CI is the checks at the bottom (which aren't running automatically for some reason), they should be all green (or blue depending on theme), you can click on the red ones to see why they failed

By squash I mean combine commits since it doesn't make sense to have one of them but not the others, you can do this with

git reset tater master # tater should be whatever your remote for tater is
git commit -m "new commit msg"
git push origin master --force # push over changes

if you fuck up, always know git reflog exists and the commit b3dd49a is always stored on GitHub

[alpi182]

The CI is the checks at the bottom (which aren't running automatically for some reason), they should be all green (or blue depending on theme), you can click on the red ones to see why they failed

By squash I mean combine commits since it doesn't make sense to have one of them but not the others, you can do this with

git reset tater master # tater should be whatever your remote for tater is
git commit -m "new commit msg"
git push origin master --force # push over changes

if you fuck up, always know git reflog exists and the commit b3dd49a is always stored on GitHub

Can´t i run the Checks myself or do I have to wait until you initiate them.

Also I don´t understand while building there are like 4000 lines of code with hundreds of Errors in files I have never touched. Do I need to edit those files aswell or just the Errors appearing at hud.cpp

Also I am doing all this inside Github and can´t really test it on my end because cloning TClient on windows is pain in the ass

[SollyBunny]

I'll just fix it

[SollyBunny]

Ah there's unrelated CI problems, I'll fix it after merge