Token

It stands behind the bushes when waiting for the chompy which is the right place afaik. I've never personally encountered another player hunting chompies though. Chompies don't have a 100% spawn rate which is why sometimes they don't spawn. I'll add code to handle other players' presence though

Authed

Yes that can be improved, it was originally designed to be a 100% precise algorithm because first thing it requires is stability, failure in such situations may severely damage the execution context

Thanks, I'll find a workaround to ensure it gets out of dialogues with wrong npcs

Clue scroll(master);

It's top secret

hi

Authed

Authed

If you use the quick start options they have individual presets for every quest. If you create your own quest list you will need different presets

Yes

By spamming you mean standing there for more than 30 seconds looping through the same dialogues? OSBot's Dialogue API is based on color detection and is prone to fail sometimes but in these rare cases calling it again usually yields the desired result. Have you started/completed any other quests related to the Morytania quest series?

Yes 24h Authed

Authed

Yes

Delete JRE, delete JDK Install latest versions and make sure they are suitable for your system

All shortcuts/walking related code is handled by OSBot's webwalker, hence there may be wrongly coded shortcuts, I can't fix the webwalker but I can write a bug report every once in a while for the following client versions. I may get around by disabling shortcuts (in previous client versions it didn't have any effect) however I have to first evaluate the impact on all 40 quests and shortcuts used during these quests

There is no client side detection since 2013. You are free to play through any client with the same ban rates

It is

Delete everything runescape related from your system and undo any changes you made to Java memory allocation

Authed

Well, someone most likely has been playing with your default memory allocation. I don't know what settings have been changed in your system (most likely runescape files were edited by a 3rd party) but in the mean time you can start OSBot through command line and set a different memory allocation by appending the following option to that command -mem 768 and you should no longer receive errors while botting Hint: maybe you modified the C:\Users\USER\jagexcache\jagexlauncher\oldschool\oldschool.prm file? Delete the jagexcache folder

Command line has a current directory but since you know the absolute path you can go with "C:\Users\Zach\Desktop\New folder\osbot 2.4.71.jar"

Has anything changed in your system? Did you update Java? Have you modified your system's environment variables?

"Ghostspeak amulet", 1, "Varrock teleport", 1, "Falador teleport", 7, "Games necklace (8)", 1, "Pot", 4, "Bucket", 4, "Bones", 4, "Iron bar", 5, "Mithril axe", 1, "Holy symbol", 1, "Hard leather", 1, "Polished buttons", 1, "Hammer", 1. However you should be able to run it without debug mode Path to jar ends with the jar file and is wherever you put your jar. Don't forget to put the path between " " if it contains spaces