Talk:Bring Condition Bug

There is no bring condition bug.

1. "Associated with each Location in Starcraft is a block of data, and unfortunately it does not always update correctly between triggers. The Location data will only update when certain Trigger Actions fire, and at the beginning of a trigger cycle." -- This is false. The only data associated with locations are its boundary coordinates and flags, there is no other data like this article is suggesting.

2. Kill Unit (and Kill Unit At) assigns the "die" order which means it's to be scheduled for destruction, but does not remove it until the following cycle. This means any unit detection can still happen in the same trigger cycle as described in this article. Try the same with Remove Unit and it will be fine.

3. The claim at the bottom of the page is even more misleading, as it perpetuates the idea that there is some bug with the same info as in 1. It then talks about ways to remedy this "bug" which don't actually do what it's proposing. The given triggers do reset the FindUnit cache which is not location-associated (it is global), but in the given scenario does nothing because the "dead" unit is re-added anyway per behaviour in 2.

--Heinermann (talk) 22:53, 23 February 2021 (EST)