cuppajava
<3
cuppajava
<3
cuppajava
<3
cuppajava
I'm sorry you're not satisfied, but I've honestly done pretty much all I can feasibly do with this bot. I have a few more small updates planned, but it's clear I can't please every user.
I've ran this bot for over 50 hours on multiple accounts, and I've found that it only ever has a situation where it runs into a fire maybe once or twice an hour, which is amazing. And it's almost always in situations where a real player would get hit by it too (eg. there's a fire blocking the tether and a wave is coming, or there's too many fires, or a fire appears as we're pathing, etc). I'm not sure if you've used the bot in the last ~30 hours, but I've fixed a lot of common issues with fires, and like I said it hardly ever runs into them now.
Regarding the tethering, there's nothing else the bot can do here. If the mast is broken, it must fix it before tethering. If it can't do so in time, neither could a player. And fixing EVERY broken mast on sight is not the solution as it would then be obvious who is a bot. It does however always fix the mast if it's right near it.
Regarding being at 5% and walking to the fishing area and then to Tempoross: again, there's nothing to change here. There's already a random threshold at ~2-4% if the bot isn't doing anything it'll go prep at the pool. You seeing the bot at 5% is just outside this threshold and unlucky. If I raise the threshold to 5%, people will see the bot do the same thing at 6% and complain. The cutoff must be somewhere.
I don't intend to sound defensive, and I always implement feedback that is possible. It's just that, honestly, none of this has much room for improvement. I know that sounds like I'm just trying to brush off criticism, but I'm not. I'm just speaking honestly. Sorry for the long response.
I've ran this bot for over 50 hours on multiple accounts, and I've found that it only ever has a situation where it runs into a fire maybe once or twice an hour, which is amazing. And it's almost always in situations where a real player would get hit by it too (eg. there's a fire blocking the tether and a wave is coming, or there's too many fires, or a fire appears as we're pathing, etc). I'm not sure if you've used the bot in the last ~30 hours, but I've fixed a lot of common issues with fires, and like I said it hardly ever runs into them now.
Regarding the tethering, there's nothing else the bot can do here. If the mast is broken, it must fix it before tethering. If it can't do so in time, neither could a player. And fixing EVERY broken mast on sight is not the solution as it would then be obvious who is a bot. It does however always fix the mast if it's right near it.
Regarding being at 5% and walking to the fishing area and then to Tempoross: again, there's nothing to change here. There's already a random threshold at ~2-4% if the bot isn't doing anything it'll go prep at the pool. You seeing the bot at 5% is just outside this threshold and unlucky. If I raise the threshold to 5%, people will see the bot do the same thing at 6% and complain. The cutoff must be somewhere.
I don't intend to sound defensive, and I always implement feedback that is possible. It's just that, honestly, none of this has much room for improvement. I know that sounds like I'm just trying to brush off criticism, but I'm not. I'm just speaking honestly. Sorry for the long response.
cuppajava
<3
cuppajava
<3
cuppajava
You've posted 3 negative reviews in the past week. I understand you're unsatisfied but please stop spamming the same reviews.
As I said in response to your last review, Jagex updated Tempoross 4 days ago and I mostly fixed the bot already, but there remains a couple more improvements to be released.
I have an update queued, pending admin approval. I can't work any faster. Please have patience and understand I'm doing the best I can here.
As I said in response to your last review, Jagex updated Tempoross 4 days ago and I mostly fixed the bot already, but there remains a couple more improvements to be released.
I have an update queued, pending admin approval. I can't work any faster. Please have patience and understand I'm doing the best I can here.
cuppajava
Please just turn off camera movement. The camera movement is optional, and if you feel that it's "odd" then disable it.
I've made nothing but improvements over the past few weeks, so if something is working "worse" it's likely an issue on your end or just the fact that teammates have gotten lazier so the minigame is more of a mess now.
Jagex did update the minigame earlier this week & I issued a hotfix to make the bot work again, but it's possible I missed updating some things that still needed updating. I'll look into it more.
I hear complaints about my prices somewhat often and it honestly boggles my mind. I always release my bots as free initially & then slowly raise the price as I get it in a more stable state. This is so people can try it for cheap as it's in development. Your complaint that I've raised the price from 2 cents to 5 cents makes absolutely no sense, as most bot authors on the site just flat out release their bots at 8-12+ cents and never even have it cheap. There are no other 2 cent bots on the site, and I promise you this bot is already more complex than most of the 8c+ bots.
I will continue working on the bot, as I have been, but these complaints are largely helpful. In the future please just PM me or post on the bot thread with bug reports.
I've made nothing but improvements over the past few weeks, so if something is working "worse" it's likely an issue on your end or just the fact that teammates have gotten lazier so the minigame is more of a mess now.
Jagex did update the minigame earlier this week & I issued a hotfix to make the bot work again, but it's possible I missed updating some things that still needed updating. I'll look into it more.
I hear complaints about my prices somewhat often and it honestly boggles my mind. I always release my bots as free initially & then slowly raise the price as I get it in a more stable state. This is so people can try it for cheap as it's in development. Your complaint that I've raised the price from 2 cents to 5 cents makes absolutely no sense, as most bot authors on the site just flat out release their bots at 8-12+ cents and never even have it cheap. There are no other 2 cent bots on the site, and I promise you this bot is already more complex than most of the 8c+ bots.
I will continue working on the bot, as I have been, but these complaints are largely helpful. In the future please just PM me or post on the bot thread with bug reports.
cuppajava
Please don't post duplicated negative reviews, that's really unnecessary.
I understand you're having issues with the fires, but I'm not certain what to tell you as it's working properly for most people (including myself), and it's very rare for it to run into the fires for me, only happening once every few games if at all.
It's impossible for me to make it *never* run into fires, as Runemate's clicks are not precise and the bot will run differently on different PCs. I will continue to work on the bot, as I have been, but it's already in a state I am mostly satisfied with.
Edit: I'm running the bot now and it does seem to be working mostly as usual, though it is acting slightly differently around the fires some of the time, possibly due to jagex's update to Tempoross from last week. I'll look into it more. In the future please just PM me or post on the bot thread with bug reports.
I understand you're having issues with the fires, but I'm not certain what to tell you as it's working properly for most people (including myself), and it's very rare for it to run into the fires for me, only happening once every few games if at all.
It's impossible for me to make it *never* run into fires, as Runemate's clicks are not precise and the bot will run differently on different PCs. I will continue to work on the bot, as I have been, but it's already in a state I am mostly satisfied with.
Edit: I'm running the bot now and it does seem to be working mostly as usual, though it is acting slightly differently around the fires some of the time, possibly due to jagex's update to Tempoross from last week. I'll look into it more. In the future please just PM me or post on the bot thread with bug reports.
cuppajava
Hi :) The bot should definitely be using a dragon harpoon correctly, I use one myself whenever I run the bot.
It's possible this is a temporary Runemate bug, could you try restarting OSRS & Runemate and see if it fixes it? If it doesn't, you could also try clearing your OSRS game cache (can google for instructions), and then start both OSRS & Runemate again.
If you still have issues please PM me or post on the thread, as I don't know why else this could happen.
It's possible this is a temporary Runemate bug, could you try restarting OSRS & Runemate and see if it fixes it? If it doesn't, you could also try clearing your OSRS game cache (can google for instructions), and then start both OSRS & Runemate again.
If you still have issues please PM me or post on the thread, as I don't know why else this could happen.
cuppajava
<3
cuppajava
<3
cuppajava
<3
cuppajava
I do appreciate that this is a fair and balanced review, and no part of it is wrong, but I just want to keep expectations tempered here as well.
From a development standpoint, it's pretty much impossible for me to ever get this bot perfect, as Tempoross is one of the most mechanically complex activities that is available to be botted on Runemate. To give context, the closest comparable bot IMO, Prime Zulrah, does not have perfect runs either and often misclicks/gets hit, as is expected on a Zulrah bot. It's just more noticeable when doing Tempoross.
I've been making lots of incremental improvements and will continue to try to make it as consistent as possible, but I just wanted to point out that it can never be perfect due to how complex Tempoross is, even for real players.
Regarding the price, I just want to put into perspective that the bot was previously 2 cents (which is literally the cheapest bot on the store), and has been raised to 4 cents (which is now on par for the price of simple cannonball smithers), while being one of the most complex bots on Runemate. At 4 cents it's still half the price of 8 cent basic fishing bots.
Again, none of this is to sound defensive, and your review is entirely fair, I just wanted to put this all into context. I will continue working on it, and I appreciate the feedback.
From a development standpoint, it's pretty much impossible for me to ever get this bot perfect, as Tempoross is one of the most mechanically complex activities that is available to be botted on Runemate. To give context, the closest comparable bot IMO, Prime Zulrah, does not have perfect runs either and often misclicks/gets hit, as is expected on a Zulrah bot. It's just more noticeable when doing Tempoross.
I've been making lots of incremental improvements and will continue to try to make it as consistent as possible, but I just wanted to point out that it can never be perfect due to how complex Tempoross is, even for real players.
Regarding the price, I just want to put into perspective that the bot was previously 2 cents (which is literally the cheapest bot on the store), and has been raised to 4 cents (which is now on par for the price of simple cannonball smithers), while being one of the most complex bots on Runemate. At 4 cents it's still half the price of 8 cent basic fishing bots.
Again, none of this is to sound defensive, and your review is entirely fair, I just wanted to put this all into context. I will continue working on it, and I appreciate the feedback.