Ericthecmh

Have you tried restarting your client. If you're using mirror mode you have to hook it before logging in.

Yes it should!

Awesome! The console log shows that it was trying to interact with the ladder... that's really weird. I'll check it out. The problem you had is because you were running an older version of the script, before I fixed the interactions :P As for loot, try again and if it still doesn't work with a stack size screenshot your loot table for me. It's been working fine for me at minotaurs with Iron arrow Great haha. If you hover over the iron knife in your inventory, what is the action? Is it "Wield Iron knife" or something else? That is probably the problem.

Thanks! I'll come to you again if I need more quests.

Hey no problem I enjoy your suggestions. I'm pretty busy tonight, so I'll have to work on those suggestions tomorow. But the portal problem was also related to the ladder problem, so that should be fixed now BTW I suggest restarting the script, I just pushed another update, still the same version though.

Released version 1.65. Fixes stupid bugs with interacting with ladder and portal! Sorry about this! Also made attacking faster hopefully Please switch to this version if you're having issues, and let me know how it runs

Okay the getting stuck at the location is the same issue as the person's who posted above at the door and ladder I have identified the issue and am about to fix it Thanks for going through the trouble to reproduce it by the way Glad to hear the restart fixed the door problem I'll edit the main thread like you suggested. And you can start anywhere in the stronghold and it will path to the room, or you can start at the Edgeville bank

Nice detailed input! Doors have been working perfectly for me though... Your screenshots don't show any paint at all, which is really weird since that means the script isn't even running? If it were walking it would show the path it's trying to use... Also if you're using mirror please make sure you hook it when you're logged out, otherwise interactions get fucked up. Maybe add my skype so we can teamview if it happens again? (ericthecmh) I'll change the idleness, it was something experimental but I guess it didn't work out... Will try to implement your other suggestions if I can Beautiful, now I know exactly what's wrong, and can fix it

Do you know what went wrong? Was it just standing there but not clicking the ladder? Or was there something blocking it? Did you happen to see what was printed into the console? Also I'll buy some knifes and test it out on my account later to fix the equipping problem Thanks for the updates! Awesome, thanks!

Let me know how it goes! Feel free to add my on skype if you have issues (skype is ericthecmh)

This script will go premium for 7.99 on Friday. So far the following people will be receiving free access: @deceiver @MillSup [member=moocowoinks] (helped a lot via skype) @jake1919 2 more slots available for the taking! If I'm missing anyone who's contributed significantly, please inform me

It depends on the amount of RAM available to the JVM. When you specify the amount of RAM, the launcher starts a JVM with that max allocation. However, on computers that don't have much RAM (or using 32 bit java), there's a limit on the max amount of RAM you're allowed to give to the JVM that you're probably hitting. In other words, you're hitting the max amount you can use for your system. Switching to 64 bit java might allow you to use more.

Awesome, looking forward to it. Eh... small change I guess. Also people might be using B2P. Lol yeah it is off... I'm guessing it has to do with login/logout. Did your character get logged out by any chance? I'll see if I can find a fix for that

Idk, but: [iNFO][bot #1][07/15 08:13:24 AM]: GUI closed. Stopping! [iNFO][bot #1][07/15 08:13:26 AM]: Terminating script CMHStronghold v1.63... [iNFO][bot #1][07/15 08:13:26 AM]: Error in script onExit(): CMHStronghold v1.63 [iNFO][bot #1][07/15 08:13:26 AM]: Script CMHStronghold v1.63 has exited! It says GUI closed. Stopping 2 seconds before the script was exited. I think it's more likely a glitch with OSBot's script executor. Let me know if it happens again; I've been able to pause and resume fine so far, except when the executor glitches.

I'm guessing you were using mirror mode? Either way, the reason it messed up earlier is probably an OSBot problem. It was unable to get the heights for the models of any of the objects. If you were using mirror mode, please make sure you hook the mirror when your are logged out. Based on the last part of the output, it shows you never finished setting up the GUI... The script's not going to do anything until you've done that :P

He's doing all F2P quests for me. Looking forward to it

In eats within 5 of the specified HP. The attack thing is probably something I did with range to make it work better. I'll limit that to range only and hopefully that will make it work better for you EDIT: Should be fixed with version 1.63.

Indeed, confirmed both bugs. I've fixed them in 1.62, which has been pushed and should be live soon Make sure you enter it exactly as runescape shows it, with the same capitalization. If you still can't get it, add me on skype (ericthecmh).

Ah. I had a dumb bug in my failsafe, fixed in 1.60. Release 1.60: Safespot support! Arrow reequip support! Stops script when out of ammo/out of food in bank. Fixed failsafe for bug reported by @MillSup Other logic tweaks

Which ladder are you talking about? What was the script trying to do? Do you have a screenshot? Glad to hear! Get a proggy if you can

And yet another update! Version 1.50 now has a profit table! Up next is range support.

Yet another update! Version 1.41, now supports: * Eat food to make space for loot * Doesn't wait for loot if your inventory is full. Next version will have profit table! As always, suggestions, bug reports, and proggies are welcome.

Done

Released on SDN

Thanks a lot for the screenshot, it was really helpful :P I believe I have fixed that question, but just in case I added a failsafe. The weird path is probably because the script decided that path was going to be a bit faster to walk, shouldn't be too big of a problem though. Pushed version 1.31 with these fixes