• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

TFS 1.X+ addCondition bug

mackerel

Well-Known Member
Joined
Apr 26, 2017
Messages
398
Solutions
18
Reaction score
72
Just moved to latest TFS version and it's been great so far. The only thing that pops up in my console is few error messages:

[Warning] Function Combat.setCondition was renamed to Combat.addCondition and will be removed in the future

Alright, so it's not a big deal. Just change the function. The thing is it does not work. Even when using examples from github. Let's say scripts/custom/combustion.lua has this code, you can test it yourself by pulling latest master:

Lua:
local condition = Condition(CONDITION_FIRE)
condition:setParameter(CONDITION_PARAM_DELAYED, true)
condition:addDamage(5, 3000, -25)
condition:addDamage(1, 5000, -666)

local combat = Combat()
combat:setParameter(COMBAT_PARAM_TYPE, COMBAT_FIREDAMAGE)
combat:setParameter(COMBAT_PARAM_EFFECT, CONST_ME_FIREAREA)
combat:setParameter(COMBAT_PARAM_DISTANCEEFFECT, CONST_ANI_FIRE)
combat:setFormula(COMBAT_FORMULA_LEVELMAGIC, -1.3, -30, -1.7, 0)
combat:addCondition(condition)

function onCastSpell(creature, variant, isHotkey)
    return combat:execute(creature, variant)
end

It meant to deal damage which it does successfully:)
it also meant to add burn condition but it does not, more precisely when you set it as -> combat:addCondition(condition)

There is workaround by assigning the condition directly to target. Unless I am doing something wrong I don't know what's wrong
 
Back
Top