Currently: 3. should work with direction as one of the given strings OR numbers (1 to 12).
2. not working due to a coding bug that treats the second roomId as a direction number (and only accepts value of 1 to 12) before even spotting that there are three rather than two arguments. 1. Can't work as I see it as it will be mistaken for 3 since we revised it since the 2.1 release to allow direction numbers (which will be more code friendly going forward to supporting more than just English language). 3. should work by detecting the *nearest* room in the *direction given* and making a *one* way exit from the first room to the second in that direction on the basis of the x,y,z coordinates of all the rooms considered (i.e. in the same area). setExit() will effectively do what 2 tries to, but without the code in front of me this instant I am not sure whether 2. was to make a one-way exit or to do both-directions, whereas setExit() only makes a single exit direction link and will need to be invoked with the two room ids swapped and with the opposite direction for the second call. The mention for removing stubs is that old code (possible back as far as 2.1 would allow both a stub and an actual exit in the same direction - this is logically inconsistent, so now you are not permitted to make a stub exit exist for a direction that there is a real exit in and making a real exit in a particular direction will automagically remove a corresponding stub exit. This consistency is now also checked for and if a problem is encountered during loading a Mudlet Map file then it is automatically cleaned up but noted in the errors.txt log file and also on-screen if that option is enabled... -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1114594 Title: setExit, setExitStub, queryRoomExits - fix inconsistency in direction parameters and returned names Status in Mudlet: In Progress Bug description: setExit() accepts a number or a short direction name (like "e", "ne") setExitStub() accepts a number as direction getRoomExits() returns a long direction name (like "east", "north") connectExitStub() is even more bizarre, it does not work with 2 arguments as stated in manual as well setDoor() and getDoors() requires and returns direction in short form ("e", "ne") Also writing scripts for non-english mud is painful as I have to maintain 3 name mappings just for directions... translating in one or another way. speedwalk also outputs short directions and I have to translate them into correct ones (and why up and down was not shortened as well?). Is it possible to make it consistent and more friendly? Make it all english short names for example or numbers everywhere (less friendly IMHO)? Mudlet: 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1114594/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : [email protected] Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
