I am struggling to find the appropriate Cancel ability so the Nexus cancels a probe via trigger.
The trigger looks something like this:
If
(Unit type of Nexus training queue slot 2 item 1) != No Game Link
Then
Unit - Order Nexus to ( Cancel) (Replace Existing Orders)
Debug - Display "No queue!" as debug output using Type 01, and Do display it in the game window
Else
When I try to get a reference of the actual ability that the Nexus uses in the Data (F7) to what I guess would cancel a Probe, it says, Queue (5) - Cancel.
So I choose that ability in the Trigger (F6); however it still does not work. Please help me, and I hope the solution you offer works (you've tested it yourselves). <sub>N.B. I have seen and already tried using: Cancel Probe - Build (Probe)</sub>
I don't think it is possible to manipulate a person from pressing his hotkeys; nor would I know how to lock the ability warp in probe, once a limit condition is met - besides, it won't become uniform compared to the Command Center which I got working. The Nexus is not any nexus for an arcade map, but a nexus used for training/custom/vs a.i. type. A probe will warp in this nexus.
I cannot make a probe warp in a customized nexus with a limited queue, otherwise my problem would become bigger.
here is a working copy of your map. I determined the problem was that you were using the wrong type of cancel. unfortunately, pacience is not my strong suite, so I just piled on the cancels. it works exactly like it would if I used only the correct one, however, because the others have no effect. this version works, but you can narrow down the proper one using trial and error if you desire, but its really not necessary.
it seems the problem is that the event "unit uses ability (warp in carrier)" is broken
I created another trigger with that event and the action to display the text "fire". it doesn't work. the problem lies in the event.
UPDATE:
ok, I noticed that in the data editor, it shows only the WoL command card. but in the game, the 2 HotS units are on the command card as well. could that have anything to do with the problem ? i'm not sure.
making more progress. it seems the problem with the event is the ability portion. no events that run using warp in carrier work. (or at least those I tested: issued that order and unit uses that ability at any stage)
UPDATE
yeah I even tried any unit uses any ability with condition triggering ability == stargate- warp in carrier
its as if the stargate isn't using that to build carriers, like its not even registering that the ability warp in carrier is being used.
honestly, im about to write this off as a bug. it makes no sense : /
after realizing that I cant reference the ability "stargate=warp in carrier", I had to create an entirely new trigger for the carrier, but at least it works.
I see. You created a new trigger. It definitely works and I'll definitely use it. Looks like a whole new paradigm though where I won't be needing the old event.
It should simplify all my other coding in the future versions. Thanks a lot!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I am struggling to find the appropriate Cancel ability so the Nexus cancels a probe via trigger.
The trigger looks something like this:
If
When I try to get a reference of the actual ability that the Nexus uses in the Data (F7) to what I guess would cancel a Probe, it says, Queue (5) - Cancel. So I choose that ability in the Trigger (F6); however it still does not work. Please help me, and I hope the solution you offer works (you've tested it yourselves). <sub>N.B. I have seen and already tried using: Cancel Probe - Build (Probe)</sub>(Unit type of Nexus training queue slot 2 item 1) != No Game Link
Then
Unit - Order Nexus to ( Cancel) (Replace Existing Orders)
Debug - Display "No queue!" as debug output using Type 01, and Do display it in the game window
Else
...why don't u just limit the queue to one probe at a time?
@joey101d: Go
I don't think it is possible to manipulate a person from pressing his hotkeys; nor would I know how to lock the ability warp in probe, once a limit condition is met - besides, it won't become uniform compared to the Command Center which I got working. The Nexus is not any nexus for an arcade map, but a nexus used for training/custom/vs a.i. type. A probe will warp in this nexus.
I cannot make a probe warp in a customized nexus with a limited queue, otherwise my problem would become bigger.
Now even if I wanted to limit the queue to one probe at a time, the Cancel ability still doesn't work/ or that I am not finding the right one.
but if the goal is to prevent ppl from queuing probes, limiting the queue to 1 will do the trick, will it not?
oh wait. I see what your saying now. hmm... ill have to look in to this....
@joey101d: Go
I've attached a file already above, as an update. You'll see that I could control queue the Command Center, but for Nexus, I can't.
here is a working copy of your map. I determined the problem was that you were using the wrong type of cancel. unfortunately, pacience is not my strong suite, so I just piled on the cancels. it works exactly like it would if I used only the correct one, however, because the others have no effect. this version works, but you can narrow down the proper one using trial and error if you desire, but its really not necessary.
Thanks for the speedy response! That solves my problem!
If I could award you 10 points for best answer (as in yahoo answers), I would.
Update: Alright...so through the process of elimination I found that the cancel probe queue ability is
Cancel Queue(5) (Passive)
for anyone who wants to know.
happy to help!
you could always like my posts, give me them reputation points ;)
@joey101d: Go
Oh boy, I got a new but somewhat related problem.
I'm working on a queue control for stargate. The Event Unit - stargate is issued an order to Stargate - Warp In Carrier won't fire up.
im currently looking into this.
it seems the problem is that the event "unit uses ability (warp in carrier)" is broken
I created another trigger with that event and the action to display the text "fire". it doesn't work. the problem lies in the event.
UPDATE:
ok, I noticed that in the data editor, it shows only the WoL command card. but in the game, the 2 HotS units are on the command card as well. could that have anything to do with the problem ? i'm not sure.
making more progress. it seems the problem with the event is the ability portion. no events that run using warp in carrier work. (or at least those I tested: issued that order and unit uses that ability at any stage)
UPDATE
yeah I even tried any unit uses any ability with condition triggering ability == stargate- warp in carrier
its as if the stargate isn't using that to build carriers, like its not even registering that the ability warp in carrier is being used.
honestly, im about to write this off as a bug. it makes no sense : /
SUCCESS
after realizing that I cant reference the ability "stargate=warp in carrier", I had to create an entirely new trigger for the carrier, but at least it works.
i'm attaching a working version of your map....
@joey101d: Go
I see. You created a new trigger. It definitely works and I'll definitely use it. Looks like a whole new paradigm though where I won't be needing the old event.
It should simplify all my other coding in the future versions. Thanks a lot!