MAG - Mudlet Aardwolf GUI

[txandi]

Thanks for this - it's amazing!
I was wondering what those numbers mean next to the {affoff} and other { } echoes mean (e.g. {affon}119,540 and sometimes {sfail}119,0,1,-1)... they keep showing up and I have no idea what's going on!

[fxf]

Thanks for the update! It's much easier to move to new version now

[lex]

to txandi
hi, thanks for trying it out. {sfail}119,0,1,-1 and {affoff} means that some spell just expired or that you failed to cast spell. (There might be something else, but I won't know unless you'll copy and paste it here.)

You can easily get rid of those by:

• open script editor
• navigate to Triggers > MAG > Gag/Delete Lines (3rd from top)
• add {sfail} (scroll little bit down so you can add it as number 5)
• add {affoff}
• Save Item

[txandi]

Hi again, I had another question - I'd like for 'says' to be viewed in the main window instead of the right chat window. I looked at the script but couldn't figure out what to change - how could I modify it so I see what people are saying in the main window? Thanks.

[lex]

Send following command to mud (this will stay only for current session)
tag says off


Permanent change
Open script editor and navigate to
Scripts > MAG > Mudlet Aardwolf GUI > MAG channel 102

Change line 19 to (replace \1 with \2)
"\9\2", -- Say tags

[gaijincory]

This is a really fantastic interface. I use it on a Mac running Snow Leopard, and it's just beautiful. I'm trying to figure a way to get the other [non-main] windows to honor the antialias setting, but haven't figured it out yet... wasn't sure if there is an AConf variable, but just downloaded the package five minutes ago.

I had to register on this board to say thanks for the contribution!

Hello,

I would like to introduce MAG (Mudlet Aardwolf GUI). Comprehensive set of triggers, scripts and aliases to enhance gaming experience on Aardwolf.

This initial release of MAG contains following:

• chat log (all communication and also some information messages won't get lost in battle spam)

• extra info (contains quick overview of quest and campaign)

• mini map (mini map capture, so you can see your surrounding during battle)

• status area (extra stats information and monitor)

• statistic (tracking kills, gold, qp and experiences)

• re-arm script (disarm and overpower)

• + tons of useful aliases and triggers

Feel free to try it and pass back any feedback and comments
Have fun


PS: I will upload release in following post, so stay tuned

[lex]

Thanks for great feedback.

To be honest I am not sure if it's possible to use anti alias in miniconsoles (non main window) at the moment. You also cannot use different font there, so it's better if you can stick with default font. This something that's needs to be implemented within Mudlet, but there are different priorities for now (for example automapper).

Make sure that you'll check following page for latest MAG versions and documentation:
MAG AardWiki

[gaijincory]

Thanks for the reply lex. The wiki page you've added to AardWiki looks great, and was easy to follow. I will definitely be following updates from there. Keep up the great work, and thanks again!

[Aeki]

Hello.

First let me thank you for working on this script (also thanks to those working on the client obviously).

I'm using latest (1.1.0) version of MAG and I got some problem.

Upon connection it looks like it has problems sending initialization command on login to channel 102.

This is the error log:

ERROR:] object:<event handler function> function:<GeyserReposition>
<>
[ERROR:] object:<MAG Startup - New Connection> function:<Trigger60>
<[string "..."]:39: attempt to call global 'sendTelnetChannel102' (a nil value)>

I don't get any feedback from the mud about tags activation, nor I see the output from
cecho("\n<red>---- Setting up MAG tags ----\n")
(from MAG.avatarSetup(), after MAG.c102.send(MAG.c102.on) )

The rest of the script (MiniMap, StatusArea, TickTimer..), however, seems to work perfectly: I tried running once the custom MUSHclient (which activates mostly the same tags on login, I suppose) and then reconnecting via Mudlet, and, with the tags now active, all the scripts seems to work perfectly (but I still get the error on login).

So the only problem should be in the initialization at login.

Actually I'm not even sure it's a fault of the script, since nobody else seems to have this problem, so maybe is there something I should check about my connection, settings...?

Thanks.

[Vadi]

Your mudlet installation seems to be too old and is missing features.