cuppajava
I'm glad it worked well for you overall :)
I am sorry you got temp banned. I don't mean to sound like I'm passing the buck here, but honestly it's pretty unlikely this bot is the one that got you banned. Jagex often delays bans to confuse botters & doesn't ban you right after, and also Cuppa Tempoross has gotten very few reports of bans (and mostly only from people with 2000-4000+ kc, so honestly there's a good chance it was a different bot you used in the past couple weeks that got you banned.
I am sorry to hear it either way, and it is possible it was this bot, but I'd honestly say it's unlikely.
I am sorry you got temp banned. I don't mean to sound like I'm passing the buck here, but honestly it's pretty unlikely this bot is the one that got you banned. Jagex often delays bans to confuse botters & doesn't ban you right after, and also Cuppa Tempoross has gotten very few reports of bans (and mostly only from people with 2000-4000+ kc, so honestly there's a good chance it was a different bot you used in the past couple weeks that got you banned.
I am sorry to hear it either way, and it is possible it was this bot, but I'd honestly say it's unlikely.
cuppajava
A fellow Coffee man, I am not surprised you have good taste ,':^)
cuppajava
You are totally correct, thank you for letting me know :) This will be fixed in the next update.
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.
Often issues like this can be fixed by restarting both OSRS & Runemate and trying again, especially after game updates. But if that doesn't work, you could try closing OSRS & Runemate, clearing your OSRS game cache (google where it can be found) and try again.
Feel free to test using the lite version so you don't get charged while debugging :) And in the future please post bug reports on the thread so I can help you out without negative reviews for temporary bugs.