Apaec

Ty for helping me fix the issue by telling me what happened

Added both of you, enjoy!

Oh woah lol smart u lucky boi

rip Started your trial, will last 24 hours. Let me know if you need longer. Enjoy!

Doesn't seem to for me. If he does get stuck, he should carry on walking.

Woah

Yes, it seems the script update still hasn't been pushed. It should be fixed if you're running version 3.05. If it still isn't working and you're running 3.05, let me know. Started your trial. Enjoy! (Let me know if you need longer)

exactly 31.24%

it is working properly for me (although i'm pending on an update to push to the sdn for a fix for ammo collection) I can offer you a 24 hour trial if you're still deciding whether to buy it! Cheers Apaec

Oh nice, I tried luring once and got an obby cape using the brass key thing but too many people know about it now lel. /it would be so cool 2 b part of a team

To all: Sorry guys, for some reason the thread got unfollowed so i didnt get notified when you guys posted. I'll start a 36 hour trial for each of you to compensate for my delayed response. Sorry about that! Apaec.

I'm sure you got your money's worth I owned an iPhone 1, but they stopped selling them. If I asked for a refund because it was no longer in production, I'm sure i'd get some confused faces xD. But in terms of the script, It must have been for the old client (OSBot 1). OSBot 2 was released earlier this year which featured major improvements to the bot - this did however make all the old scripts mostly disfunctional. Alot of the scripters were inactive / moved on after it's release as they weren't prepared to update their scripts (basically re-write them) for the new client. Apaec

I pushed a fix for this ages ago and i'm not sure why but it's still not on the sdn... Wierd. EDIT: turns out the SDN manager was on holiday but returned today. @Alek mentioned he will try and commit the changes within the next few days (but hopefully sooner, if he can). When version 3.05 is out, then your problems will be fixed.

He's looking for a mouse-keys style of interaction. interact(item) is too slow for him! OP: You can use the following code to generate the area around an item in your inventory (I put this in onpaint just for the visual representation). All you would do then is move the mouse using rectangle destination and click. Item[] items = this.inventory.getItems(); for (Item item : items) { Rectangle rectangleAroundItem = this.inventory.getMouseDestination(this.inventory.getSlot(item)).getBoundingBox(); g.drawRect((int) rectangleAroundItem.getX() - 1, (int) rectangleAroundItem.getY() - 1, (int) rectangleAroundItem.getWidth() + 1, (int) rectangleAroundItem.getHeight() + 1); } The rectangle will be recreated every iteration, however if the id/name of the item changes and you adjust the filter for the items array, you should be able to write it like that.

Was the pun intended?

That's odd as I pushed an update fixing that a while back, perhaps it hasn't been committed? I'll look into that Edit; Yes, I pushed a fix not too long ago however it looks like the version hasn't been pushed to the SDN. I'll push a quick version this evening being version 3.05. Once you're getting 3.05, your problems should be solved, however we're currently waiting on the development team to push my update live! Hopefully this problem will be short-lived Apaec

Is the issue still persisting? because I didn't get round to testing it on my account however I filed through the code and it seemed in order. Will deffo run the script on my account tonight and see what happens.

Lol, not sure what happened there xD

Will take a look into this when I get home, thanks for reporting.

I can enable a 24h trial on your account so you can give it a shot! Trial started now, let me know if you need longer. Enjoy!

u can have house parties in world 330

close tab

Take care :c

Congrats! :3

Unfortunately the error drawing canvas was a confirmed bug in the client which us (all the scripters) are still waiting on to be fixed! At the moment there's nothing I can do however I believe this issue has been reported to the devs so it will be fixed soon hopefully.