CLIENT: Dump of mudlet related things for y'all

[Adael]

I hadn't had a chance to reply, but Reyne's reply is nearly spot on.

The only thing that I would change is the regex pattern. As written, it will capture, e.g., "an ancient tree" as the targetting variable - but trying to "kill an ancient tree" will likely not give the response you want

The pattern I had was

Code: Select all

(\S+): (\S+) >

which can be used to capture the last word of whatever you're engaged on (in my example case, just "tree"), which I've found is typically a keyword that can be used for most mobs. For pcs, this will always capture their name. And in this case you would use

Code: Select all

CurrentEnemy = matches[2]

to set the target, as the pattern was slightly different.

[Jada]

This works perfectly. Thanks to you both.

[Adael]

Fixed a bug in the equipment trainer that was *still* requiring the equipment database package to be installed in the right order
Hopefully the problem is gone now so that it doesn't matter what is installed first...

[Thore]

Had installed Mudlet fresh on a new PC. Installed the wotpack. Got the mapper working. Went to install comms window and Mudlet crashed and when I re-opened, all of my packages were gone. Reinstalled wotpack, and when I went to load the mapper it crashed again.

Any idea what might be causing this?

[Adael]

The first line of the readme

There’s a bug in mudlet 4.17 when installing packages from the command line. You can downgrade to 4.16 (there’s a link in the readme) and that should work fine. Hopefully they release 4.18 soon though.

If you have your old PC though, it’s a lot easier to transfer one file to your new PC and have your exact same setup with no work.

[Thore]

Shoot. Ok - we mudders skim text don't ya know I'll see what I can do.