- Added Force Menu Interaction
Great work!
Thank you for the in-detailed feedback! I'm very happy to hear that Lumbridge is working correctly (I was a shot in the dark and wasn't tested haha).Since this version update, Lumbridge trout/salmon fishing & banking is now working flawlessly in DarkScape!
When I get some more free time, I hope to check out some of the other fishing areas currently supported, though I assume they are all likely to be working just fine.
As a side note... the only real issue that continues to persist is miss clicking. I've noticed this issue exists in almost every bot I've had the pleasure of using, and am assuming it is more of an issue with the RuneMate client itself, rather than with individual bots. Anyways, to keep on topic, I have noticed that this bot does have some issues with closing accidentally opened windows. More specifically, if you have a pet out (Like the baby troll for example) and the bot miss clicks to talk with it, then it appears to get stuck in this window. Most other windows that are potentially opened by accident are handled correctly, and the bot closes them just fine (Examining another player, for example). I'm not really sure if this is a client or bot specific issue, but thought I would report it here just in case.
While the most obvious solution to this problem is to simply not carry around a pet while fishing, I think that the main reason the bot is unable to close this window is because it is a window that does not have an [X] to close and requires one to press [Esc] to close. However, this is merely my theory and I am unsure of how correct that it actually is.
Well that is all I have to add. Thanks again for this great bot, and keep up the good work.
Since this version update, Lumbridge trout/salmon fishing & banking is now working flawlessly in DarkScape!
When I get some more free time, I hope to check out some of the other fishing areas currently supported, though I assume they are all likely to be working just fine.
As a side note... the only real issue that continues to persist is miss clicking. I've noticed this issue exists in almost every bot I've had the pleasure of using, and am assuming it is more of an issue with the RuneMate client itself, rather than with individual bots. Anyways, to keep on topic, I have noticed that this bot does have some issues with closing accidentally opened windows. More specifically, if you have a pet out (Like the baby troll for example) and the bot miss clicks to talk with it, then it appears to get stuck in this window. Most other windows that are potentially opened by accident are handled correctly, and the bot closes them just fine (Examining another player, for example). I'm not really sure if this is a client or bot specific issue, but thought I would report it here just in case.
While the most obvious solution to this problem is to simply not carry around a pet while fishing, I think that the main reason the bot is unable to close this window is because it is a window that does not have an [X] to close and requires one to press [Esc] to close. However, this is merely my theory and I am unsure of how correct that it actually is.
Well that is all I have to add. Thanks again for this great bot, and keep up the good work.
Misclicks should not be a thing if interaction is implemented correctly. The most specific interaction method should be used whenever possible i.e. interactable.interact("Action", interactable.getName()). If misclicks occur with this interaction type, then it is a client issue. If not, then it is a bot issue. As far as unwanted interfaces it is best to be handled at the client level, but in order to do so we need the full information and an account to reproduce it with. One would be best off posting a Client Support thread dedicated to it with a screenshot of the interface, reproduction steps, and an offer to a client developer to borrow your account to test the fix.Thank you for the in-detailed feedback! I'm very happy to hear that Lumbridge is working correctly (I was a shot in the dark and wasn't tested haha).
As for the mis-clicking issue... there really isn't much I can do about it :/
You are correct that it is client-sided and not bot related, and you are also correct that RM has an event handler to close out of windows that are generally unwanted.
Unfortunately, the only thing I can do to help with misclicks is to position the camera as appropriate as possible. And as far as the random menus that appear the most convenient thing for me to do is enable RM's built in event handler and hope for the best, the other option would be me gathering all of the unwanted menu's and continually check for them. (Not only would that be a huge pain, but I'd imagine it'd rarely be executed).
Regardless, Thanks for your feedback! I'm glad you're enjoying the bot
Thanks for bringing that to light to me Arbiter! I'm actually just using interactable.interact("Action"); I will look into this next time I sit down to mess with the code.
I don't know what you mean by this.
This. So people can shut down the bots in there anytime they want. And they are doing it alot :s
Sick, what a savage updateHandled client-side. Will be in the next update.
Dude sweet! May I like your post a million times?Handled client-side. Will be in the next update.
The interaction method was updated in the last push.
