Hey, I saw your feedback, I was going to PM you actually.
!possibly an issue on my end, not quite sure what was happening but I tried again and it continued to run in circles. I changed worlds and it worked fine
Sorry I just saw this actually.Following up on my recent review,
-Walks weirdly far sometimes, sometimes walks close
-Perhaps certain logic ought to be changed, because what if:
-you're walking close to a person when you walk to a vein closer to hopper, which looks weird, but not too weird because you're acting efficiently and going to closest vein.
-if you walk close to a person when you're walking further to a vein, which would look even weirder because who would both walk far, and right next to a person, double inefficiency, looks weird
Obviously none of this applies to upper level because upper level vein mechanics don't penalize efficiency as much with multiple people mining the same vein. I personally haven't tried top level option with this bot yet.
Edit: Yeah, just walked weirdly close towards a guy, lower west, walked past 12 fresh veins to mine right next to a dude. Too sketch for me, not gonna use
Edit2: I understand the concept of built in inefficiency for lower rate of detection, but if this sort of pathing was intended for that effect, then I believe it causes more red flags in other detection domains. If looking for a proper way to build inefficiency, build it into the afk time between veins, that's more human, which you obviously provide extensive option and variability for, in all of your bots
Edit3: In response to your response on my review, instead of random, I think it would be less odd and more humanlike if the bot went to the most efficient vein, the closest vein, rather than a random vein or even "weighted" random vein. Maybe prioritize a specific section, sort of like you have already designated as options, and then go to the closest available vein in that section. To me this would be less odd. But obviously I have a bit of an overachiever mind on these things, so I completely understand if this is taken as "nitpicky". Another idea is adding person-sensing, in the same way you've implemented it on your Miner bot, hop worlds if player within 1 tile, etc. but in this case it wouldn't be hopping, it would be running 7 squares away and then finding new vein.
Yeah I do definitely appreciate feedback, especially detailed feedback like yours. Totally honestly it's just hard to properly get to all the feedback because I've spread myself among so many botsYeah I see what you're saying, and you obviously have implemented more complex logic than I had assumed. I definitely see the difficulty in the optimal tweaking, especially with that many variables.
I slightly disagree with your assessment regarding real player behavior while afking in MLM, but hey, our own personal impressions and assumptions of "average behavior of members in a group" is always going to be a bit subjective without extensive data to determine statistically-sound solutions from.
Thanks for your response, I appreciate you!
Edit: After re-reading your message again and remember what I was experiencing while watching the bot behavior, the logic that bugs me is the "First-vein mined after unloading dirt" logic, not the "2nd+ vein mined after unloading dirt" logic --- perhaps this will help with optimization efforts if you so desire to tweak. I simply enjoy giving feedback, don't really mind if this is a priority or not. I figure better bots make you more money
But MLM is one of my most used bots so it should be high priority.
I've sent you a refund just now for 4 hours
Unfortunately there's nothing I can do here. This is another game's anticheat breaking Runemate and if anyone at Runemate can help you it'd be the client developers (eg Party), but I don't think he'd be able to do anything about a different game's anticheat disconnecting RM.
This only happens when Runemate returns an incorrect varp (basically Runemate is reading data from the cache wrong). It's not that my bot went out of sync, because it doesn't keep track of ore in the sack manually, it reads it from Runemate api (which reads it from the cache). Unfortunately there's not much I can do here either as it's just a weird RM quirk. Trust me I'd fix it if I could.
Hi, I can add it to my todo list but honestly I'm not really sure when I'll get the chance to implement it as it's pretty low priority. Using the coal bag only saves like, 10-30 seconds per full sack which is not much time at all in the long run.
