Damage engine bugged?

[HammerFist132]

Hello I have problemm with bribe damage engine and I am bad in scripting, now problemm: when attacked unit is on 100% hp and it null all taken damage and there is many attacking units it happens to me to his max hp goes to 50K for a momment what looks really bad. Any help

 

[Mr_Bean]

It's just how the system works. The damage blocking ability is added to units when they are damaged. This is how it is able to block damage.

 

[HammerFist132]

but mostly thet 50K hp do not show and I should not see it in game for excample 360/50360 hp and in next o,1 it goes back to normal.

 

[Mr_Bean]

Hmmm, it has never happened to me. Perhaps contact Bribe and ask him about it.

 

[Bribe]

It is a WC3 bug. The thing is this happens with every damage detection engine that involves blocking. 0-second timers are not truly 0-seconds, in fact 0-second timers are a bit random like waits for some reason.

I have tried other approaches to 0-second timers like delayed-events, however they also work the exact same. 0-second timer event triggers also do the same.

As I said, it is a WC3 bug, and this is an 11-year old engine that Blizzard only supports to a limited extent. You can write them if you want to ask them to fix these kinds of problems.

 

[Mr_Bean]

Yeah, Warcraft III is old, but still awesome!
I doubt writing to them would help, they have most probably moved on to Starcraft II and World of Warcraft.

 

[Bribe]

The patch that brought in hash tables was quite unexpected of them after such a long time. But I think they only released that patch to get a functional and safe alternative to the exploitable return bug.

 

[Mr_Bean]

When was that patch released?

 

[edo494]

When was that patch released?

according to http://www.dota-utilities.com/2009/05/warcraft-124-patch-warcraft-patch-124.html
the release date was maybe in May 2009