Token

Most efficient way to use a mule is letting a script handle it. You obviously won't find any public scripts with mule support but if you plan to make money you will need private scripts anyway (sooner or later you will reach that conclusion even if you don't agree with it right now). As for the IP related questions, use the same protocol as for your other bots.

Acne is impossible to cure :tears: But from my own experience, don't ever go for home remedies, if you just wait it will become worse. I'm on a blue light laser therapy for acne right now and that's definately helping me more than prescription products and at the same time it's not drying my skin at all.

Looks great but when I read the name I thought it was an autoflamer for spamming clan chats

The OSBot Grand Exchange API unfortunately doesn't support actual interactions with the Grand Exchange as in buy, sell and abort. The buy and sell methods are not properly named because they cannot buy or sell items, they only click a Grand Exchange box, as for the abort method, that doesn't even exist. In order to sell an item to the Grand Exchange, you don't have to click the sell button on a box, instead you have to click the item in your inventory. This cannot be done as usually because of the Grand Exchange interface being open. You will have to interact with the widget that contains the item you wish to sell instead of directly interacting with the item because OSBot will attempt to close the Grand Exchange interface if you want to interact with an inventory item. This method should properly offer an item: public boolean offerItem(String string) { for (int n = 0; n < 27; n++) { RS2Widget inventoryWidget = getWidgets().get(467, 0, n); if (getInventory().getItemInSlot(n).getName().contains(string)) { return inventoryWidget.interact("Offer"); } } return false; } Now all you have to do is set the price and quantity (either by using the OSBot Grand Exchange API, which might not work properly, or by interacting with widgets).

You have to initialise your variable before the switch statement with an actual value. long buyPriceNew = 0; switch (...) { case A: buyPriceNew = grandExchange.getAmountSpent(Box.BOX_1); return; case B: ... // the variable is initialised here so you can use it } Use null as a default value for all types except for numerical ones.

Read the AHK docs.

That's just a basic mouse move. The mouse move has a parameter for speed which when set to 0 it's instant. From my own experience, it's not detectable at all even if you leave it running for hours instead of making it just a hotkey for a short action. Read the AHK docs.

AHK is not related to runescape at all so you won't find anything runescape related. Read their documentation and write your own script. All you have to do is put 2 mouse clicks in a loop with a decent sleep. Don't forget to add a hotkey for stopping the script. EDIT: remove the loop part if you want to manually press a button for every alch cast.

Did you really find a mouse pointer in your backyard

Did you try reinstalling Java? Sounds like a JVM related error.

If that works perfectly then reinstalling the windows will obviously do it

Java Development Kit (only if you have that)

Reinstall client, reinstall java, reinstall jdk, reinstall operating system

Don't make the script report itself, that's all the antiban you need... More than that is just xp/gp waste

Yes you can get banned if your bot accidentaly reports himself

1 min progress pic, even better than the 3 min one I saw yesterday

Events are not accessible by Jagex through their game client. I don't think you understand though, all your "theoretical concepts" are nothing but special cases of mouse movements. Anything you mentioned can only be interpreted by jagex as a series of mouse movements, clicks, delays etc. And you cannot say a scripting concept has nothing to do with code when scripts are code, just like their bot detection system. PS: Just stop quoting me if you aren't even going to bother reading what I've told you ever since the first post, I'm not going to be wasting more time explaning the same thing 10000 times.

You don't get what I'm saying. A bot detection system is a software. As any software it is written in a programming language, most likely Java. In any programming language, in order to assess whether the player has left the game screen or not you don't have a application.hasUserLeftGameScreen() method. They have to implement such thing by using CODE. The only possible way to do such thing is by verifying mouse position and movements. Can you think of any other way to tell if a player has left the game screen or not without checking his mouse? Or what exacly do you mean by "have nothing to do with code in a direct way"? Any piece of information is aquired by using code and there is no other possibility.

You were talking about mouse movements. Moving the mouse out of the runescape window is a mouse movement. There is no other way to interpret it at code level. Delaying interactions means delaying mouse movements. Everything you mentioned can only be interpreted as mouse movement behaviour. EDIT: Just so you know, everything you mentioned and much more has been researched intensively on another botting site and their ban rates are no way different from ours. I cannot say which bot it is but all their scripts are required to implement lots of things similar to those but A LOT more. Yet there has been no difference, but they still do it.

While this does sound nice I'm 100% sure it's not going to change anything. I can bot 100+ hours without a break and still not receiving bans. If jagex doesn't even look at your login time when searching for bots then they for sure won't bother looking at your mouse movements...

That should freeze your client because it has no sleeps so the new thread will attempt to use the whole CPU execution cap.

3 min proggy 5/7

Looks good, you might want to consider using a proper thread instead of the paint thread though. As far as I know the paint thread is executed like 60 times a second, so that's literally every ~16 ms which is not really necessary. If you want to go with the optimisations to the maximum then you can detect the changes every tick instead since we have the possibilities to do so with the current API which would be about 40 times more efficient CPU wise.

I would request a porn room, but that won't happen either.

Most offensive scripter.