Khaleesi

Just click the foreman once. Working on a fix

wtf ... ?!

Welcome and goodluck!

Yeah, OSBot genius developers have done it again. Use Version .65 for now. That is the downside with mirror client, takes a moment for it to realize that the rockfall has been mined.

You mean V0.12? I didn't change anything to the code ... I only added failsafes incase something went wrong xD What are the issues you are having? Folow bug report template. I can't help you if you only complain and won't tell me anything else ...

Whatever... Khaleesi

Here: http://osbot.org/forum/topic/66803-what-is-osbots-mirror-client/

Check previous post. I pushed something for it Wait for V0.14

Wb! Done, enjoy!

It's not stuck, it osbot failing there methods... Even though the foreman is visible it returns false. I'll update it, but don't come complain if its totally broken xD Script updated to V0.14: - "Fixed" paying foreman on broken osbot methods... Enjoy Khaleesi

sure you got 6 hours

Do you offer package deals/discounts? :P

Better hope I don't run into you

That's too bad, you still got a few hours left though. Unfortunately it's one auth per person regardless of reason or people would come in here and demand trial after trial with new excuses everytime.

I mean, can you tell me when it happends again?

You requested it and I gave to you1 hours later ... By the time you asked the trial again there was still 11 hours left... Which trial did you want?

I use both, but default runs way way better then mirror atm. Mirror is too laggy, which makes it missclicks a ton! Can you tell me when you get the "out of iron" error again? Khaleesi

Mirror client does miss a lot ... known fact due to client lagg. Try to lower to 1000 then ;) I add like 4000 to it xD Makes it lagg free and run way way better then on standard 500... Khaleesi How can you "never" run the script for more then an hour, the update is live for barely 1-2 hours ... xD Like I said: I can't test it since I can run this 100 hours without getting 1 issue at all. The more client lagg you got because of mirror, the more the script will mess up data. When did you get these messages? Khaleesi

Sure pm me when you want it

No the account is still going hard xD

Fixed the issue J mods don't even work on weekends, use mirror client or that's gonna keep happening.

What is this, RuneScapes next top model? I'd go with the tradtional macro-look

Try use the format next time plz You got 24 hours. Enjoy!

Script updated to V0.22: - Updated Seers course - Added a failsafe when getting stuck, script will fix itself within 10-15 sec! If you are still getting stuck somehow, please leave a message. Kind regards Khaleesi

It is using it correctly, this issue happends when the world dc or if using mirror client. dcing worlds are a major issue at this point, since all data/timer will be messed. I do store it as osbuddy, but since mirror client laggs, it skips steps... once in a while. Script updated to V0.13: - Using OSbuddy prices - Added paying foreman failsafe if worlds dc's ... - Added failsafe for waiting forever on bars, with ores in the inventory - Added a failsafe if trying to put more ore onto conveyor even though bars/ores are inside. Note: All this is in beta, I have no way of testing, been running the script for 40 hours and didn't notice any of the bugs reported above. adding more RAM to mirror makes the client less laggy, which means better results. All this issues are caused by lagging mirror client or dcing worlds. If you want to run it 100% flawless use the default client... If you still have issues with previously reported bugs, feel free to post them again if you tried V0.13. Kind regards Khaleesi