Server Help

[Maverick]

Ok, how to get a Mervbot plugin to call a function every 101 ms ?
I guess you would have to create a timer (and a thread?) to do that, can someone give me an example of that?
_________________

Nickname: Maverick (I changed my name!)
TWCore developer | Subspace statistics

[Bak]

I'd just change the EVENT_Tick in the core to occur every 0.1 second (like powerbot's tick does).
_________________
SubSpace Discretion: A Third Generation SubSpace Client

[Maverick]

Guess that is another solution to the problem, but it would be making mervbot custom then. Hmmm, custom mervbot for my plugin

[xor eax]

I think you should use SetTimer function

Code: Show/Hide //To start the timer:     UINT hTimer;     hTimer = SetTimer(NULL,0,101,TimerProc); // (101 is the timer interval (milliseconds)) // (TimerProc is the callback that will be called when interval expires) --------------------------------------------------------- //To stop the timer:     KillTimer(NULL,hTimer); --------------------------------------------------------- //The callback function VOID CALLBACK TimerProc(HWND hwnd, UINT uMsg, UINT idEvent, DWORD dwTime) {    //Put your code here    // ...    return; }

[Maverick]

Thanks I will try that.

[CypherJF]

Submit any core changes to catid to merge into the main build. I saw SOS posted his version of Merv, but doesn't it need .NET?
_________________
Performance is often the art of cheating carefully. - James Gosling

[Maverick]

xor eax, what should be the name of the CALLBACK TimerProc() function be if I want it to be part of the botInfo:: class ? Or isn't that possible?

[Smong]

I remember going through this. You can have a static function with an extra parameter 'this' to call the member function you want.

Code: Show/Hide class DirClient { protected:    void OnDisconnected(void *clos);    static void OnDisconnected_(void *self, void *clos); }; ...    net->SetDisconnectFunc(OnDisconnected_, (void*)this, NULL); ... void DirClient::OnDisconnected(void *clos) { ... } void DirClient::OnDisconnected_(void *self_, void *clos) {    DirClient *self = (DirClient*)self_;    self->OnDisconnected(clos); }

[Cyan~Fire]

I'm curious. Without a message loop, how exactly does the timer notification get to your code? A separate thread? In that case, wouldn't you have to mess around with mutex's?
_________________
This help is informational only. No representation is made or warranty given as to its content. User assumes all risk of use. Cyan~Fire assumes no responsibility for any loss or delay resulting from such use.
Wise men STILL seek Him.

[xor eax]

[Maverick]

Smong, how do I make that extra parameter 'this' use with the code xor eax posted?

Cyan~Fire thats more or less the problem I am having (was said on another forum about settimer and non-static functions)

[Mr Ekted]

Using Win API SetTimer() to handle bot timers is not good.
_________________
4,691 irradiated haggis!

[D1st0rt]

Does pbot have separate timers or just really fast ticking?
_________________

[Cyan~Fire]

He said once before the pbot defines a timer interface for its plugins. This is something I will add to MERVBot, if I ever finish.

[xsp0rtsfanx]

i'm glad my topic started helping out with something for mervbot although i got lost when people starting posting code lol

[Mr Ekted]

Pbot has a 100ms tick event and a programmable timer event (with 100ms granularity). Even if there are 20 bots, each with 20 modules, each with 20 timers going (8000!), there's no overhead. I keep timers in a linked list sorted by trigger time, and only have to check the top one. Try calling Win API SetTimer() 8000 times.

[Cerium]

Single threaded?
_________________
There are 7 user(s) ignoring me right now.

[CypherJF]

Doubtful.

[Mr Ekted]

Each bot is a single thread. Each thread manages its own timer list in the core.

[Maverick]

Whats the solution for mervbot then?
Mervbot has a tick event, which goes once every second. for the rest nothing that can be really used to spec areas on a map reliable.

I need something like a timer to make function being called every 101 ms. But with a timer I have problems with non-static functions etc.

Is there a solution to making timers work in Mervbot or do I have to make a custom mervbot to have the tick event go every 101 ms?



(Can a mod split this topic into noisySpectator entitled topic please?)

[xor eax]

So using 1 timer is not good because 8000 timers are an overhead?

Who is talking about calling SetTimer 8000 times? Not Maverick, not Smong, not me.

All I'm saying is that what Maverick wants can be done using SetTimer. And I haven't heard any good argument of yours against that.

Do you think a single timer per bot supose a significant overhead?

How is pbot handling the timer event? Is it using a timer or a... wheelchair?

How you're fabulous theory applies to Maverick's needs?

(and yes, Cerium, it can be single threaded, it simply does not depend on the thread model)

[Mr Ekted]

Obviously my example was hyperbole. My point is that when coding, you consider scaleability. Don't do a "one time hack" that will end up being the foundation of something much more widely used.

Also, why exactly 101ms? Do you realize that, depending on the operating system, the resolution of the system timers could be as high as 16ms? Under Windows, if you are running in a worker thread (ie not a message loop), you can potentially use the multimedia timer or the high-res timer to get 1ms or even 1us accuracy. However, polling those timers has its own overhead.

[Maverick]

I don't care it has to be 101 ms, at least faster then the current EVENT_Tick of Mervbot.



I guess I am going to continue building my bot based on noisyspectator :/

[Guest]

Mav, you want the bot to spec players one by one, if I understood well.

And I guess 101 msecs is the minimum time you must wait to assure that 1 position packet at least will be received from each player.

You want a non-static function to be triggered every X milliseconds... Why don't you call the non-static function from the TimerProc function?

Anyway, I think it can be done without a timer:
Why don't you make it so when a position packet arrives from the expected player then the bot switches to next player?

-You put the bot to spec the next player in list.
-When its correspondent position packet arrives the bot switches to next player.
-If a player goes to spec or leave the arena it is removed from the list of players being speced by the bot. And if the bot was specing him it switches to next player. When a player enter it is added to the list... etc.

Well... sorry Mav, I'm trying to help but maybe is better not to try it if I can't do it properly...

[xor eax]

the guest is me