[VoiDeD]

Not to mention that client's switching weapons tends to reset m_flMaxspeed.

[Chdata]

Does m_flMaxspeed stick as long as they don't switch weapons?

I always thought it gets reset at some unknown interval of time.

[sarysa]

Sorry, just to explain my perspective...most of the people here asking for coding advice are probably going to make public hales. They're effectively in the same situation as me because I'm not a server operator. While there may be better options than m_flMaxspeed, it's what FF2 uses, and it trumps any other option whenever it's set. So if your goal is to create a public hale like Fast Zombie or Grey Alien, and you want to bypass FF2's use of m_flMaxspeed, you must use it yourself. There's no other way...and it's far too late now to transition from m_flMaxspeed to something else in the 1.X branch, IMO.

Chdata:
m_flMaxspeed is recalculated by two conditions I'm aware of:
- Changing weapons
- A user's m_nWaterLevel set to 3 (artificially or by the game)

But since FF2 calls it several times per second, it's rarely an issue. (and someone won't spam mouse wheel purposely as hale, it'll make them slower)

[friagram]

The way i do it is transparent to the mechanic, and if tf2att fails, it reverts to maxspeed.

You pass a speed value like 350 and it is converted to the ratio for that class.
An override perameter will set the speed if it is present, and there is a native for that.
The ff2 devs would just need to add this.

If i call ff2_setbossspeed(0, 350)
The boss will get 350 speed, be tf2 attributes installed or not, or i can enter negative value to reset it to default speed.

You really cant go wrong here. Just if tf2att is installed, it works much smoother and minigun/hunstman hales dont run around crazy fast when deployed, and there are no odd errors.

[Wliu]

@sarysa, Shadow, etc: I've finally gotten around to implementing a stop-gap solution for this. There are now two new config options: "disable_health_override" and "disable_speed_override". DHO will prevent OnGetMaxHealth from being hooked while DSO will prevent FF2 from setting the maxspeed every 0.2 seconds. What this means is that if you set DHO to 1, you will also need to manually apply the boss's health (including the starting health when the round starts, or else the boss may have 0 health!). I'm honestly not too sure if you'll need to call "fl_maxspeed" yourself constantly, but based on friagram's comments, it seems so.

This solution is obviously undesirable, so...would it be more beneficial for me to add support for formulas in configs for 1.10.4 than wait until 2.0.0?

Actually, as I've been writing this, I've decided that formulas might as well be supported in 1.10.4. So I guess don't use DSO/DHO since they'll probably disappear before 1.10.4 is even released.