FrostBug

Well, if you can get an admin to refund that payment, or somehow cancel it, you could try re-doing the payment using a different payment method than eCheck. Most payment methods are instant.

When you configure the magic setup, it will detect which spell you have set to autocast. Like noted in the OP, only autocastable spells are supported

Not sure. Still working on getting a new puzzle box so I can test and fix it

That'd be awesome ;o

x^2*69/75*y^+pid^10

not impressed

Wew so beautiful Who designed dis :xdoge:

It's probably a value between 0 and 2048 for use in SIN/COS tables.. not 100% sure tho

Started

Started Very nice

Any script purchased prior to the release of OSBot 2 will have disappeared. If you did infact purchase it after the release of OSBot 2, then I don't know the cause :| If this is the case, perhaps you can try sending a PM to a supermod or the administrator

OSBot released a new client somewhere around 2014. This is essentially a different script by the same name, written for the new client. No real relation to the old script, as they were discontinued Sorry for your loss

Please stop spamming. If todays update broke something, use the provided bug report template. Other than that, follow the troubleshooting guidelines. For the 1 ppot thing, make sure you specify the number in the GUI in doses as written For the script stopping at the bank, look in the client logger, as the reason for stopping will always be written there.

I don't think there's any particular guide on configs. They're somewhat self explanatory though. The game has a bunch of configs. A config (also called varpbits), is an integer packed with information used by the client. Eg. a bit register where each bit may have a specific meaning. They can be debugged with the client config debugger. You can check if a dialogue with a certain text exists by getWidgets().containingText("Some dialogue text").isEmpty(), if this returned list is not empty, then the dialogue widget exists

http://osbot.org/api/org/osbot/rs07/api/Mouse.html http://docs.oracle.com/javase/7/docs/api/java/awt/Graphics2D.html

NPC#isInteracting doesn't do what you seem to think it does. It will return the NPC guide while the player is 'focusing' him. But that focus is lost as soon as you've interacted with him. Instead you should check if the current dialogue contains whatever it is the guide says. Also, to stop spam clicking, sleep for a bit after interacting. Either with a ConditionalSleep or a simple randomized sleep()

Found the thread, in case you run into any further problems http://osbot.org/forum/topic/80846-using-resources-folder/ Probably has be named "resources" exactly

mm.. I think a dev posted a solution to it somewhere in the dev section (probably a couple of pages back by now) Alternatively you could download them (if mostly images)

If you're looking for specific methods, you can do a quick search in the API index Locate the method you want by its name, and it'll tell you what class(es) it belongs to

Not 100% sure, but since OSBot obfuscates everything, the package structure may be refactored (most obfuscators remove package structure), invalidating this relative path

Do you happen to be missing any tab hotkeys? Sorry to hear that

Started

You weren't supposed to move the deposit statement into the open-bank block, would have been fine if left where it was. Glad you solved the problem, tho.

The problem is pretty obvious if you think about it. 1. If the bank booth is not null, you interact with it. 2. After interacting with it, you immediately try to withdraw from it, in the case that the bank is open. The bank however is in many cases not going to be open after 500 milliseconds after clicking, especially if there's distance between you and the object (which there will often be, since 'closest' method doesn't use manhattan distance). 3. In the case that the bank was not open after the 500 milliseconds, you try to interact with the bank booth again, but since you cannot interact with object while the bank widget is open, the interact method will close the bank before interacting. ^this repeats. You should generally avoid doing multiple interactions in 1 loop cycle, and always evaluate the success of your actions (never assume success). In this particular case tho, I think you can solve it by adding a check to the case for opening the bank if (bankbooth != null && !getBank().isOpen() && !myPlayer().isMoving()) { //interact }