FrostBug

Your trial looks like it expired naturally. Tho that said, the devs and admin had a debate yesterday on whether or not to limit the auth system as it was being somewhat abused. Maybe they tinkered around with the auths a bit; I don't know. I hope the 4 hours were enough to determine whether or not you want the script

Everyone knows that ban rate is proportional to how many times per minute you check your woodcutting xp.

I assure you it will not leave it behind on the floor :E

Well, more so than being a bug, it's a limitation caused by the way my framework handles travel routes. I am aware of it though, and there is a note in the route description about it (bottom line)

Noted; Can you give me the exact chatbox message that appears when you try to pick it up?

NPC Index

I have things very similar to this in my Hotkey API What I'd do is: 1. Create a MoveMouseEvent or ClickMouseEvent 2. Set the event to run asynchronously (setAsync) 3. Get the distance to the destination 4. Execute the event 5. ConditionalSleep until event finished or remaining mouse distance is less than 30-50% of original distance 6. Hit the hotkey 7. Wait until event finishes (if not already finished)

700 people, thank you very much

No1 has ever been banned with Frost's Puzzlebox solver Just saying

If you lend me your account with them

What exactly do you want to see improved? Which part of the coding is bad? You seem to be an expert on the topic, so I'll listen to your suggestions

You need a hotkey assigned for the quest tab, like noted in the guide 'starting the script' on the first post ;)

Open the client logger before starting, and lmk what gets logged please

Everything okay now?

A few points to note: - You should probably stick to a single ScriptExecutor (the one provided by the Bot instance). I doubt two script executors can run for the same Bot instance. - You would need to control the ScriptExecutor asynchronously (outside the context of your main script). If the ScriptExecutor is not running, your onLoop will never be called again, and you won't be able to start up the next script. - Take a look at calling the 'prepare' method before 'start'. Be sure to terminate the previous script before attempting to run a new one. Not sure if this is even possible, but it's worth a shot :E

Not sure then; I don't know much about windows 10 since I haven't upgraded yet. Are any other windows 10 users experiencing similar text scaling issues? In any case, I've committed a fix that allows vertical scrollbars if the content for some reason does not fit. It will be live as soon as the SDN manager sees and updates it. For the sake of comparison, this is the default UI:

I just linked you to the microsoft article :E.. Should be the same on win 10 http://windows.microsoft.com/en-US/windows-8/make-text-screen-larger-smaller/?v=t

Pushing an update now to add a scrollbar. For now, try to remove text zoom from your system settings (set to 100%)

What operating system, if I may ask? Sounds like the UI components scale differently

Select the protection prayer for the enemy on the combat tab. If you want it to use potions to keep the prayers active, uncheck the 'do not restore prayer' checkbox

Damn, that sucks. I once forgot to turn off my bot before answering a phone call. As a result it ended up running for more than 65 hours straight. Luckily did not get banned.

Looks like your client has trouble connecting to the SDN. Might your firewall be blocking it?

Joke's on him, I don't have a girlfriend