cuppajava
<3
cuppajava
<3
cuppajava
<3
cuppajava
<3
cuppajava
<3 <3 <3
cuppajava
<3 <3 <3
cuppajava
Hey, I think Runemate was having some intermittent issues at the time. It should be working now though?
As always, feel free to DM me if you're having further issues and I can help debug.
As always, feel free to DM me if you're having further issues and I can help debug.
cuppajava
<3 <3 <3
cuppajava
<3
cuppajava
<3 <3 <3
cuppajava
<3
cuppajava
<3 <3 <3 <3
cuppajava
Hey. So I can appreciate a balanced 3 star review, and the feedback as always.
But honestly, kind of makes assumptions about my work that just aren't true. Mostly regarding:
> But it really seems that these bots are just rushed out and not necessarily thought about in detail. And I feel the primary reason for this is just the sheer amount of bots Cuppa provides.
These bots really are not rushed out (besides the few bots I leave with [BETA] tags forever, like StallThief, Itemcollector, GoutTuber). The rest of my bots I actually spend a pretty huge amount on; For example this agility bot has had 89 updates over 3 years... I just have a lot of bots because I've consistently been working on these for a pretty long time now.
To respond to your specific feedback in your cons:
- 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.
- 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?
- 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.
Just as a side note, my philosophy is to prioritize "impactful" features over "bot startup convenience" ones, especially if the minor ones are difficult to test thoroughly (like all the different runes that could go into a pouch). So for example, the bot supports Byrophyta's staff & Tome of fire, Seers teleport, as well as every combination staff & rune (since they effect runes used) but not Rune pouch (since it has no benefit over nature runes in your inventory).
Anyway, I don't mean to sound like I'm totally rambling in this long reply, even though I recognize I am. Just wanted to share some thoughts. Next update should improve the slowness & lack of rune pouch support. Let me know if you notice any further issues.
But honestly, kind of makes assumptions about my work that just aren't true. Mostly regarding:
> But it really seems that these bots are just rushed out and not necessarily thought about in detail. And I feel the primary reason for this is just the sheer amount of bots Cuppa provides.
These bots really are not rushed out (besides the few bots I leave with [BETA] tags forever, like StallThief, Itemcollector, GoutTuber). The rest of my bots I actually spend a pretty huge amount on; For example this agility bot has had 89 updates over 3 years... I just have a lot of bots because I've consistently been working on these for a pretty long time now.
To respond to your specific feedback in your cons:
- 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.
- 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?
- 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.
Just as a side note, my philosophy is to prioritize "impactful" features over "bot startup convenience" ones, especially if the minor ones are difficult to test thoroughly (like all the different runes that could go into a pouch). So for example, the bot supports Byrophyta's staff & Tome of fire, Seers teleport, as well as every combination staff & rune (since they effect runes used) but not Rune pouch (since it has no benefit over nature runes in your inventory).
Anyway, I don't mean to sound like I'm totally rambling in this long reply, even though I recognize I am. Just wanted to share some thoughts. Next update should improve the slowness & lack of rune pouch support. Let me know if you notice any further issues.
cuppajava
<3
cuppajava
<3
cuppajava
<3
cuppajava
<3
cuppajava
It's hard to debug these types of issues in reviews; You could dm me with more info or post on the bot thread.
Are you seeing an error message or specific issue causing it to stop? I'm currently running the bot on my account, so it does seem to be working overall.
You could try running with less plugins, or in a different screen size (if using fixed, try resizable, and vice versa).
Are you seeing an error message or specific issue causing it to stop? I'm currently running the bot on my account, so it does seem to be working overall.
You could try running with less plugins, or in a different screen size (if using fixed, try resizable, and vice versa).