MacBook user-- tried Wine/MushClient and wasn't happy with the results. Recently switched from Nexus to Mudlet... so now I am working without any system outside of my own triggers/aliases. Have no coding experience, so a curing system is a long way off.

Wondering if anyone has already tackled writing or converting scripts for Mudlet.

Put your map in a console window:

functions:

function init()
resolutionX, resolutionY = getMainWindowSize()
createMiniConsole("mapcap", resolutionX-440, 50, 400, 350)
setBackgroundColor("mapcap", 0, 0, 0, 0 )
setMiniConsoleFontSize("mapcap", 8);
end

function mapCapture()
selectString(line, 1)
copy()
appendBuffer("mapcap")
deleteLine();
end

Triggers:

Name: Map start
Regex: v\\d+ +$
Code:
enableTrigger("Map capture")

Name: Map end
Regex: -?\\d+:-?\\d+:-?\\d+
Code:
disableTrigger("Map capture")
mapCapture()

Name: Map capture
Regex: ^.*$
Code:
mapCapture()

Set the last trigger to be disabled. The triggers will enable it for you.

Looks like this:

Building a defence tracking system:

First, build a reset list with the names of all the defences you use:

function def_reset()
def = {}
def.weathering = 0
def.vitality = 0
def = 0
def.thirdeye = 0
def.nightsight = 0
def.deathsense = 0
def.insomnia = 0
def.selfishness = 0
def = 0
def = 0
def = 0
def = 0
def = 0
def = 0
def.resistance = 0
def = 0
def.constitution = 0
def.adrenaline = 0
def.flex = 0
def = 0
def = 0
end

Clearly mine is a work in progress, I don't have the elixers, herbs etc up there yet.

Next build the infrastructure:

function def_on(d)
if def == nil then
fg("red")
echo("Error: Incorrect defence variable assigned to above trigger.")
else def = 1 end
end

function def_off(d)
if def == nil then
fg("red")
echo("Error: Incorrect defence variable assigned to above trigger.")
else def = 0 end
end

function def_def(d)
def_on(d)
end

function list_defs()
local i
i = 0
fg("red")
bg("black")
echo("\\nCurrent Defs: ")
fg("white")
for k, v in pairs(def) do
if v == 1 then
if i == 0 then echo(k) else echo(", " .. k) end
i = 1
end
end
if i == 1 then echo(".") end
i = 0
fg("blue")
bg("black")
echo("\\nMissing Defs: ")
fg("white")
for k, v in pairs(def) do
if v == 0 then
if i == 0 then echo(k) else echo(", " .. k) end
i = 1
end
end
if i == 1 then echo(".") end
end

Using the above, you can set triggers to do -
def_on("defname") to tell your client that you have the def "defname" set to on
def_off("defname") to tell your client that you have the def "defname" set to off
def_def("defname") to tell your client that you have the def "defname" set to on, and that the information was recovered from the DEF command. This is a little bit of indirection in case you want to expand the system later.

Now you need to do is setup the triggers to each of the ON and DEF phrases for each def. I.e. for weathering

Begin of line substring: A brief shiver runs through your body.
Code: def_on("weathering")

Begin of line substring: Your body is weathering the storm of life a little better.
Code: def_def("weathering")

Lastly, setup this alias:

Alias name: defs
Pattern: ^defs$
Code: list_defs()

This will make you a list of what defs you have on, and are missing.

Hrm. Doesn't seem to work for me, even given not enabling that last trigger. Just to check, should the function be put into a script?

EDIT: On a sidenote, it seemed to affect READLOG in not being able to display... at all!

Functions go into scripts, yep. You can chuck the whole functions section into one script object.

No wonder, I forgot the names on the triggers!

The first trigger is named Map start
The second trigger is named Map end
The third is named Map capture <--- this bit is important

I'll update it in the original post.

Script:


Usage:
nlink 20
It will link until 20% has been added to your reserves. Not a difficult script, but handy. Easy enough to adapt it to harvesting/crafting etc as well.


Note:
My scripts require the following function, though the alternative is to replace all instances of "sendr" with "send".


There is also an alias that changes the values of commandEcho between 0 and 1
I originally added this function when Mudlet didn't echo commands send with send(). I use it for debugging scripts etc. Even though there is an option in preferences to show commands sent, I still prefer to use sendr() because I can toggle it on/off from the command line. Easier/quicker. Plus, I prefer the way this function displays the echo.

anyone know how to make a window where I can keep "info here" updated?

Duuuudeee, necro much! Ask here. As for IH, you will want to create a miniconsole, capture the IH output and direct it to there. My two cents are that you should bind who here / ih to numpad 5 so you can spam it while walking about.