You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since 2.0 will break ALL the things, why not break more things and use an attribute to modify hales speed? If you take the desired speed from the config, and divide it by the class's max speed, you'll get an accurate "move speed bonus" attribute number.
The only minor flaw with this is you can't have perfectly exact numbers, if you take scouts 400 speed, and want him to move at 385, the attribute value would actually make him move at 384, the attribute appears to use the first 2 decimal numbers, assuming there's no sort of rounding going on...
I only did a quick test of this using a command to set the attribute on me, a command to print out m_flMaxSpeed, and a calculator. The results were more or less what it should be.
The text was updated successfully, but these errors were encountered:
Since 2.0 will break ALL the things, why not break more things and use an attribute to modify hales speed? If you take the desired speed from the config, and divide it by the class's max speed, you'll get an accurate "move speed bonus" attribute number.
The only minor flaw with this is you can't have perfectly exact numbers, if you take scouts 400 speed, and want him to move at 385, the attribute value would actually make him move at 384, the attribute appears to use the first 2 decimal numbers, assuming there's no sort of rounding going on...
I only did a quick test of this using a command to set the attribute on me, a command to print out m_flMaxSpeed, and a calculator. The results were more or less what it should be.
The text was updated successfully, but these errors were encountered: