1) please tell me you have {}'s around the log() and update_roundtime() calls.
Otherwise I would suggest getting an editor that will indent code for you.
2) Ahh... now i understand what you are up to. Events might work. The only
problem you might have is that players like to stack commands against the
inputbuffer and let them be run as soon as they can. How are you going to
handle this?
--Angus
______________________________ Reply Separator _________________________________
Subject: Re: Moderating Command Lag
Author: INTERNET:CIRCLE@POST.QUEENSU.CA at CSERVE
Date: 7/14/98 7:51 PM
um..i was asking for the call to that function in heart_beat()..for all i
know you screwed up the 'if (!(pulse % PULSE_PER_SEC))' check that would
call it every second..shrug..whatever, dude.. >>
Oh sorry. :-P
if (!(pulse % PASSES_PER_SEC))
log("update_roundtime");
update_roundtime();
but it gets past that part fine, apparently. It's just when using the GET_RT
macro.
Not using WAIT_STATE because that makes them wait before typing ANY commands.
But I want them to be able to talk and joke around and stuff in between
command uses...just wanna restrict movement and stuff.
GET_ACTION isn't quite right, unfortunately. I need something that is second
based, not event based.
THanks for the help though. :-)
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST