Zugg Software :: View topic - Need help getting around the use of the #Waitfor command

Apprentice Joined: 27 Mar 2008 Posts: 106

This is my current use, and works fine, everyone seems to be against the wait and waitfor commands though. Therefore I am looking for a solution.

Wizard Joined: 22 Mar 2007 Posts: 2320

It is not that everyone is against the #wait and #waitfor commands, it is that when you use those commands, you must be aware of the thread issues. For most simple uses, there is no problem. Problems usually arise if you write your code in such a way that a trigger might end up producing multiple threads all waiting for the same thing when you only expected one to run at a time, or when other threads are changing the same variables that your thread is using. These situations can usually be handled as well, if you understand how threads work.

I'm not sure offhand whether your code would have threading problems. If your code is working, go ahead and use it. You might be able to do something similar with a multistate trigger. I take it that sometimes your kill command doesn't actually start the combat you want, so you have to execute it a second time?

Apprentice Joined: 27 Mar 2008 Posts: 106

True, from time to time the command kill so and so will not connect. It may happen only one time, although I have seen it happen 3 times in a row. I tried using a multi-state trigger using Loop Expression, and triggered it off a blank line. This spammed me so bad I just went back to the old way.

One reason why I would like to find a better way is because this way only works one time. If the kill command does not connect 2 times in a row my character will not try a third time.

To comment on the thread issue, I don't even know what a thread is!

Well, thanks again!