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
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
Looking at the code in TLuaInterpreter::connectExitStub(...) in the C++ code I
see that it is supposed to exist in two forms:
A) connectExitStub( (number)fromRoomId, (number OR string)direction)
B) connectExitStub( (number)fromRoomId, (number) toRoomId, (number OR
string)direction)
If the
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: and script execution is stopped.
I am sure
Work in progress on the above, should also act on
https://bugs.launchpad.net/mudlet/+bug/1097543
** Changed in: mudlet
Status: Fix Committed => In Progress
** Changed in: mudlet
Assignee: Chris (chrismudlet) => Stephen Lyons (slysven)
--
You received this bug notification because
That sounds good.
--
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
There is a bit of a dichotomy with the way that exit directions are
treated but in the long term I think we may have to split exit
directions into two groups, the normal exits which we can represent
with a (short unsigned) numeric constant internally and special exits
with a string representation.
This has been changed so any variation of direction is now accepted for
exit arguments (#,short,long names)
** Changed in: mudlet
Status: New = Fix Committed
** Changed in: mudlet
Milestone: None = 3.0
** Changed in: mudlet
Assignee: (unassigned) = Chris (chrismudlet)
--
You
** Changed in: mudlet
Importance: Undecided = Low
--
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
** Description changed:
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
10 matches
Mail list logo
