mudlet-makers team mailing list archive

[Garagoth <1114594@xxxxxxxxxxxxxxxxxx>]

I see this is a must have for 3.0 release. I am testing my mapper script wrote for 2.1 on 3.0-iota.
Trouble that I have  is with connectExitStub(). I am passing 3 arguments to it: roomId, second roomId, direction number.
All I get is error message: <connectExitStub: Need a direction number (or room id) as 2nd argument> and script execution is stopped.
I am sure that this works in 2.1 and all roomIds exist before calling this function.
Calling it with 2 arguments, both roomIds, also produces same error.
Calling it with roomId, direction# makes it stop complaining, but connects rooms on second invocation - first does nothing.

Regards,
Garagoth.

-- 
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