Mudlet-2.0-test4 released
Re: Mudlet-2.0-test4 released
I think he meant "0<command>") or "0"..command
Re: Mudlet-2.0-test4 released
that's what I was doing, I just didn't throw down the quotes and such in the example
Re: Mudlet-2.0-test4 released
Heiko, I updated my repository to fix the special exits issue and also some places I put return 1 in TLuaInterpreter.
Re: Mudlet-2.0-test4 released
I probably should mention this: A week ago, my profile I use that autoconnects on startup opened but didn't connect as if there is a wifi issue on my part with the maroon text, and my triggers, scripts, aliases, etc got erased, and all the settings as well. I redid all of this, but it was still a pain in the butt. Can you please look into it, Vadi, or Heiko, or someone, if possible. If yes, it would be much appreciated. Or is it fixed in test4?
Re: Mudlet-2.0-test4 released
For things like this, you can just load the previous profile save, and viola you are back. The only thing I can imagine which may cause that was some permissions error in writing, which causes a blank .xml file to exist perhaps.
Re: Mudlet-2.0-test4 released
Just a quick note about getMapVar()....
If you ask for a varible that does not exist(getMapVar("whatever") it raises a Lua Error.... I would think that making it return null would be preferable.
If you ask for a varible that does not exist(getMapVar("whatever") it raises a Lua Error.... I would think that making it return null would be preferable.
Re: Mudlet-2.0-test4 released
or you can use if getmapvar ()[" var"]
Re: Mudlet-2.0-test4 released
getSpecialExitsSwap returns a table that looks something like....
table {
'0closet': 13
'0staircase': 16
'0loset': 17
}
Huh really? What exactly should the behaviors be(or will be)? and what can I do to work around this (I can't see the pattern yet?) I am running test4b on a windows machine.
EDIT: never mind.... I saw the prev posts on this.... looks like I need to build from the source (not something I have done on windows before). A quick description of the "fixed" behavior would still be useful if anyone knows it.
table {
'0closet': 13
'0staircase': 16
'0loset': 17
}
Huh really? What exactly should the behaviors be(or will be)? and what can I do to work around this (I can't see the pattern yet?) I am running test4b on a windows machine.
EDIT: never mind.... I saw the prev posts on this.... looks like I need to build from the source (not something I have done on windows before). A quick description of the "fixed" behavior would still be useful if anyone knows it.
Re: Mudlet-2.0-test4 released
I don't use exit swap so the behavior there is right. Check getspecialexits for correct behavior. I'll update that to give a table of tables too
Re: Mudlet-2.0-test4 released
If I understand you correctly (and I am not sure I do)...
addSpecialExit(currentRoom, room to link, command)
...should work like it used to (no need to add a char to the begining of the command string)
getSpecialExits(room id)
...should return a table of tables with the room id as the key, something like
table{
15:{
1:"closet"
2:0
}
16:{
1:"stairs"
2:0
}
...
}
...and getSpecialExitsSwap(room id) should return something like
table{
"closet":{
1:15
2:0
}
"stairs":{
1:16
2:0
}
...
}
Please confirm for me if this is going to be the new usage of these functions.
(Note: getSpecialExitsSwap is very important for mapping muds that do not support mapping. It allows you to quickly find your given room based on the room you were in and the last command entered.)
addSpecialExit(currentRoom, room to link, command)
...should work like it used to (no need to add a char to the begining of the command string)
getSpecialExits(room id)
...should return a table of tables with the room id as the key, something like
table{
15:{
1:"closet"
2:0
}
16:{
1:"stairs"
2:0
}
...
}
...and getSpecialExitsSwap(room id) should return something like
table{
"closet":{
1:15
2:0
}
"stairs":{
1:16
2:0
}
...
}
Please confirm for me if this is going to be the new usage of these functions.
(Note: getSpecialExitsSwap is very important for mapping muds that do not support mapping. It allows you to quickly find your given room based on the room you were in and the last command entered.)