I was being hypothetical. The point is: the proper place for time checking is in the core, with events to notify modules. Using this method, the core can poll a single interval per tick and notify modules accordingly.
50% Packetloss - Sun Jan 23, 2005 3:28 am
Post subject:
I found powerbot's timer methods much handier that mervbots. But yah, in mervbot you need to use event_tick, its called once every second (or close to it depending on how often control is returned to the core).
So a posibility is to have a variable in event_tick that increments each time the event is run and keep track of the time that way. Use of the sleep() function will cause your bot to lag out.
Mr Ekted - Sun Jan 23, 2005 4:53 am
Post subject:
You can't really rely on events coming at any particular rate. Timing 10 events that are supposed to occur every second will not guarantee a 10 second interval. If you don't need that kind of precision, then I guess it's fine, but it still means polling of a kind (checking your own counter every tick).
Underlord - Sun Jan 23, 2005 7:43 am
Post subject:
Code: Show/Hide // spawn.h class botInfo { int countdown[1]; public: botInfo(CALL_HANDLE given) { countdown[0] = 10; // initially starts at 10 seconds //spawn.cpp case EVENT_Tick: // called once a second { for (int i = 0; i < 1; ++i) --countdown[i]; if (countdown[0] == 0) // 10 seconds have passed { countdown[0] = 10; // reset timer // insert code that happens every 10 seconds here } |
Mr Ekted - Sun Jan 23, 2005 2:33 pm
Post subject:
Exactly what I was saying NOT to do.
D1st0rt - Sun Jan 23, 2005 2:35 pm
Post subject:
thats how merv does it, if you want people to do it right, you should just give us all a copy of powerbot
Solo Ace - Sun Jan 23, 2005 2:36 pm
Post subject:
Instead of saying what not to do, could you tell him then how to do it right?
Cyan~Fire - Sun Jan 23, 2005 2:58 pm
Post subject:
@Solo:
*
