Alek

BuyItem does everything for you and uses the first available box to do it. BuyItems was the original method which only clicks "Buy" on the desired GrandExchange box. This means you can either have OSBot do everything for you, or you write your own GrandExchange methods.

Event execute() is an internal method used by the event executor. You can use either bot.getEventExecutor().execute(event) or the wrapper method which is simply "execute(Event)" therefore execute(e); will work

Try checking out my Macro Killer source code, I made it public.

You seemed to find out the random method pretty quickly.

That doesn't make any sense. You contradicted yourself in the same sentence. "I didn't follow the guide and never got banned, I only got banned when I followed your guide". "I'm trying to figure out how I got banned". You answered your own question, you got banned for following the guide. Go back to whatever you were doing before then?

Get back in the Chatbox.

You spent a lot of time on ridiculous antiban and not a lot of time on solid logic. Remove all of the bullshit antiban and I'll look it over when I get a chance, if you're still having the issue.

Use InventorySlotDestination or any of the inventory methods that take slot as an argument (as mentioned above). Good luck with the 0% ban rate, Ill be expecting a competitor client soon.

Please take a look at this thread:

operating system?

So you only get the issue on a second tab on your machine?

Thanks for letting me know!

https://i.gyazo.com/c3fd35e3d9cbb06baf0a8c32143afb44.mp4 Hmm

I spammed the logger a bunch: https://i.gyazo.com/c2fb8675eb20fafc2554e3058eb909c3.mp4

Not really a secret since I don't allow overriding human input: bot.getCanvas().addMouseListener(mouseListener); Your custom mouse listeners will get removed during some certain events (such as Windows UAC being prompted). It's part of some larger input issues that I can't really track down right now.

Here is Macro Cutter: https://i.gyazo.com/7083ee031132d07dc25de656cbec1891.mp4

Alright Ill ask around, I think Zach might have that on one of his spares.

I just tested opening and closing the logger and turning disable input on and off. Both were tested using the menu and the hotkeys. Seems to be working for me. Also two of my scripts don't have interfaces and rely on mouse/key listeners as well, they are working just fine. What OS are you on?

Advertisements now show up for the freeloaders valued non-VIP members once again. Additionally I took another crack at the input issue and it seems to be working for me. Unfortunately this is a forced stable build with not a whole lot of testing, but it should be at least better than .127. If you have any continued issues please let me know. Changelog: -Patched advertisements (fixed by Zach) -Changed hotkeys to PostProcessing --Hotkeys are now numkey "7" and "9" when numlock is OFF -Attempted patch at input bugs -Updated web data

When you pass an array/list of positions into webwalkevent, it automatically generates the fastest route. If you use prefetchrequirements, you can grab the closest bank without actually walking there.

Not to vent on you, but I have to explain this topic so many times its getting annoying. The closest bank in regards to the map coords is different than actual traversing. Consider wanting to grab the closest bank to you. The closest bank in coords is on the other side of a river which; you can't cross the river but its the closest. This is a common error in such approaches, because although its physically closer, actually walking there is much longer.

How does it prove that other clients are right? Like I mentioned in the original post, it's not a couple of brothers hanging out making their first Unity game on personal edition. This game has been botted and reversed for a very long time; I'd throw myself off of a bridge if the company was completely clueless about these "methods". As far as "helping delay it - even just by very little", is very wishful thinking. As with @IDontEvenBot, all I personally do is move mouse off screen. I'm not saying that's the cure-all that will save your 100 bot mega farm, nor am I saying if that has any impact at all. Use this information as you want, most botters want quick stats and quick money which is a great trap for catching bots.

Both your solution and LoudPacks solution won't work with web walking.

Quests are largely thought to be a component of their profiling, not the entirety. Doing a couple of quests won't prevent a ban. We can draw conclusions from F2P trade restrictions with 7QP and time requirements that are designed to hinder bot farmers.