Fixed so that delays on a blind path doesn't affect other paths

[TFSMads]

Problem

Teleport effect is causing set damage not to work as expected as described in #8203

Solution

Removed teleport effect setting hasDelayBefore to Unkown.

Testing Completed

Tested on version 1.21.10

Supporting Information

---

Completes: #8203
Related: none

[Efnilite]

this should be fixed by only setting the delay before of the if branch

[sovdeeth]

The teleport effect is working fine, do not remove its setting of the delay.

The issue is in the prolongation of delays through the parsing of the if. The parser should be smart enough to realize that the delayed path stops and only non-delayed paths reach the set damage effect.

[TFSMads]

on damage of player:
    if world of victim is "world":
        wait 1 tick
    if damage cause is fall:
        stop    
    set damage to 0
    #HasDelay is not chaged - 

 
on damage of player:
    wait 1 tick
    if damage cause is fall:
        stop    
    set damage to 0
    #HasDelay is not chaged
 

on damage of player:
    if world of victim is "world":
        wait 1 tick
        stop    
    set damage to 0
    #HasDelay is set to false

on damage of player:
    if world of victim is "world":
        if damage cause is fall:
            wait 1 tick
        stop    
    set damage to 0
    #HasDelay is set to false

I have tested the changes on version 1.21.10 with the script above. Delays from paths where set damage is unreachable is ignored while delay from paths that can reach 'set damage' remains.

[sovdeeth]

Suggested change

[sovdeeth]

Is this safe in the following scenario? I don't think it is

loop 3 times:
    wait 1 tick # the loop is delayed
    exit loop # only this section is delayed, so we set delayed before to false
set damage to 2 # setting damage after event has passed