I have a pretty good idea of what the problem is. I just need to come up with a work around. This likely won't happen to everybody either. It could have to do with proxies but I'm honestly not 100% sure.
The way it is set up I have set a boolean after the interaction with a master so if for whatever reason your interaction fails but it is registered as true then it will actually cause the bot to get stuck. I will work on a fix for this and remove those booleans.
This would explain why you said it got stuck on config 2. I thought that was very strange but the only thing done there is interacting with the runescape guide.