Advanced MUD Concepts

scandum · 03-20-2009, 10:34 PM

Might be the RESTRING macro call on d->terminal_type while it's NULL. Not sure what you're doing, but if you use it "as is" you'd want to use: d->terminal_type = strdup("");

Should be more obvious if you execute:

telnet
set options
open nimud.divineright.org 5333

locke · 03-21-2009, 12:24 AM

While using gdb it hung in select() instead of crashing.

locke · 03-21-2009, 12:28 AM

Quote:

Originally Posted by scandum

Might be the RESTRING macro call on d->terminal_type while it's NULL. Not sure what you're doing, but if you use it "as is" you'd want to use: d->terminal_type = strdup("");

Should be more obvious if you execute:

telnet
set options
open nimud.divineright.org 5333

This was already done as d->terminal_type = &str_empty[0];

scandum · 03-21-2009, 04:13 PM

Quote:

Originally Posted by locke

This was already done as d->terminal_type = &str_empty[0];

You should use d->terminal_type = strdup(""); if you're gonna use the macro provided with mth.

locke · 03-21-2009, 06:48 PM

Quote:

Originally Posted by scandum

You should use d->terminal_type = strdup(""); if you're gonna use the macro provided with mth.

This fixed the problem, and I am now using translate_telopts with no wierdness. Undefined Behavior beware.

So, please try connecting us to your network. Once connected I will release NiMUD with an announcement at the top of the README about contacting you should someone want to start a NiMUD and join your network.

The specific copy of NiMUD I run is at nimud.divineright.org 5333, but others may join your network someday.

Tintin was the first client I ever used, but I later switched to TinyFugue. Now I just use PuTTy. It would be interesting to see a "lite" version written for use with the standard telnet port instead of stdin, that was easily added to existing MUDs -- one with the ability only to connect with multiple sessions to a default mud address -- as a proxy service. That way MUD admins could set up Tintin on their primary port, with some default settings to auto connect to the MUD, plus the ability to allow players to manage multiple sessions with Tintin on MUDs (like mine) that allow multiplaying.

You know .. it could activate when another client isn't detected, otherwise merely forwarding to the port like tcpxd.

Regards,
Locke

scandum · 03-21-2009, 08:28 PM

It's not working as of yet, I get:

RCVD IAC 0 0
NiM5 Build 12773

<the greeting screen>

What is thy name?
RCVD IAC IAC
RCVD IAC SE 253
ÿú
RCVD IAC IAC
RCVD IAC SE 32
ÿúFNAMEThe Isles: Lands of KltaraPLAYERS62UPTIME24CODEBASENiMUDCONTACT<etc>

Looks like it tries to send out the actual MSSP data, but it gets mangled somewhere.

The debug output in tintin is supposed to look something like the following:

Code:

RCVD IAC SB MSSP (725)
############################################################
PLAYERS              5
UPTIME               1237444142
CODEBASE             CircleMUD 3.1
CONTACT              
CREATED              2000
HOSTNAME             azereth.game-host.org
ICON                 http://azereth.game-host.org:6400/icon.gif
IP                   68.103.0.241
LANGUAGE             English
LOCATION             United States
MINIMUM AGE          0
NAME                 AzerethMUD
PORT                 6464
FAMILY               DikuMud
WEBSITE              http://azereth.game-host.org:6400
GENRE                Fantasy
GAMEPLAY             Hack and Slash
GAMESYSTEM           Custom
INTERMUD             I3
INTERMUD             IMC2
STATUS               LIVE
SUBGENRE             Medieval Mythical
AREAS                213
HELPFILES            797
MOBILES              2705
OBJECTS              3552
ROOMS                11552
RESETS               0
MUDPROGS             0
MUDTRIGS             1122
CLASSES              7
LEVELS               0
RACES                10
SKILLS               150
WORLDS               1
ANSI                 1
MCCP                 1
MCP                  0
MSP                  0
MXP                  0
PUEBLO               0
VT100                0
XTERM 256 COLORS     0
PAY TO PLAY          0
PAY FOR PERKS        0
HIRING BUILDERS      1
HIRING CODERS        0
############################################################

locke · 03-21-2009, 09:44 PM

Quote:

Originally Posted by scandum

It's not working as of yet, I get:

RCVD IAC 0 0
NiM5 Build 12773

<the greeting screen>

What is thy name?
RCVD IAC IAC
RCVD IAC SE 253
ÿú
RCVD IAC IAC
RCVD IAC SE 32
ÿúFNAMEThe Isles: Lands of KltaraPLAYERS62UPTIME24CODEBASENiMUDCONTACT<etc>

Looks like it tries to send out the actual MSSP data, but it gets mangled somewhere.

The debug output in tintin is supposed to look something like the following:

There's that wierd character combination, ÿú !!! I have no idea but I will switch to your write_to_descriptor and see if that helps.

Are you related to 121.149.104.1 ? This bot seems to be repeatedly connecting, maybe it's your crawler?

locke · 03-23-2009, 02:59 PM

Quote:

Originally Posted by locke

There's that wierd character combination, ÿú !!! I have no idea but I will switch to your write_to_descriptor and see if that helps.

Are you related to 121.149.104.1 ? This bot seems to be repeatedly connecting, maybe it's your crawler?

I have done this. Please retry.

scandum · 03-23-2009, 03:48 PM

That's a korean IP, not sure who it is.

MSSP is still not working, nor is the mud announcing MSSP support.

I suggest you use tintin++ for debugging it with the following line to connect:

#config debug on;#ses x nimud.divineright.org 5333

If MSSP works you'll automatically get a formatted display of MSSP variables and values as I pasted earlier on.

locke · 03-24-2009, 06:14 PM

Scandum,

Code:

Notify> LOG: Sock.sinaddr:  204.209.44.14
Notify>  New connection: 204.209.44.14
Notify> LOG: D7@mudconnector.com RCVD IAC WILL SUPPRESS GA
Notify> LOG: D7@mudconnector.com RCVD IAC DO TERMINAL TYPE
Notify> LOG: D7@mudconnector.com RCVD IAC DO NAWS
Notify> LOG: D7@mudconnector.com RCVD IAC DO NEW_ENVIRON
Notify> LOG: D7@mudconnector.com RCVD IAC WILL MSSP
Notify> LOG: D7@mudconnector.com RCVD IAC WILL MCCP2

Yet it still does not work. Why?

scandum · 04-02-2009, 01:32 PM

Quote:

Originally Posted by locke

Yet it still does not work. Why?

No idea.

Back on topic:

3 more muds added MSSP bringing the total to 9.

I updated my crawler to report average players and average uptime.

MSSP Mud Crawler

And for those who missed the earlier mention, an easier to implement plaintext version of the protocol is described on the specification page.

MSSP (Mud Server Status Protocol)

locke · 04-25-2009, 07:00 AM

Still unable to figure out why it does not work with your network; it seems to be sending statistics to mudconnect's bot, though.

03-20-2009, 10:34 PM	#31
scandum Senior Member Join Date: Jun 2004 Posts: 251	Re: MSSP (Mud Server Status Protocol) Might be the RESTRING macro call on d->terminal_type while it's NULL. Not sure what you're doing, but if you use it "as is" you'd want to use: d->terminal_type = strdup(""); Should be more obvious if you execute: telnet set options open nimud.divineright.org 5333

03-21-2009, 12:24 AM	#32
locke Banned Join Date: Jan 2009 Home MUD: nimud.divineright.org 5333 Posts: 195	Re: MSSP (Mud Server Status Protocol) While using gdb it hung in select() instead of crashing.

03-23-2009, 03:48 PM	#39
scandum Senior Member Join Date: Jun 2004 Posts: 251	Re: MSSP (Mud Server Status Protocol) That's a korean IP, not sure who it is. MSSP is still not working, nor is the mud announcing MSSP support. I suggest you use tintin++ for debugging it with the following line to connect: #config debug on;#ses x nimud.divineright.org 5333 If MSSP works you'll automatically get a formatted display of MSSP variables and values as I pasted earlier on.

04-25-2009, 07:00 AM	#42
locke Banned Join Date: Jan 2009 Home MUD: nimud.divineright.org 5333 Posts: 195	Re: MSSP (Mud Server Status Protocol) Still unable to figure out why it does not work with your network; it seems to be sending statistics to mudconnect's bot, though.