Somthing else, the Lopes color code for a beep is {*, might make sure
that isnt anywhere in what you are send_to_char'ing. Also, stabbing in
the dark, this wouldnt be a client thing?
--
Kevin
Michael Weiss wrote:
No.. the only other thing that has changed is the wiznet TICK! message is
now in dark red. I checked for the color string that changed it and came
up with nothing. Nothing else is odd at all.
I'll check the send_to and other code to see if anything looks odd.
Thanks,
-Mike
----- Original Message -----
From: "Jason Gauthier" <[EMAIL PROTECTED]>
To: "'Michael Weiss'" <[EMAIL PROTECTED]>; "ROM List" <[email protected]>
Sent: Tuesday, June 25, 2002 8:41 PM
Subject: RE: Ok.. I need some help
If it happens with wiznet, it's not the interpret code.
Check send_to_char, and stuff.
However, is there anything else strange? weird characters, etc?
If you have string corruption sometimes unprintables beep.
-----Original Message-----
From: Michael Weiss [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 25, 2002 8:37 PM
To: ROM List
Subject: Ok.. I need some help
I have a very odd error that just started. I get a 'beep'
(audible chime)
with every command typed on the mud... I even get it on wiznet messages
(ticks..etc..). Socials, commands, etc...
I figured that it must be in the interpret code, but I can't
find anything
and I haven't made any changes in the file that could have caused this.
Where else should I look? I'm stumped. I'm running 2.4b6,
OLC 2.01 and
Lopes 2.0.
Thank you in advance for any help you give me.
-Mike
--
ROM mailing list
[email protected]
http://www.rom.org/cgi-bin/mailman/listinfo/rom
--
ROM mailing list
[email protected]
http://www.rom.org/cgi-bin/mailman/listinfo/rom
