[Bug]: [1.4.2] Conditions are not working for spells/weapons .lua files #4813
Labels
bug
An issue describing unexpected behavior of code
needs-confirmation
not confirmed by a developer yet
By submitting this bug issue, you agree to the following.
Does this bug crash tfs?
no
Server Version
1.4.x (Release)
Operation System
all (listed below)
OS Description
No response
Bug description
Damage is only dealt on players combat.
Possible Pull Requests which are to blame
Steps to reproduce
Code to reproduce the issue:
-- paste your script here
Actual Behavior
When player casts spell which should give condition the condition does apply but never ticks
the only time u get a tick if player (owner of condition) deals the damage to the monster.
e.g try using poison arrow itself it does not actually work dealing the poison ticks over time no matter what way you add condition
I tried 50 different ways to force condition create second combat object and everything
issue possibly comes from Updated lua libraries or some other stuff while it might have worked in 2018-2019 it does in fact not work nowadays.
Expected Behavior
Conditions should tick in their own respected time
use poison arrow for reference.
there is never a second tick ever unless player deals the damage to monster via weapon/spell/ or other combat only then it ticks and player has to finely TIME his hit with the tick otherwise it wont tick either.
Backtrace
No response
The text was updated successfully, but these errors were encountered: