Hi, When im trying to use anyscript/play by my own in Osbot after few seconds/minutes this window is showing. 

http://scr.hu/27u3/d4xve

I was trying to kill other process, redownload client but nothing works.

I want notice that im using only 1 bot.

Have you tried restarting your computer and trying again?

Have you tried restarting your computer and trying again?

yes

Start task manager, end all your java processes, repeat.

Make sure you don't have any Java applications or Java update manager running, you might need to check within 'msconfig' under start. Check your task manager as well.

If Maldesto's method doesn't work, delete your OSBot folder located at C:\Users\"your user name"

Sorry for late response but i was away. I deleted folder, updated java still doesnt work

 

I was also trying to search for other java processes while the "error" appears, but there is still only 1 process.

Edited October 6, 201510 yr by Efpkaf

Bump I'm having the same problem... Every few minutes of running osbot, get that error saying it shut down from inactivity / need VIP for multiple bots. I've tried all of the above...... HELP!

 

UPDATE: Seems to be working today.

Edited October 13, 201510 yr by cheifkeith69

I'm having this issue aswell... deleted osbot folder / ended all java related processes / restarted and problem still persists.

Another update, still having this problem. Sometimes it'll run successfully, other days not so much. Today I can't run more than a few minutes without getting this:

 

 

Another update, still having this problem. Sometimes it'll run successfully, other days not so much. Today I can't run more than a few minutes without getting this:

Sent to a developer, this seems to be occurring to often.

Try it again guys.

Thanks for looking in to it, starting up the program again, will update later today if problem still occured or not.

 

UPDATE: Been running over 3 hours strong so far, looks like it's fixed

Edited October 17, 201510 yr by cheifkeith69

yh i was getting this to seems to be fixed now, gj devs.

Ran the bot for like 14 hours straight, worked great