| 07-10-2008, 01:04 PM | #2 |
This: call RemoveLocation (udg_x_TempPointSpawn[GetForLoopIndexA ()]) or call RemoveLocation (udg_x_TempPointSpawn[bj_forLoopAIndex]) But, to be honest, you don't need an array. You are destroying the point after it's created/used without any delay, so an array just makes it longer and more awkward |
| 07-10-2008, 01:17 PM | #3 | |
Quote:
Or that I don't need an array for the trigger? Because that I do. |
| 07-10-2008, 01:20 PM | #4 | |
Quote:
That you don't need an array. If that's your whole trigger, you sure as hell don't need an array. You don't need that "Do nothing" either. Leaving the Else - Actions blank will have the same effect |
| 07-10-2008, 01:31 PM | #5 | |
Quote:
And Do Nothing is purely aestethic. :P ed: +rep for being pro. ![]() |
| 07-10-2008, 01:41 PM | #6 | |
Quote:
Ye, it'll be MUI. It'll have to go through all the loop actions for that particular value of integer A before moving onto the next value for integer A |
