Timer/Thread Question?

why not just time stamp the magic use? If the character tries to use it again, check the current time against the time stamp stored.

I'm a very pro-thread programmer, but in this case i think SoulSpectre's advise is the best solution.

I see where you're coming from now on the multi-threaded theory. Still, for only one attribute that happens on a regular interval, it seems like it would be simpler to put a section in your game loop that will check the hit points to see if they're more than 50 points from the maximum and then check the last time heal was called, if necessary. If it gets to the point that you have hundreds of things timing out, then it might be worth it to create a dedicated timer thread, but you're looking at a lot of overhead to replace about 10 lines of code in your game loop if you're only checking if heal can be called again.

If you haven't done any multithreaded programming before, there's a strong possibility that you're using non thread safe functions in your code without even knowing it. Plus, it can be a little tricky to get linux threads running on a windows box. (It can be tricky to get windows threads running on a windows box, too.)

If the effect is automatic, you need a update method for your objects, each frame the update method for all your objects are called. Just have the update method perform the automatic effects.

Hi,

I think you're right! I will put it in game loop. For now I will not have a lot of automatic action like this. It will be faster for me to continue on the project.

I will still continue to check for Threading, and I will test it in a test project when I will have the time.

Thanks!!!!