| 03-27-2007, 03:19 AM | #2 |
If it was just double free of location then you could blame the handle var stuff But of group? The only explanation would be that something is really messed up in your map. |
| 03-28-2007, 09:07 PM | #3 |
In hindsight it is obvious but I am still not so smart in understanding the way triggers get executed and I had to stare at this for awhile. The problem is that the "Set Next Waypoint" and "Detonate" triggers that get called by this function use the ug and p global variables themselves so those triggers get called, execute, overwrite the variables causing the other ones to leak and then remove the new group and location then come back to the original trigger and try removing the location and group again. Correct me if I am wrong in this understanding but I don't get those error messages anymore when I made sure to remove the location after the group is made and remove the group inside the if statement just before the triggers get called. I should really just convert all my spawned creep triggers to jass functions and use local variables I suppose. |
| 03-28-2007, 11:10 PM | #4 |
That's a good point, many guys think they can just use global variables like that when it is not the case, things like running another trigger may cause conflicts, but also some times if you do something to trigger another trigger. |
