Mudlet features and API requests
Re: Mudlet API requests
Would like a getAreaName(areaID) function, ala getRoomName(roomID).
Re: Mudlet API requests
Script editor request:
When editing a parent script object, and clicking save (or just clicking on it, which causes a recompile of the contents) can the child script object also be recompiled?
At the moment I organise things like this:
Parent Object: "Auto Bashing Script"
Script:
av.bashing = {}
av.bashing.denizenTable = {
bleh blah
blah bleh
}
av.bashing.funcs = {}
Child Object: "Functions for adding appropriate targets"
Script:
function av.bashing.funcs.addtarget(name, id, mood)
blah blah
end
av.bashing.funcs.activetarget()
blh blah
end
Child Object 2: "Pick best target"
Script:
function av.bashing.funcs.picktarget()
blah blah
end
If I click on the parent object, the functions are set to nil. I think clicking on the parent object ought to set them to nil, and then recompile the child scripts, recreating the functions.
Perhaps it doesn't work that way for a specific reason, if that is so - please tell me so I can adjust my scripting style. Every time I make a change to my scripts when writing them initially, I have to click on the parent, then each individual child object to reinitialise it. I can't just do:
av.bashing = av.bashing or {}
because when debugging, I need it to change when I make changes, not stay the same.
When editing a parent script object, and clicking save (or just clicking on it, which causes a recompile of the contents) can the child script object also be recompiled?
At the moment I organise things like this:
Parent Object: "Auto Bashing Script"
Script:
av.bashing = {}
av.bashing.denizenTable = {
bleh blah
blah bleh
}
av.bashing.funcs = {}
Child Object: "Functions for adding appropriate targets"
Script:
function av.bashing.funcs.addtarget(name, id, mood)
blah blah
end
av.bashing.funcs.activetarget()
blh blah
end
Child Object 2: "Pick best target"
Script:
function av.bashing.funcs.picktarget()
blah blah
end
If I click on the parent object, the functions are set to nil. I think clicking on the parent object ought to set them to nil, and then recompile the child scripts, recreating the functions.
Perhaps it doesn't work that way for a specific reason, if that is so - please tell me so I can adjust my scripting style. Every time I make a change to my scripts when writing them initially, I have to click on the parent, then each individual child object to reinitialise it. I can't just do:
av.bashing = av.bashing or {}
because when debugging, I need it to change when I make changes, not stay the same.
Re: Mudlet API requests
I haven't had a problem with it, since if I'm working with a single script - clicking on it recompiles it, and if I'm working on multiple ones - switching between them recompiles the old ones as well.
Not sure if this behavior change is good yet.
Not sure if this behavior change is good yet.
Re: Mudlet API requests
I ran into an issue, searchRoom returns a table of room names but it uses the room name as a key, if whatever mud you are mapping has many rooms of the same name, it will only return the last one.
I would like a function similar to searchRoom that returns the list of matching rooms with the roomID as the key value. (allowing duplicate room names)
-Omit
I would like a function similar to searchRoom that returns the list of matching rooms with the roomID as the key value. (allowing duplicate room names)
-Omit
Re: Mudlet API requests
searchRoom has been fixed in git and latest snapshots for a bit now.
Re: Mudlet API requests
fixed? In what way? I am on the latest (or so I thought).Vadi wrote:searchRoom has been fixed in git and latest snapshots for a bit now.
Re: Mudlet API requests
Hm, -not- fixed. Perhaps it was fixed before but the fix was reverted?
Re: Mudlet API requests
Would like to see the align functions written by demonnic to be added as regular mudlet functions. Also several other functions that are very useful made by him. Will post them first chance I get.
-
- Posts: 186
- Joined: Sun Nov 14, 2010 5:57 am
Re: Mudlet API requests
Right now when you log it logs after triggers have fired. Could we get an option to log mud output pre-triggers?
Re: Mudlet API requests
Using your own logger would accomplish this (have the trigger before anything else).