based
There have been no ban reports for Based NMZ, so it is unlikely.
wait
This was caused by a RuneLite update on Saturday.
cuppajava
<3
Thank you for the feedback; I'll add these to my list and try to look into optimizations :)
Thank you for the feedback; I'll add these to my list and try to look into optimizations :)
cuppajava
Hey, thank you for the feedback. Just as an aside you can always contact me if there's things you'd like to see improved in the bot, as no one has ever mentioned any of these issues before I'm a bit surprised.
A few of these I can kind of picture how they'd happen, but a few I'm a bit stumped on honestly. You already have GPU plugin on & others off it sounds like, though DI enabled would help a couple misclick related ones too.
Just to address them:
> Dying while standing on the wrong side of a jaguar
Not sure how this would happen besides the bot misclicking. Enabling DI may help here, but please let me know if you have info on how I can reproduce the issue.
> taking a complete detour when killing only Blue moon and Eclipse moon
Honestly the bot pathing gets a bit confusing when only some moons are selected, and you haven't given much info on what the detour is. But my best guess is the bot left the Shrine south & went through the Prison/Red Moon area; I'll make it so it doesn't do that if red moon isn't enabled. Will be in next update.
> deciding to turn around last-minute to drink a cuppa
The bot tries to avoid this with some calculations but it's actually a bit complicated in code. Will try to have improved in next bot update but this should be uncommon anyway. Enabling DI would actually improve this too, because the bot is probably trying to click the stove while moving but runemate's mouse is bad at that.
> sometimes even getting stuck in a loop between entering Eclipse room and drinking a cuppa
If you ever see this happen, please send me a log from the session (help > view logs), your settings, and any other info that might help me pin it down. I've never had this reported before and can't reproduce it. But I'd love to fix it.
> randomly running to the other side of a moon occasionally
This could be a number of different things and isn't really possible for me to narrow down without more info. I'll keep an eye out for it though.
Anyway thank you for the feedback and I do look into all of it. A few of these things should be improved in the next update, but a couple of them I need more info on or I'll need to see if I can reproduce them.
A few of these I can kind of picture how they'd happen, but a few I'm a bit stumped on honestly. You already have GPU plugin on & others off it sounds like, though DI enabled would help a couple misclick related ones too.
Just to address them:
> Dying while standing on the wrong side of a jaguar
Not sure how this would happen besides the bot misclicking. Enabling DI may help here, but please let me know if you have info on how I can reproduce the issue.
> taking a complete detour when killing only Blue moon and Eclipse moon
Honestly the bot pathing gets a bit confusing when only some moons are selected, and you haven't given much info on what the detour is. But my best guess is the bot left the Shrine south & went through the Prison/Red Moon area; I'll make it so it doesn't do that if red moon isn't enabled. Will be in next update.
> deciding to turn around last-minute to drink a cuppa
The bot tries to avoid this with some calculations but it's actually a bit complicated in code. Will try to have improved in next bot update but this should be uncommon anyway. Enabling DI would actually improve this too, because the bot is probably trying to click the stove while moving but runemate's mouse is bad at that.
> sometimes even getting stuck in a loop between entering Eclipse room and drinking a cuppa
If you ever see this happen, please send me a log from the session (help > view logs), your settings, and any other info that might help me pin it down. I've never had this reported before and can't reproduce it. But I'd love to fix it.
> randomly running to the other side of a moon occasionally
This could be a number of different things and isn't really possible for me to narrow down without more info. I'll keep an eye out for it though.
Anyway thank you for the feedback and I do look into all of it. A few of these things should be improved in the next update, but a couple of them I need more info on or I'll need to see if I can reproduce them.
2006bottingftw
Thanks for the review but sorry for the inconvenience!
This is a feature if you fail to catch fish multiple times in a row because there's a problem with memory leaks and the fishing spots.
So in short, from time to time the spots become static in memory while actually not existing. Making the bot think there's a fishing spot but there isn't.
Once you relog this will reset the memory of the spots and you're not gonna click an "invisible spot".
Some times you're unlucky and multiple spawns get stuck in short intervals making you relog more often. But overall there's no other good workaround for this issue. The bot will log in again, the delay can be very varied though. But it will log in again within 5-30 seconds.
This is a feature if you fail to catch fish multiple times in a row because there's a problem with memory leaks and the fishing spots.
So in short, from time to time the spots become static in memory while actually not existing. Making the bot think there's a fishing spot but there isn't.
Once you relog this will reset the memory of the spots and you're not gonna click an "invisible spot".
Some times you're unlucky and multiple spawns get stuck in short intervals making you relog more often. But overall there's no other good workaround for this issue. The bot will log in again, the delay can be very varied though. But it will log in again within 5-30 seconds.
cuppajava
<3
cuppajava
<3
Thank you for following up and I'm glad it's working well now!
Thank you for following up and I'm glad it's working well now!
cuppajava
I'm sorry you got banned. Unfortunately, despite my best efforts, bans are always a possibility.
Honestly botting this at edgeville for 12 hours would not be recommended however, as it is a heavily botted & repetitive activity. Also, if you used any other bots within the past couple weeks it is also possible they were the cause of the ban, as Jagex often delays bans. But I am sorry either way.
Honestly botting this at edgeville for 12 hours would not be recommended however, as it is a heavily botted & repetitive activity. Also, if you used any other bots within the past couple weeks it is also possible they were the cause of the ban, as Jagex often delays bans. But I am sorry either way.