Uhhh. Using Mudlet for linux. Didn't see anything. Tried using the screendump script, it wouldn't work for me. Maybe I'm just a dunce.

Hey if I do this send ("Phantomsphere attack" ..target). I tried doing the normal way which aliases work , like ^w5$. I did numbers because I think it's easier to remember that. It seems that unite look and move work but not attach shatter or detonate.

Ok, a noob question:

How do you check where the variables are?

Also, how do I flag the variable true or false?

For example, I got a trigger line where enemy uses shield, as a warrior my next attack should be a cleave or raze.

Any thoughts? Mudlet plus Lua is all very confusing for me, just came from MUSHclient. :/

The variables aren't stored in a single place that you can look up, unless you create a script to track and echo them yourself.

Lua code like this should work:
To set your variables:
tar = "orc" -- for words, aka strings, put it in quotation marks. The default assumes numbers, which have no quotation mark requirement.

To see your variables:
echo("\\ntarget = " .. target) -- gives the value of the variable called "target."
echo("\\neshield = " .. eshield) -- gives the value of the variable called "eshield."

To do what you put into your example:
if eshield == 1 then
send("cleave " .. target .. " head") -- sends the command "cleave orc head" to Lusternia, if your target is orc and eshield is 1.
else
send("swing " .. target) -- normal swing if they aren't shielded.
end

To my knowledge you should just be able to paste the above things into trigger lines or aliases and they should start working.

Edit:

Ok, forget the last question I posted, how do I set an alias or trigger to use an existing Alias?

example, the alias 1 is to drink water

so I made a script on alias 2 where

If Hungry == true then
send ("eat food")
else
send ("")
end

Just make an alias with the following Lua code:



For local variables, you will have to use debug.getlocal()

cecho()

expandAlias() is what you need.

Has anyone had an issue with logging not working correctly? I had logging turned on for almost the entire ascension event, but all it captured in the file was a little piece of the middle.

The logging button in mudlet was highlighted the entire time, too.

Some people had it using 2.0 snapshots with html... are you on that?

(I personally just set my buffer to 10mil lines and screendumped at the end)

Yep, I am on 2.0 and using HTML, thanks for the heads up.

Whenever you do a screen dump, is there a command somewhere to export everything in the buffer, or do you just copy and paste it all?

Oh, it's a function/alias: http://forums.mudlet.org/viewtopic.php?f=6...creendump#p4144

Would you be able to put mudlet and any work done on it on an external harddrive and still be able to have it work?

Not as yet, sadly. The paths are still hard-coded at present, as far as I am aware.

Help. Help. I just got back after two weeks or so of "ghosting" and have only checked the code stuff now. I noticed I wasn't able to use the search function. E. g. If I tried searching for the trigger line for eq recovery, search turns up nothing. I replaced my version with the most current one and had refreshed my m&m version as well. At first, the search function worked..then it suddenly stopped working while I was preoccupied with setting pipe stuff in m&m.

okay..it suddenly worked. I have no idea what's happening.

Can I ask for help regarding setting colors in cecho?I can't tolerate uber bright colors and while I prefer dark colors, my eyes can't see too dark colors, too. I'm leaning towards having sky blue, lavender colors and such, but I don't know how to set them. Was only able to set cyan so far. Thanks!

Put showColors() into an alias and run it

just make an alias and put showColors() in the big box?

yep!