| View previous topic :: View next topic |
| Author |
Message |
Elvang
Joined: 27 Mar 2012
Posts: 16
|
 Posted: Fri Mar 30, 2012 2:46 am Post subject: Two ?'s: #SHORTEST PATH: UNKNOWN ERROR. and #send issues |
 |
|
Version: wintin++ 2.00.8
MUD: Materia Magica (materiamagica.com port 23)
The first issue I'm having is that the mud thinks I'm sending ' ] }' immediately after the gmcp handshake in the following section of script. It appears to be attached to the beginning of the first thing I physically type (the string doesn't get attached to the username or password sent by the connect script).
| Code: | #format IAC %a 255
#format DONT %a 254
#format DO %a 253
#format WONT %a 252
#format WILL %a 251
#format SB %a 250
#format SE %a 240
#format GMCP %a 201
#var CLIENT_NAME TinTin++
#var CLIENT_VERSION 2.00.8
#event {PROGRAM START}
{
#var CLIENT_NAME %0;
#var CLIENT_VERSION %1
}
#event {IAC WILL GMCP}
{
#send {$IAC$DO$GMCP\};
#send {$IAC$SB$GMCP core.hello { "client": "$CLIENT_NAME", "version": "$CLIENT_VERSION" } $IAC$SE\};
#send {$IAC$SB$GMCP core.supports.set [ "room 1", "char 1" ] $IAC$SE\};
} |
The second issue is that in certain rooms, '#map find'ing to rooms that have been customized (color+symbol+desc) returns '#SHORTEST PATH: UNKNOWN ERROR.'. The rooms generate paths that end up looping back on themselves, and don't end on the correct room. The final room of the path is always the same (vnum 11440), so long as I search from a room that causes the error. It is possible to successfully search the room from other rooms, and to search other rooms from the problematic rooms.
This is a zip containing the map, and the automapper script in its entirety. As an example, '#map find {The Hungry Goat Inn}' from room "A Dusty Path", vnum 11438, will cause the mentioned error. The path it returns is 'n w w w e e'.
In general, searching for any of the rooms in the western area that have been customized will return that. |
|
| Back to top |
|
 |
Scandum
Site Admin
Joined: 03 Dec 2004
Posts: 3281
|
| Posted: Fri Mar 30, 2012 4:25 pm Post subject: |
|
|
The script looks alright to me so the problem is most likely on the server end as there have been no reports of problems from IRE players.
Want to check if the issue with the mapper has been fixed in the beta? An updated tt++.exe file is here:
http://tintin.sourceforge.net/download/tt++.exe
Just copy it over the tt++ file in your WinTin++ installation folder. |
|
| Back to top |
|
|
Elvang
Joined: 27 Mar 2012
Posts: 16
|
| Posted: Fri Mar 30, 2012 5:09 pm Post subject: |
|
|
I thought that might be the case, but I wasn't sure since gmcp and the specified modules were still being turned on by the '#send's.
The mapper issue appears to have been fixed in the beta.
Thanks for the assistance. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
