I've never used the codebase before, but is it possible that they've attempted a symbol -> text converter, to stop the '$1LL`/' people. i.e. '$' is translated to 'S' in its every instance?
No, I see that it does that run-time, but what about when it reads in the files at boot? Do the socials work before you modify them? (and do they use the $ symbol?)
David Haley aka Ksilyan
Head Programmer,
Legends of the Darkstone
Alright I'll start to see if I can find that and see what is going on. As for the BUG, I don't think all of the RoTs have it but this particular modified version might be an exception, it's a little one, but very frustrating :P
To answer Ksilyan's question a bit:
Examples of how it converts $ to S
say $
You say (OOC) 'S'
sedit cnoarg hmm $n mutters hmmm loudly.
New message is now:
Sn mutters hmmm loudly.
[Global Social] 'Sn mutters hmmm loudly.'
It's the oddest thing I've seen thus far working with it :P
Here is what might be happening, although I haven't looked at the RoT code.
If the display routine always converts $n to "player name" then it might have something in its input routine to change $ to S so that you don't have something like this:
Hello $n there.
... come out with a substitution. Sounds like a hack to me, but I would search for '$' in the code (with the quotes) and see if you can find where it does it.
I believe it is a unix/linux based server. The command isn't reading within the actual MUD. Via say via channels via socials. It's been tested out on multiple mud clients but it's the MUD code itself reading the $ and repeating it as a S. So when you sedit a social instead of $n being read for input it displays Sn hmmms loudly.
I recently started a brand new RoT 1.4 code and seem to have parser problems with the mud reading $ as S. I was wondering if there was a way to root this out or if anyone may have an idea why the mud is reading $ as S. Thanks
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.