Since I can't respond to your response, I felt it best to just try and continue on in here if that is alright.
First off, please don't take my review as some sort of shite talk. All of your bots are good, I've used your GOTR bot on another account for hours and hours (you might be able to see my use history, not sure) and I had never gotten banned. So with that being said I wanted to elaborate on my review.
CuppaJava said:
- Rune pouch: Honestly, I never added this because I don't see a benefit to using a Rune pouch in an agility bot; There's no limited inventory space or anything. But anyway, it's easy enough to add, the bot will support Rune pouch in the next update.
I try and PVM/Quest in between botting to try and make these accounts look a little less autonomous, with that being said I generally leave the same kind of runes in my rune pouch. Law, Nature, and Bloods. Then I use tome, and generally a mist staff. I can see why you feel there isn't a point in adding rune pouch support, it's just a QOL thing that other bots have, not only just from RuneMate. But I do appreciate your reconsideration.
CuppaJava said:
- Tome of fire: The bot does support Tome of fire, and has since 2020; I just tested it as well. Do you have a page in the tome?
I do have a page in, for some reason it isn't alching. It will run through the course numerous times and never alch, as soon as I put 1 fire rune in my inventory it works. Therefore I'd assumed it was broken.
CuppaJava said:
- Slow: This is actually mostly intentional. About a year ago, bans were way more common on Runemate (and this bot) so I went through every course manually, recorded roughly how long I personally delayed between each obstacle & added a (randomized/shorter) version of that delay to try to seem more human. In the next update, I'll make this an optional toggle though, since bans are less common these days.
- Various stopping options: this is a design choice due to Runemate's structure. Since Runemate charges when a bot is started & each subsequent hour, the best bang-for-your-buck is to stop the bot right before the hour, which is why I have that. I don't feel good about adding "stop at level" etc because I'm concerned about the bot stopping at like 5:02 because they just reached their level.
I'm responding to these two with my own personal point of view. But I personally like to have as much control over what happens with the bot as I possibly can. I 100% understand the premise behind the best bang for your buck, and I like that idea. However stopping the bot at 4:59 or what have you still doesn't look the greatest and then you could argue stopping the bot at 4:47 you're missing out on 13 minutes. Either way there's never the
perfect solution to it. But having as much control over it lets anyone do whatever they want with it. If I want to collect 170 marks for whatever reason, and that strictly be it; I can't do that only with time stop. Goal stop isn't as necessary since you can just calculate xp/hr and setup the time stop for that but either way. More control gives the feeling of a better product. At least for me. I also understand adding these things means adding a lot more "moving parts", which gives a lot more opportunity for things to break in the future. Coming from experience in selling dll injection hacks like walls and aimbot.
I guess without it being too long winded which it already is, I understand your point of view. So my review isn't necessarily the most fair, and I do apologize for that. I appreciate your response and I am excited to see what other bots you come out with in the future.
