Yeah, that makes things pretty easy. Thanks again, Zarquan!

A few questions:
(Using Treant system, so I believe any help(code and such) would need to be in Lua.)

1. How do I create a mini-window that captures something? (like how Treant places the MAP in a mini-window as you move)
2. How do I assign a name(varable) to a number. (so say I have a turret12345 and Kundu is in it. What exactly would I need to do so when I type something along the lines of 'Heal Kundu' when I'm locked in the grid it heals kundu (so sending GRID REPAIR MODULE 12345))

Wait, Treant places MAP in a mini-window? How do you do that?

From the looks of the plugin_map file, yes. It creates the window (WindowCreate) and places it in there....somehow...

Ah, ok, time to meddle with that.

EDIT: Nice. I made it work!

There's good documentation on how mini-windows work, which is what the map window is. It's very flexible, and works a lot like a standard windows api call. You create the window, and cause it to redraw every time you wish it to change its display. Parsing into the window is just a matter of creating functions to draw text to the window, and parsing information from the mud into those functions, probably with an omit to keep it from displaying on the world window.

Yeah, I'm trying to do that for capturing channels. The Mushclient documentation webpage is really helpful.


Although, when I said 'meddle' and 'made it work', all I did was look at the code, wonder how to 'activate' it, and found the Plugins option in Mushclient. Heh.

That is more involved than you might think, but the MUSHclient documentation and forums can give you all the details.



Make an alias that sets things in a table. The Lua code might look something like this:


Setup your "heal" alias to accept the name and look up the module number:

I want to add something so that when I find a room with a secret exit, I can type a command, like SECRETEXIT , and have the client
automatically make a trigger so that whenever I walk into the room I get an output echo of something like, Secret Exit: . My question is how can I capture the room title in such a way a that it can send the whole string to the AddTrigger function that Mush has. I know with that room titles by default are brown on black (at least mine are) and that they end with a period and have start line and end line tokens. Can I capture the room name as a subpattern and call is using a wild card? How would I capture it in the first place? In fact, how do you even use wildcards with regex when * has a special meaning of 0 or more?

1. You could use ATCP to capture the room title, which is more reliable than capturing brown text, since you'll run into shield shrines and midnight date changes.
2. I highly recommend you get yourself a good regular expression reference/tutorial to learn about wildcards.

How would I do something like this except for a maro?

How do I make an alias call another alias? For example, I have an alias called "test1" and I want to use it to send something to the world, while calling another alias, called "test2".

Using send to script, use Execute("aliasname").

EDIT: And of course, to send to world, Send("blah")

Execute basically means check for aliases then send - so if you attempt to execute something that isn't an alias, it sends it to the mud.

Meh, should have remembered that! Thanks.

For the non-standard macros, have a look at Accelerator.

Script:
Accelerator("do whatever you want it to")

It executes whatever's in the quotes, so it looks for aliases before sending to world.

Anyone know the exact colours Nexus uses in terms of MUSHClient colours so I can make the latter look more like the former?

Alright, I want to make a macro to basically envenom @weapon1 with mantakaya but I notice that it doesn't see @weapon1 as a variable and it also doesn't send to script. Is there an easier way to do this other than to make something like (this is probably wrong anyway) this below along with an alias:
AcceleratorTo ("Ctrl+F1", "Execute ("alias")", 12)

You need to check 'Expand Variables' for @weapon1 to be converted.

Your accelerator will call the alias without the special parameters, if you just use Accelerator("Ctrl+F1", "alias") or you need to fix your quotes by using single instead of double on one pair or escaping the inside quotes with backslashes.

I made myself a handy little alias to envenom my flails with as many different poisons as I want. It alternates between one weapon and then the other to keep them balanced, so I can do "ev mantakaya calcise dulak" and it'll envenom weapon 1, then weapon 2, then weapon 1 again. If I enter the same command a second time, it does weapon 2, then 1, then 2. (Note: requires the php:split function included with Treant.)

Don't know if this is of any use to anyone...

I wipe and envenom before every attack but sometimes I get a bit carried away and like to spam my macros over and over again which used to lead to me using thousands of poisons so I developed a really basic system of venom tracking on my weapons it assumes that poison is delivered on every strike and resets the venom variables to none. Only works if your weapons don't look the same and for bonecrusher attacks but I'm sure someone could easily modify it.



These go with my combat aliases (which are used in macros or accelerators), I use Larkin's Treant with his autoraze system and a custom made alias he helped me create which means I don't perform any action which follows the alias unless I'm free of entanglement, paralysis, stun and I have balance on both limbs and equilibrium. If you want those you'll have to speak to Larkin about paying for them. The envenom system should still work without the autorazer and balance/aff checker though. Just remove any reference to ART or ACT and adapt the trigger lines above, weapon numbers below and maneuver names to suit.

Does anyone know if it is possible to use the 10-key keys as macros? CMUD recognized them as KEY0...KEY9, and was very handy for me as a knight because I would assign macros based on how a body looks (KEY8 = head, KEY5 = chest and so forth).

It'd be really nice not to have to figure out new ways of associating attacks to keys in my brain.