1. OSBot Version (do NOT put "current version", be specific)

2.4.43

 

2. A description of the issue. Include relevant logs.

The pause and stop buttons are still up even after the script uses "stop();" Still logs you out though.

3. Are you receiving any errors in the client canvas or the logger?

Nope

 

4. How can you replicate the issue?

Just start a script and stop it? I'm unsure. I ran out of items and it called for the stop method.

 

5. Has this issue persisted through multiple versions? If so, how far back?

no clue, just noticed it

 

Why are you blocking out the script name? Chances are the script is caught in a loop which can't be exited. 

Why are you blocking out the script name? Chances are the script is caught in a loop which can't be exited. 

I don't actually remember why I bothered blocking it out, lol

 

It's this.

http://pastie.org/10746391

 

Chances are, you're probably right about it being stuck in a loop.

Some places it might be getting stuck:

 

case 10:
mouse.moveOutsideScreen();
sleep(random(5000, 10000));
break;


if (w2 != null) {
w2.interact("Make All");
state = "butter on potato";
sleep (17000);
}


if (w3 != null) {
w3.interact("Make All");
state = "Cutting tuna";
sleep (17000);
}


if (w4 != null) {
w4.interact("Make All");
state = "Sweetcorn on tuna";
sleep (18000);
}


if (w5 != null) {
w5.interact("Make All");
state = "Tuna Potatoes";
sleep (20000);
}


while(guiWait)
try {
sleep(500);
} catch (InterruptedException e) {
e.printStackTrace();
}

 

 

Some places it might be getting stuck:

 

case 10:
mouse.moveOutsideScreen();
sleep(random(5000, 10000));
break;


if (w2 != null) {
w2.interact("Make All");
state = "butter on potato";
sleep (17000);
}


if (w3 != null) {
w3.interact("Make All");
state = "Cutting tuna";
sleep (17000);
}


if (w4 != null) {
w4.interact("Make All");
state = "Sweetcorn on tuna";
sleep (18000);
}


if (w5 != null) {
w5.interact("Make All");
state = "Tuna Potatoes";
sleep (20000);
}


while(guiWait)
try {
sleep(500);
} catch (InterruptedException e) {
e.printStackTrace();
}

 

Should I use conditional sleeps for waiting until it's out of required items to fix the stuck loop part?

 

The guiWait is what I use in all GUI requiring scripts and it's never caused this before.

 

Even after sleep times pass, like I can wait minutes, the pause/stop buttons are still there. Shouldn't they technically go back to normal? Is that how it would get unstuck?