Spring RTS Engine

	if paralyzer then
		 local h,mH,pD,cP,bP = Spring.GetUnitHealth(unitID)
		Spring.Echo("h = "..h,"mH = "..mH,"pD = "..pD,"cP = "..cP,"bP = "..bP)
		if pD < mH then
			return damage + mH
		else
			return damage + pD
		end
	end

Each slow update (every 16 frames) paralyzeDamage is decreased with maxHealth * (16/30/40) = maxHealth*0.025*16/30.

TheFatController wrote:So just to get my head around all that, if a BLADEWING_LYZER has "paralyzetime=7;", will there still be circumstances where a unit can be paralyzed for longer than 7 seconds?

Argh wrote:Only problem is that the treatment of the paralyze time is funky. On the first hit, a weapon doing 1000 damage seems to do roughly 1 second of paralyze.

On the second hit, it's nearly 7 seconds, due to

Each slow update (every 16 frames) paralyzeDamage is decreased with maxHealth * (16/30/40) = maxHealth*0.025*16/30.

This isn't going to produce very logical behavior- things with lots of hitpoints, even if set up to be extra-vulnerable to paralysis, become free of paralysis faster, arbitrarily.

It should just ramp down 1000 units / second, so that building timing and balance is straightforward. 1000 paralyze damage == 1 second game-time. If people want to make Units recover faster / slower than that, they can use Lua to easily manipulate the logic then.

Then you can get rid of all the extra cruft, like having a timing variable in the WeaponDef (or just treat that as an override- if defined, ignore damage, multiply that number by 1000).

Or... even better yet... fix it however you want to, but let us turn that whole system off with a mod option. Now that I know how it works, I'd rather do it in Lua.

Tobi wrote:

TheFatController wrote:So just to get my head around all that, if a BLADEWING_LYZER has "paralyzetime=7;", will there still be circumstances where a unit can be paralyzed for longer than 7 seconds?

With only my change the only case in which this can happen is if it is being / has just been paralyzed by another weapon, which has paralyzeTime > 7 seconds.

Gota wrote:Was there emp in OTA?
In any case IMO hurt units should not become paralyzed faster.
I think it makes more sense for the paralyze to use the units full hp as a base.

Pxtl wrote:

Gota wrote:Was there emp in OTA?
In any case IMO hurt units should not become paralyzed faster.
I think it makes more sense for the paralyze to use the units full hp as a base.

I don't know whether to laugh or cry at reading this.

Yeah, there were paralyze units in OTA. The Arm spider and tactical missile launcher building were stun units.

Google_Frog wrote:Please make this optional. CA emp is balanced around damaged units being easier to paralyze and the ability to keep units paralyzed by damaging them.

TheFatController wrote:

Google_Frog wrote:Please make this optional. CA emp is balanced around damaged units being easier to paralyze and the ability to keep units paralyzed by damaging them.

I'm sure you'll have no problem recreating the old functionality with lua as BA had to do with the reclaim change.

Google_Frog wrote:Please make this optional. CA emp is balanced around damaged units being easier to paralyze and the ability to keep units paralyzed by damaging them.

TheFatController wrote:Where they replaced the crazy reclaim formula with the sensible one, but as BA was balanced on the crazy formula it had to be reinstated with a Gadget, no modrule was provided to access the old formula.