[Solved] Unit Orders

[jolelele]

Hello there. Im currently working on a Bossfighting system for my map.

My question is this:
Is it possible to save a unit order in a variable?

Example: I want my "Super Tauren" boss to use war stomp. I have to use

• Unit - Order BOSSBoss to Orc Tauren Chieftain - War Stomp

What I want to do is this:

• Unit - Order BOSSBoss to BossAbility[1]

or something similar.

Is this possible in GUI?
If not. Is it possible with custom scripts?

I never bothered to learn vJASS and I dont really have the motivation to do it now so if this is impossible Il just hardcode it.

 

[streetpunk]

create a order variable and set it to the desired order

 

[apsyll]

I don't think there is something in GUI for order from a variable but you can use custom script for
this. I just transfered gui to text and changed a bit to get this:

• init
  • Ereignisse
    • Zeit - Elapsed game time is 0.30 seconds
  • Bedingungen
  • Aktionen
    • Set BOSSboss = Tauren-Häuptling 0000 <gen>
    • Set order_string[1] = stomp

• order
  • Ereignisse
    • Spieler - Spieler 1 (Rot) skips a cinematic sequence
  • Bedingungen
  • Aktionen
    • Custom script: call IssueImmediateOrderBJ( udg_BOSSboss, udg_order_string[1] )

sorry my editor is still german but i hope you understand everything.

 

[Dehua_Darbuya]

Just to add to Apsyll's post, it would be slightly more efficient to use the native IssueImmediateOrder as opposed to the BJ function.

Spoiler: Native vs BJ

native IssueImmediateOrder takes unit whichUnit, string order returns boolean

function IssueImmediateOrderBJ takes unit whichUnit, string order returns boolean
    return IssueImmediateOrder( whichUnit, order )
endfunction

There's also the native IssueImmediateOrderById which uses the order's ID instead of it's string. To find the ID of an order, there's this: Order Ids.

Spoiler: Native using ID

native IssueImmediateOrderById takes unit whichUnit, integer order returns boolean

 

[FUJI]

• Untitled Trigger 002
  • Events
  • Conditions
  • Actions
    • -------- --------
    • -------- onInit --------
    • Set AbilityOrderString = stomp
    • -------- ^ String Type Variable = <orderstring> ( ex: stomp, channel, move, attack, roar. ) --------
    • -------- --------
    • -------- onCast --------
    • Custom script: call IssueImmediateOrder( udg_UNIT, udg_AbilityOrderString )
    • -------- ^ Ordering the unit to cast that stored String Order variable. --------
    • -------- --------

^ Yes it is possible to store a unit's ability order via string variable.

 

[jolelele]

Thank you guys. I was up to 6 am last night and actually managed to fix it. But I still dont understand the difference between IssueImediateOrderBJ and IssueImediateOrder. Is there a difference or is the second one simply more effective?

I think this is solved now. Thanks all.

 

[Rheiko]

The second one is simply more effective. Because as most people said, BJ is bad.

 

[jolelele]

Ok nice. Thanks.