mudlet-makers team mailing list archive

[Stephen Lyons <1173407@xxxxxxxxxxxxxxxxxx>]

A quick check suggests that the following Lua functions (ie in TLuaInterpreter.cpp) use an index that starts at zero and that the index is directly returned as a "key" thereby creating a table with keys including "zero" - I had wondered why some lua display(somefunction()) had produced tables/lists with a "[0]=..." entry, now I know!:
getAreaRooms()
getExitStubs()
getRoomsByPosition() *** Just found that the TArea::getRoomsByPosition() that this uses is broken (is not currently area selective/specific, possibly introduced by RoomDB introduction...) - I've posted a possible fix, see https://bugs.launchpad.net/mudlet/+bug/1174484 ***
searchRoomUserData()

I am testing now to see if adding 1 to the index when it is pushed into
the results table on the stack in those four functions has any side
effects...

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1173407

Title:
  getRoomsByPosition()'s table indexing starts at 0

Status in Mudlet the MUD client:
  New

Bug description:
  getRoomsByPosition()'s table indexing starts at 0, while it should be
  starting at 1. We would need to see if any public scripts are broken
  by this before fixing, if we can at all.

  All future functions should start their indexing at 1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1173407/+subscriptions