Page 1 of 15
Mudlet 3.0.0-delta (preview #4)
Posted: Tue Jan 20, 2015 9:07 am
by Vadi
Mudlet 3.0.0-delta is here! This is a delta release - the
fourth preview of what Mudlet 3.0 will look like. In this release we focused on fixing the search editor content replacement bug that occured in the gamma.
[/size]
[/size]
Please provide all feedback and problem reports on 3.0.0-delta here! Feature requests can be done in our
dedicated thread.
Re: Mudlet 3.0.0-delta (preview #4)
Posted: Tue Jan 20, 2015 4:48 pm
by Belgarath
Thanks Vadi! Looking smooth so far, apart from blackness in the button menu and it resizing itself (issues from beta release). Will let you know if anything unexpected happens.
EDIT: It was working well for hours and after I finished I a fight I clicked on the search box and it crashed.
Re: Mudlet 3.0.0-delta (preview #4)
Posted: Wed Jan 21, 2015 10:46 pm
by Arcraban
There is something unexpected here, and if I recall correctly it was also in the previous release.
When I make a link between two rooms and then delete one of them the link from the existing room to the deleted room (it's ID) is remembered in "exits". To avoid problems with a connection to a non-existent room I want to remove it manually. To do this I need to right-click on the map, select "exits" and delete one of the IDs, but exactly when I click on "exits" Mudlet crashes
Re: Mudlet 3.0.0-delta (preview #4)
Posted: Thu Jan 22, 2015 1:39 am
by Israafiyl
using Gamma and it seems some of my triggers, scripts, aliases, keybindings (when I switch back and forth between such while making them) are being filled with info from the previous thing I was looking at....
Re: Mudlet 3.0.0-delta (preview #4)
Posted: Thu Jan 22, 2015 2:04 am
by Vadi
Yes, that is an issue with the gamma that is fixed in the delta now - please update.
Re: Mudlet 3.0.0-delta (preview #4)
Posted: Thu Jan 22, 2015 2:05 am
by Vadi
Arcraban wrote:There is something unexpected here, and if I recall correctly it was also in the previous release.
When I make a link between two rooms and then delete one of them the link from the existing room to the deleted room (it's ID) is remembered in "exits". To avoid problems with a connection to a non-existent room I want to remove it manually. To do this I need to right-click on the map, select "exits" and delete one of the IDs, but exactly when I click on "exits" Mudlet crashes
Thanks for reporting that, will have a look.
Re: Mudlet 3.0.0-delta (preview #4)
Posted: Fri Jan 23, 2015 9:43 pm
by Arcraban
I tried to addMapMenu() with some addMapEvent()s and it worked awhile, but since the beta release it doesn't work anymore.
Here's a sample code:
addMapMenu("create exit stub")
addMapEvent("nw", "createExitStub", "Create Exit Stub", "northwest")
addMapEvent("n", "createExitStub", "Create Exit Stub", "north")
addMapEvent("ne", "createExitStub", "Create Exit Stub", "northeast")
addMapEvent("e", "createExitStub", "Create Exit Stub", "east")
addMapEvent("se", "createExitStub", "Create Exit Stub", "southeast")
addMapEvent("s", "createExitStub", "Create Exit Stub", "south")
addMapEvent("sw", "createExitStub", "Create Exit Stub", "southwest")
addMapEvent("w", "createExitStub", "Create Exit Stub", "west")
addMapEvent("u", "createExitStub", "Create Exit Stub", "up")
addMapEvent("d", "createExitStub", "Create Exit Stub", "down")
The problem is that when I right-click on the map and then put the mouse cursor on the "create exit stub" the submenu doesn't show up, there's only a little rectangle in the top-right corner.
Mapper screenshot.
The second problem appears when I do sth with the right-click on the map i. e. "delete" the room or display "exits" window. After that I can't type anything in the command line, even when I click on it. Only clicking on the search box and again on the command box allows me to type. This isn't a big problem, but IS a problem.
Re: down
Thanks, didn't notice.
Re: Mudlet 3.0.0-delta (preview #4)
Posted: Fri Jan 23, 2015 10:59 pm
by Vadi
"create exit stub" is not the same as "Create Exit Stub" though. Use:
addMapMenu("create exit stub")
addMapEvent("nw", "createExitStub", "create exit stub", "northwest")
addMapEvent("n", "createExitStub", "create exit stub", "north")
addMapEvent("ne", "createExitStub", "create exit stub", "northeast")
addMapEvent("e", "createExitStub", "create exit stub", "east")
addMapEvent("se", "createExitStub", "create exit stub", "southeast")
addMapEvent("s", "createExitStub", "create exit stub", "south")
addMapEvent("sw", "createExitStub", "create exit stub", "southwest")
addMapEvent("w", "createExitStub", "create exit stub", "west")
addMapEvent("u", "createExitStub", "create exit stub", "up")
addMapEvent("d", "createExitStub", "create exit stub", "down")
Re: Mudlet 3.0.0-delta (preview #4)
Posted: Sat Jan 24, 2015 7:27 pm
by Belgarath
I think this version is deleting map data. A good few areas were suddenly erased from my map while using it.
Re: Mudlet 3.0.0-delta (preview #4)
Posted: Sun Jan 25, 2015 10:16 pm
by Arcraban
Sth strange here:
Alias:
Name: change type
Pattern: ^change type (.*)
Big box:
setRoomChar(nmapper["activeRoom"], typeChar[matches[2]])
setRoomEnv(nmapper["activeRoom"], typeEnv[matches[2]])
typeEnv = {
Shop = 258
}
typeChar = {
Shop = "S"
}
nmapper["activeRoom"] is an ID of a room
when I write in the command line:
lua setRoomChar(nmapper["activeRoom"], typeChar["Shop"])
lua setRoomEnv(nmapper["activeRoom"], typeEnv["Shop"])
everything works
but when:
change type "Shop"
there is an error: <setRoomArea: wrong argument type>
and when I change text in a big box (change order):
setRoomChar(nmapper["activeRoom"], typeChar[matches[2]])
setRoomEnv(nmapper["activeRoom"], typeEnv[matches[2]])
there is another error: <setRoomEnv: wrong argument type>