Public bug reported:
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
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?
Mudlet: 2.1
** Affects: mudlet
Importance: Undecided
Status: New
** Tags: exits
--
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 the MUD client:
New
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
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?
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