Brief summary of issue / Description of requested feature:
connectExitStub(fromID, direction or toID[, optional direction])
In the above, you can see that connectExitStub() is supposed to accept a room id as the 2nd parameter and optionally a direction as the third.
In my testing the function connectExitStub() only works if the 2nd parameter is a direction number such as:
connectExitStub(fromID, directionNum)
For me this means using connectExitStub() will not work to connect the exits between rooms in different Areas.
I had planned to use the more explicit version such as:
connectExitStub(fromID, toID, directionNum)
But after testing it does not work.
Steps to reproduce the issue / Reasons for adding feature:
While mapping an area try using connectExitStub(fromID, toID, directionNum)
Error output / Expected result of feature
If you look in the debug console, you will see that it throws an error:
LUA: ERROR running script onRoom (onRoom)
Error: connectExitStub: Need a direction number (or room id) as 2nd argument
Extra information, such as Mudlet version, operating system and ideas for how to solve / implement:
On my system I an running Mudlet 3.17.1-dev on Ubuntu 18.04 with KDE
Brief summary of issue / Description of requested feature:
connectExitStub(fromID, direction or toID[, optional direction])In the above, you can see that connectExitStub() is supposed to accept a room id as the 2nd parameter and optionally a direction as the third.
In my testing the function connectExitStub() only works if the 2nd parameter is a direction number such as:
connectExitStub(fromID, directionNum)For me this means using connectExitStub() will not work to connect the exits between rooms in different Areas.
I had planned to use the more explicit version such as:
connectExitStub(fromID, toID, directionNum)But after testing it does not work.
Steps to reproduce the issue / Reasons for adding feature:
While mapping an area try using connectExitStub(fromID, toID, directionNum)
Error output / Expected result of feature
If you look in the debug console, you will see that it throws an error:
Extra information, such as Mudlet version, operating system and ideas for how to solve / implement:
On my system I an running Mudlet 3.17.1-dev on Ubuntu 18.04 with KDE