Continuous Anti-Random Check?

[nielsie95]

Hey,

I was thinking about scripts that *sometimes*, *maybe*, *could probably*, miss a Random Event. I thought that it maybe could be an idea to run a second script behind the running script that keeps checking for new random events.
And if it has found one; it could send an InterScarMessage to the running script that it have to pause until the random is solved.
This way it will probably *always* find a random event fast..

Just an idea, tell me what you think about it.
Nielsie95 :)

EDIT : sorry that this is problably the wrong place in the forum. Could this be moved?

[almost]

I like that idea but my comp would lag :(

[Boreas]

I'm working on it but there a few problems to figure out. It might not be practical, but at this point I'm hopeful.

[seaking]

That's how iBot works :D it works very well actually, no login bugs or whatever and scripting becomes a lot easier.

[nielsie95]

I'm working on it but there a few problems to figure out. It might not be practical, but at this point I'm hopeful.

Great :)

Why wouldn't it be practical? All the existing scripts have be recoded for a part or something?

[Boreas]

Random solvers use the mouse, and the other thread/scar would also be using it to click rocks or whatever. So they would need to communicate often to check whether to stop mining or whatever until the random stuff is done. Or perhaps have one scar do the keyboard and mouse stuff and another do the 'looking'. There a few ways I could go, but there are a lot of pros and cons to weigh up, so don't expect it soon. If it gets to a point where it's so complicated it's not worth it, I'll scrap it.

Edit: hehe smartz I beat you :p

[Smartzkid]

If you did two scars...you'd need to make the main scar to pause for the 'looker', while the looker took care of the random; if you didn't, the main scar could get you pretty messed up