[Trigger] Custom Scripts

[LittleBigApple]

Hey
I have a question concerning custom scripts.

Is it possible to create the index "For Loop Integer A" in a custom script?
I tried for instance: call RemoveLocation(udg_Tempp[IntegerA]), but it didn't work.

Thanks.

 

[IcemanBo]

Yes, use "GetForLoopIndexA()"

But anyway in most cases it's better to use own integer variables for loops instead IntegerA/B

 

[deathismyfriend]

Use this instead of calling the function above.

bj_forLoopAIndex

 

[LittleBigApple]

Thanks both!
So it should look like this:
call RemoveLocation(udg_Tempp[bj_forLoopAIndex])?

Own integer variables is better that IntegerA/B - how so?

 

[deathismyfriend]

Integer A / B are slower and less efficient because they use a function call rather than the variable directly. It is better to use your own integer.

 

[venger07]

you can also index these..

[GetConvertedPlayerId(GetTriggerPlayer())] = Triggering Player Index
[GetConvertedPlayerId(GetOwningPlayer(GetTriggerUnit()))] = Owner of Triggering unit Index

 

[PurgeandFire]

Own integer variables is better that IntegerA/B - how so?

See:
http://www.hiveworkshop.com/forums/...fer-integer-custom-script-244291/#post2444460

It has an explanation of why we use separate variables for loops. Technically you don't have to replace every Integer A/B if you know exactly how it works, but it is usually easier to just use a separate variable for all loops (or at least a separate variable for each trigger).

 

[IcemanBo]

^But the sense of global variables is usually that you use them in more triggers.

I would say only use an extra integers for systems, but for general loops you always can work with a temp_integer.

And PurgeandFire made a really good example of how you should not do it with loops.. it's the same issue with "A Unit dies", or?

 

[LittleBigApple]

Ok, great. Thanks for the replies!

This may be a dumb question, but is this test-trigger correctly made then?

• Test
  • Events
    • Map initialization
  • Conditions
  • Actions
    • Set Regions[1] = Region 000 <gen>
    • Set Regions[2] = Region 001 <gen>
    • Set Regions[3] = Region 002 <gen>
    • For each (Integer A) from 1 to 3, do (Actions)
      • Loop - Actions
        • Set TestInteger = (TestInteger + 1)
        • Set TestPoint[TestInteger] = (Center of Regions[TestInteger])
        • Unit - Create 1 Footman for Player 1 (Red) at TestPoint[TestInteger] facing Default building facing degrees
        • Custom script: call RemoveLocation(udg_TestPoint[udg_TestInteger])

 

[IcemanBo]

Instead of using For each IntegerA, use For each IntegerVariable, and then select your TestInteger.

Now it's not needed anymore to set TestInteger +1 each time.

 

[LittleBigApple]

Ahhhhh, now I see