1. roomId, roomId - not working and not sure how it could guess direction (by coordinate difference?) 2. roomId, roomId, direction - not working (is working fine im 2.1) 3. roomId, direction - working, but first invocation does not connect anything. Second, same, does connect. Seems very unreliable... does it scan whole map in given direction?
For me it is regression. Any chance of fixing this or should I start rewriting code to use setExit() ? Or, if 1 and 3 are impossible to implement properly anyway and setExit() removes stubs anyway, what is the reason for this function then? -- 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
