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
Need help with $
Posted by Taishar on Tue 14 Sep 2004 01:52 AM — 9 posts, 28,863 views.
What OS are you running under and where is it reading $ as S?
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.
But when you read it from area files, it seems to read the $ symbol correctly? Like the builtin socials, do their $ symbols work?
This could be a "feature" of the RoT codebase, but I can't think why they'd do that...
This could be a "feature" of the RoT codebase, but I can't think why they'd do that...
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.
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'd be kind of surprised if it were a MUD codebase bug... I mean, you'd think they'd have noticed it or something. :-)
But it very well could be, so I'd suggest doing what Nick suggested.
But it very well could be, so I'd suggest doing what Nick suggested.
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
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
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?)
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?