-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: [1.4.2] Conditions are not working for spells/weapons .lua files #4813
Comments
in the mean time im probably gonna create "invisible" condition fields that I want :/ |
seems fine for the fluids however but thats on self which is odd |
i could not find any reference to the poison arrow addConditionDamage or whatever htat function is anywhere in luascripts |
can you provided some example script? probably this is source of problems: forgottenserver/src/combat.cpp Line 677 in 3bca716
|
seems like it happens when u apply a Condition to combat. |
Provide example to reproduce |
Poison arrow in weapons |
yeah conditions applied in combat only tick if the combat is ticking if there is no reaction to combat then the condition time is not running or its running but skipping the tick adding yoiu have to hit monster at either extactly the tick time or near it for the tick to happen |
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: