Commands within the Java client itself...

by Unknown

Back to Mechanic's Corner.

Unknown2005-06-28 19:52:48
...since the help button seems to take me to an irrelvant page on Achaea.

Is there some command, character, etc that can be used to separate a line into two separate commands? Basically, how do I take something from my rift and use it with a single command?

Also: Are there triggers built into the javaclient, or is that why everyone uses something else?
Unknown2005-06-28 20:06:35
The Java client does have triggers, but they use odd pattern symbols and don't do as much as many other clients. There is a new Java client in development which may one day be made available to all IRE games, and it has much more capability for triggers and scripting.

To execute more than one command, don't you just put each on a separate line in the value for your alias or trigger? (I don't use Java, so I'm just guessing as to something you can try.)
Vix2005-06-28 20:13:37
Yeah, in the little box for commands you just put them on separate lines. For example, if you had an alias for outrifting and eating reishi, it'd look like this.

Alias:
reishi

Commands:
outr reishi
eat reishi
Manjanaia2005-06-28 20:16:30
EDIT: Nevermind.
Unknown2005-06-29 01:58:25
Here's another thing, what's the actual syntax to change variables for the client? I think I'm using commands to change variables within the mud itself and not for the client. And I think the help button is giving me information that is simply wrong.

...did I misread it, or is there a real helpfile somewhere that I'm not aware of?
Shiri2005-06-29 03:53:39
There isn't a real helpfile somewhere you're not aware of. And it's REALLY annoying.

To set variables, use

#set variablename variablevalue

To execute a variable, it's $variable

When you use {w} in a trigger, it sets that variable as $1 by default, or $2, $3 etc. depending on how many {w}s you use. NEVER use {*}s, it keels over and dies if you try.

And the help file is outdated by about four years, rather than wrong.


Shiri2005-06-29 03:57:10
In case you're wondering, the #send command is wonderful for sending an alias on a trigger that really commonly occurs and not spamming yourself when you unset the alias (with the #alias and #unalias commands, not the in-game ones), but using it with two values (I tried to use it with harvesting triggers so that it would #send $pick $herb) seems to want to send it as two seperate values rather than all in one line, so if you're trying to do that sort of thing, just use it without the #send.
Unknown2005-07-13 22:47:11
I'm having a similar problem here. (Tam, instead of setting variables via text, maybe use the Settings button and minimize your window for a more user-friendly variable/alias/trigger setter).

My problem is that if I set multiple commands (for example N, E, N but all on different lines) it seems to try to execute them all at once. ie, I get error messages saying "You cannot go that way from here," instead of going N, then E, then N as I'd like. Is there some sort of wait or delay command? Would this even help?
Shiri2005-07-14 05:18:38
There is no wait or delay command. Which is highly annoying. You're going to have to put up with only sprinting if you want to autowalk like that (which carries you all the way in a straight line, and isn't always possible. Especially if you don't have the skill. Warriors, Wiccans, and Druids all have it.)
Unknown2005-07-14 20:28:52
Well, that's useful at least. The walking wasn't the only thing I wanted, or at least I rather suspect it soon won't be, but if nothing else, I'll look into learning how to sprint. Thanks!
Shiri2005-07-15 05:21:22
It's good for little aliases, like I have one which takes me from the Moonhart Mother Tree to Celest by sprinting around and up into the commune, and then into the portals and out into Celest. ('course, us JAVA people have to make it two aliases, because we have no #DELAY or whatever, and you can't walk even one room while sprinting because you get the "hastiness" stuff, so there's a slight kink in the path.)