There is no checkbox for that in the macros screen, though.

You'll have to either set the macro to call an alias, or use the full GetVariable("variablename"), I expect.

As far as I can remember, the 'repeat on same line' option only works for highlighting, and not for scripting. You can, however, catch it all in a single trigger then split it up. You may also be able to use a series of triggers, each trigger capturing and processing only one of the positions in the rift list, but I haven't tried that myself.

I just ended up using a single trigger with optional elements to capture it all. Just wish I knew for certain why the other way didn't work.

Another question. Below is a bit of code I wrote. It's meant to change my nextweapon variable to 1 if it is on 0 and vice versa whenever I envenom my weapons. It seems to be firing, but the variable isn't changing. Any ideas?

A few problems here, firstly it should read @nextweapon, not "@nextweapon"
secondly, you are comparing the value to a number:



but then trying to assign a string to it:



so, if we correct these we get:

Mushclient stores all variables as strings anyway. Meaning that you need the quotes in the compare (if x == "y") but not in the assignment (for numbers, at least, although you should probably have them anyway for cleanliness' sake). Unless you use tonumber.

Thanks to Kuroi and Esano for the help. That part works now. Next problem! The following alias is meant to envenom mantakaya to my first weapon if nextweapon is set to 1 and to my second weapon if it is not set to one. What's wrong with it?

Unless you have nextweapon defined as a local variable or some such, it's null. Use GetVariable("nextweapon")

Aha! That worked. Thanks

ah yes true! well I still do it anyway for cleanliness' sake, the real problem is the quotes around the variable.

EDIT:
Also, if you want to carry on using variables the same way, this should work:

I'm on Mushclient currently and I want to have MXP on to take advantage of Mudbot. However, it's messing me up in that all the < and > signs in Lusternia (such as for family tree and so on) get read by Mush as MXP tags, and then get omitted.

Is there any way for me to fix this, or do I just have to live with the random line truncations?

AFAIK, there is no way around that. You either live with the omissions or live without MXP. (Though I suppose you could try some form of trigger to capture and re-echo certain things, like GTS, but I've never felt it worth looking into.)

Thanks. I worked around it. I'd originally changed Treant's mapper around a bit so it captured the output of Mudbot's map window instead of the game map because MAP CONFIG ON was slowing me, and now I'm just triggering it to do lmap upon seeing room names, which isn't so different.

Edit: Another question: is it possible to get on-click scripts on Mush? I remember someone once made a shopping trigger that would probe things if you clicked them, that was useful.

If you use that method you need to clik on expand variables, I also have perfect success with if/then statements when I put both the variable name and the variable value in quotation marks so:

That wasn't really what I meant, if you were replying to me. In ZMUD you could have this script that went:

#sub {~%1%2:~}

and it would let you click on whatever it was you'd subbed in order to execute probe %2.

Edit: Oops, looks like you weren't talking to me. But anyway!

I use the in-game map mostly because it's more correct 90% of the time and actually helps me build my LMap. When you get tossed around by waves/earthquakes or otherwise moved to an unknown location, the in-game map tells you right where you are every time.

And thank goodness for that!

The IG map is better 99% of the time for normal exploring/ quick walking use. The LMap is better when you need to speedwalk to a place with just a vnum.

Exactly. I'd rather see where I am using the in-game maps, but I speedwalk to everywhere using LMap, especially since it tells me the numbers on things like scrying, deathsight, etc.