[BlazingDiancie]

Could you make it so that this plugin affects MvM robots with a convar? This would allow Super Scouts to reach their true max speed.

[FlaminSarge]

Was there a particular reason for DHook + NOP instead of just patching the value inside the CMoveData.m_flMaxSpeed assignment?
e.g. https://github.com/FlaminSarge/tf_maxspeed_patch solely patches the value and I'm unclear on if it does better, worse, or the same for prediction.
Also, have you attempted editing m_flClientMaxSpeed? Does that help with prediction at all?

[xXDeathreusXx]

Originally Posted by FlaminSarge Was there a particular reason for DHook + NOP instead of just patching the value inside the CMoveData.m_flMaxSpeed assignment? e.g. https://github.com/FlaminSarge/tf_maxspeed_patch solely patches the value and I'm unclear on if it does better, worse, or the same for prediction. Also, have you attempted editing m_flClientMaxSpeed? Does that help with prediction at all?

No particular reason, but I believe just replacing with NOPs 1 time instead of constantly overriding the value would be better performance wise, but we're talking nanoseconds here

As far as I knew TF2 doesn't even use m_flClientMaxSpeed

[FlaminSarge]

Originally Posted by xXDeathreusXx No particular reason, but I believe just replacing with NOPs 1 time instead of constantly overriding the value would be better performance wise, but we're talking nanoseconds here As far as I knew TF2 doesn't even use m_flClientMaxSpeed

No no, the divergence here isn't `patch with NOP` vs `override value every time in DHook`, it's `patch with NOP` vs `patch with new max speed value`.

The performance hit would only happen when you update the cvar value, which would undo the patch and then redo the patch with a different value; I'd hope users aren't updating the cvar frequently, though.

RE: clientmaxspeed, I'm just trying to figure out how to solve jitteryness on client as client doesn't expect max speed to go over 520 either (I think?).

[CookieCat]

Broken as of latest TF2 update, the message appears indicating it applied the patch but the movement speed is not uncapped.

[Mikusch]

I have made a SourceScramble manager config that mirrors this plugin's functionality: https://github.com/Mikusch/SourceScramble-Patches

If you need this plugin, I recommend switching to this. It's easier to maintain.