apply_verb
- Thread starter Blazer
- Start date
Apparently you need to quote the whole command line of EQ2execute to make it work if the verb you are trying to apply contains spaces.
EQ2execute "/apply_verb ${Actor[tradeskill_work_order_desk].ID} Search Invoices"
The above worked when I tried it.
I would really like to see Ama add a DoVerb fuction to Actor to make it easier to use verbs. Somthing like the following would be a little easier to read and clearer in purpose.
Actor[tradeskill_work_order_desk]
oVerb(Search Invoices)
v01d
P.S. This method allows you to use the cloud stations in KoS as well as anything else available via right click menu, like disarm trap, mentor etc.
P.P.S Using the loot verb on corpses cleans up empty corpses.
EQ2execute "/apply_verb ${Actor[tradeskill_work_order_desk].ID} Search Invoices"
The above worked when I tried it.
I would really like to see Ama add a DoVerb fuction to Actor to make it easier to use verbs. Somthing like the following would be a little easier to read and clearer in purpose.
Actor[tradeskill_work_order_desk]
oVerb(Search Invoices)v01d
P.S. This method allows you to use the cloud stations in KoS as well as anything else available via right click menu, like disarm trap, mentor etc.
P.P.S Using the loot verb on corpses cleans up empty corpses.
Since it's possible without isxeq2 and since if it were added to isxeq2 it would do exactly the same thing, it's not worth the time and energy to put it in. Moreover, I do not see it as complex at all, the only thing you have to know is the syntax. All we need to do is add a section to the wiki with "useful but undocumented EQ2 slash commands".
And, using the quotes around the entire eq2execute is logical. The syntax of eq2execute (straight from the wiki) is "EQ2Execute <command>", and since the command is the entire line..then it should be in quotations. In fact, anything used with eq2execute that contains more than one token should be contained within quotation marks (since quotation marks are used by InnerSpace to tokenize arguments on the command line.)
Quest Progress
I am also messing around with this writ thing, maybe I will learn more about ISXEQ2 in the process. I was messing with the Quest Data example posted in the wicki by Traill, and there is a problem:
1. For example, the rush order says "I need to mix a glass of Wild Apple Juice", but it doesn't tell how many...
Is it possible to read directly from the Journal, is there a function, would I have to use the EQ2UIElement to read from the journal?
Also, I have this so far if it helps anyone: (Catheryn Wilona is the Qeynos Rush Writ lady), this gets you to the part where you are ready to Look for your invoice, which everyone is still stuck on..
Actor[Catheryn Wilona]oTarget
eq2execute /hail
wait 10
EQ2UIPage[ProxyActor,Conversation].Child[composite,replies].Child[button,1]:LeftClick
wait 20
EQ2UIPage[MainHUD,RewardPack].Child[button,RewardPack.Accept]:LeftClick
I am also messing around with this writ thing, maybe I will learn more about ISXEQ2 in the process. I was messing with the Quest Data example posted in the wicki by Traill, and there is a problem:
1. For example, the rush order says "I need to mix a glass of Wild Apple Juice", but it doesn't tell how many...
Is it possible to read directly from the Journal, is there a function, would I have to use the EQ2UIElement to read from the journal?
Also, I have this so far if it helps anyone: (Catheryn Wilona is the Qeynos Rush Writ lady), this gets you to the part where you are ready to Look for your invoice, which everyone is still stuck on..
Actor[Catheryn Wilona]
oTargeteq2execute /hail
wait 10
EQ2UIPage[ProxyActor,Conversation].Child[composite,replies].Child[button,1]:LeftClick
wait 20
EQ2UIPage[MainHUD,RewardPack].Child[button,RewardPack.Accept]:LeftClick
I'm working on it; however, it's not going to be easy, and may not be attainable.
Why can't you use mouseto and so forth (the innerspace functions) for now until it's figured out? The window should be on the same place every time, and then people will just have to manually set the location on the screen for their own installations. No other windows should be up and in the way at that point.
Why can't you use mouseto and so forth (the innerspace functions) for now until it's figured out? The window should be on the same place every time, and then people will just have to manually set the location on the screen for their own installations. No other windows should be up and in the way at that point.
Nope, it won't be easy. It is highly probable that this is the exact reason that SOE made the writs work this way: to make it difficult to automate.
However, it's a simple thing to use the mouseto and manually click. The script could also bring up a UI that would explain how to set those values and allow the user to imput them during the first usage.
I will continue to look for it; however, it's definately not obvious or easy.
However, it's a simple thing to use the mouseto and manually click. The script could also bring up a UI that would explain how to set those values and allow the user to imput them during the first usage.
I will continue to look for it; however, it's definately not obvious or easy.
For anyone who hasnt saw it yet, Amadeus posted a fix for the Dialog we experienced problems with.
http://www.isxgames.com/forums/showthread.php?t=392&highlight=writ
http://www.isxgames.com/forums/showthread.php?t=392&highlight=writ