Ericthecmh

Thanks for the positive feedback :) Trial given

1) Intentional, it saves your energy for when you're actually in the stronghold (reduce time with aggro). Could change to activate run when it reaches 100 2) Might add varrock later, but not glory. I don't want to have to equip stuff. 3) Will add later

It runs when walking. I'll enable run when fighting too. Done.

Done.

Hey, forgot to say that I fixed this issue and extended your trial for you to check again Just one of them.

Lol... You can't just run a command and make a program magically use less memory.

First of all, if you're doing string comparison you should be using .equals() Second, setEnabled controls whether the checkbox is active. You're looking for setSelected() And I would recommend doing something like boolean selected = Boolean.parseSelected(line05); checkbox.setSelected(selected); Cleaner code

Add me on skype (ericthecmh).

Done.

What? This script is now DreamStronghold. Some images might still say CMHStronghold until I get them changed.

Done.

Also should note that users who previously purchased a script will keep their access to the script.

Loving these proggies, you'll both get access. Just don't get banned please :P

New update 2.3 Should fix the issue with the script trying to attack a dying monster.

Because the newest OSBot released removed the Area class which many scripts were depending on. The scripters will have to update their scripts for it.

Wow, thanks man! Yes you do. Your prize is free access to the other scripts that will be part of the DreamScripts package (provided that my partner will be okay with it) :P LOL haha I've actually not had a single ban report so far. The antiban is pretty good if I do say so myself.

Done. Was an API change, but I fixed the script for it. Your trial has been automatically extended

Done for both.

Ask for a trial first! http://osbot.org/forum/topic/78101-cmhscripts-are-back-request-a-trial-here/

Ayyy nice catch

Shameless advertising (facepalm)

Read my correction above EDIT: Fixed in new version 2.2 Thanks to @ThatOtherGuy and @Three Shot for the report and help.

99% sure this is an OSBot issue. Your getting hit by the logout timeout and when it logs back it the script doesnt' resume properly. Correction: With the help of @Three Shot, I was able to identify the problem. Will fix now

Unfortunately it's nearly impossible to debug based solely on that info. Can you proved the following info: 1) When you see that it's stuck, what is it doing? Is it trying to click the door over and over? 2) If you open the console log, what does it say? 3) What state is the paint in? Thanks

Dual boot with 2 windows installs is a pain in the ass. Not to mention some people don't want to repartition their drives and mess around with the bootloader... And if you have a computer sitting around... why not?