Hayase

... @Override public void onPaint(Graphics2D g) { ... /* * If the bot loses connection (got banned?)--take a screenshot */ if (getClient().getLoginStateValue() == 40) {//40 = connection lost log("Client connection lost!"); Utilities.takeScreenshot(); } ... Detecting the last moments of your bot! I've always wondered when and where my bot would get banned. It would be nice to see the last bit of life the bot had before it got banned. This snippet does generate false positives because not all connection losts are bans. The only problem is if you run a lot of bots and are having connection issues--this could potentially generate a lot of disk space.

change is bad, this sucks.

10m

good luck I believe in u

Botnet

They stopped developing for archeage too which kinda sucks. I used to sell gold on that game and now that a new server was added I couldn't take advantage of all the whales buying gold. RIP.

I forgot but I think you just need to have the biohazard quest started

make one? You asked for ideas m8 you got one

Who needs loops wen u can just switch it up int k= getWCExp(); //get ur wc exp cuz u need it switch (k) { case 1: checkWCexp();break; case 2: checkWCexp();break; case 3: checkWCexp();break; case 4: checkWCexp();break; case 5: checkWCexp();break; case 6: checkWCexp();break; case 7: checkWCexp();break; case 8: checkWCexp();break; case 9: checkWCexp();break; case 10: checkWCexp();break; default: checkWCexp();break; } np

while (tree.exists()) { sleep(random(500, 700)); } This is very bad. If you are chopping and under attack the while loop will never exit. Look into a conditional sleep instead, and also add a condition if you suddenly get under attack. new ConditionalSleep(5_000) { @[member='Override'] public boolean condition() throws InterruptedException { return !tree.exists() || myPlayer().isUnderAttack(); } }.sleep();

No one has been banned for using osbuddy which is just like osbot. Both are using injection. However you do get banned for botting

sick cannon bro which 1 is urs?

You can set your onloop() to handle things like this and other issues. You know for sure that the onloop() is going to be looping until script stop. You can define the cooldown then the conditional sleep after like another poster said. Alching is like a 2s delay? do your sleep(2000,2500) and put your conditionalsleep after.

Untested but it seems like it could work /** * * @param position to check if it is within the region * @param player the current position of the player (myPosition()) * @return true if the position is within the region with respect to our players position */ public boolean isReachable(Position position, Position player) { int HOW_BIG_IS_REGION = 20;//idk how big a region is Position insidePos = new Position(position); int distance = insidePos.distance(player); //If the distance from the region is less than our current position, it is reachable return distance < HOW_BIG_IS_REGION; } Just noticed there's already a function for this: map.canReach(position);

awesome thx bro

Change the sleep to return when the player is animating. This way after you interact, it will sleep until you are animating. if(script.inventory.interact("CAST", "Maple Bow") && !script.myPlayer().isAnimating()){ new ConditionalSleep(1200) { public boolean condition() throws InterruptedException return script.myPlayer().isAnimating(); } }.sleep();

Hi I'm gay for ur gooty hole

Let's make america great again!!

WRONG my name is connor

Since you are using a combobox and your options are stored in an array of strings why not just handle them based on the index of the string? We know that at index 0 in your box, answer is "Yes" setShouldBank = cmbBank.getSelectedIndex() == 0;If the selected index is 0, setShouldBank will be true. If you absolutely need the name of the value use this: String selectedIndex = cmbBank.getItemAt(cmbBank.getSelectedIndex());

Strange if it worked before and suddenly stops working. Also not too important in this situation but I think using .contains() could be bad practice if you were dealing with strings that used other words with the sequence "axe" but were not axes. Again there's no case in this situation but if you were dealing with axel logs, .endsWith() would be better in this case since we know our axes always ends with "axe"