addHealth(-damage) crash console

[Stanos]

Hello,
so i found lua script in otland and when i tried to test it i noticed that every time creature:addHealth(-damage) is called it crash my console, then i tried to use fire field

        <attribute key="field" value="fire">
            <attribute key="damage" value="20" />
            <attribute key="ticks" value="10000" />
            <attribute key="count" value="7" />
            <attribute key="damage" value="10" />
        </attribute>

which crashed my console either, so any ideas? Using tfs 1.2 8.60

 

[Infernum]

Post Game::creatureChangeHealth

 

[Stanos]

Post Game::creatureChangeHealth

Probably it will sound really weird but i dont have createchangehealth in my src

 

[roriscrave]

Probably it will sound really weird but i dont have createchangehealth in my src
View attachment 35263

and "doCreatureAddHealth" ? have?

 

[Infernum]

Sorry, the correct function name is Game::combatChangeHealth, I'm rusty as hell.

 

[Stanos]

Sorry, the correct function name is Game::combatChangeHealth, I'm rusty as hell.

Its all good [C++] bool Game::combatChangeHealth(Creature* attacker, Creature* target, CombatDamage - Pastebin.com (https://pastebin.com/8mA0z2Wm)

 

[Stanos]

Bump

 

[Stanos]

Maybe bump

 

[pudim]

Is it a creaturescript?

 

[Infernum]

Yeah I don't see anything wrong with your combatChangeHealth function, there must be a script or some other source change somewhere checking for a null attacker.

 

[Stanos]

Is it a creaturescript?

No, first one i tried was movements, second one i tried was just items.xml damage attribute.

Yeah I don't see anything wrong with your combatChangeHealth function, there must be a script or some other source change somewhere checking for a null attacker.

Where it might be if its possible to know?

 

[Infernum]

No, first one i tried was movements, second one i tried was just items.xml damage attribute.

Where it might be if its possible to know?

You can easily pinpoint the fault if you use Visual Studio and just run the debugger on your exe and let it crash.