Navigation

Navigation section

Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!

Cuppa Herbiboar [Deleted]

Status
Not open for further replies.
cuppajava

cuppajava

cuppa.drink(java);
Joined
Mar 13, 2018
Messages
6,661
amour said:
@CuppaJava Does this support regular secateurs, or only magical?
Click to expand...
It should support both :) I've mostly tested it with magical, but regular worked when I tried it.

Feel free to test it out on the trial version and let me know if you have any issues.
 
Z

ziplock1738

Joined
Feb 7, 2017
Messages
269
I'm at about 500kc with this bot so far, and it has really been great. One thing I noticed recently that I'm not entirely sure what is causing it but the bot will continuously close the herb sack even when herb sack is toggled on. I've tried running the bot starting with it open vs closed and it doesn't seem to make much of a difference. It also doesn't happen every time, occasionally it will get stuck in the loop and other times it will work fine. Otherwise bot is running perfectly.


I should mention that the bot still does click on the herb sack with the "fill" action. In other words, the bot still works I just didn't know if this was an intentional feature as opposed to just having the sack stay open.
 
Last edited:
cuppajava

cuppajava

cuppa.drink(java);
Joined
Mar 13, 2018
Messages
6,661
ziplock1738 said:
I'm at about 500kc with this bot so far, and it has really been great. One thing I noticed recently that I'm not entirely sure what is causing it but the bot will continuously close the herb sack even when herb sack is toggled on. I've tried running the bot starting with it open vs closed and it doesn't seem to make much of a difference. It also doesn't happen every time, occasionally it will get stuck in the loop and other times it will work fine. Otherwise bot is running perfectly.


I should mention that the bot still does click on the herb sack with the "fill" action. In other words, the bot still works I just didn't know if this was an intentional feature as opposed to just having the sack stay open.
Click to expand...
This is intentional currently, the bot will close the bag if it's open.

Someone (I forget who, mighta been you) mentioned to me that the bot breaks when the bag is open, so the bot will now close it if it notices it's open. It's possible for me to support leaving the herb sack "open" in the future, but it requires making some annoying logic changes on my end so it's kinda low-priority.

And honestly leaving the herb back "closed" and just clicking to fill it 3-4 times a trip is a really small functional difference in my mind, which is why I haven't supported leaving it "open" yet.
 
A

amour

Joined
Aug 18, 2020
Messages
17
Ran it for 415kc straight, worked exceptionally except for a few snags when it couldn't track the route but the world hopping failsafe made short work of that issue every time. Thank you for consistently pushing out such quality work Cuppa.
 
cuppajava

cuppajava

cuppa.drink(java);
Joined
Mar 13, 2018
Messages
6,661
Last edited:
N

niini

Joined
May 20, 2019
Messages
28
Hey Cuppa, what are your suggestions for maximum performance, e.g. fixed mode, banking at cwars vs fossil island etc?
 
cuppajava

cuppajava

cuppa.drink(java);
Joined
Mar 13, 2018
Messages
6,661
Niini said:
Hey Cuppa, what are your suggestions for maximum performance, e.g. fixed mode, banking at cwars vs fossil island etc?
Click to expand...
I'd recommend fixed mode on all bots on runemate, as runemate has a (rare, but possible) bug to incorrectly think something is visible when it's hidden behind the chatbox or inventory. This never happens in fixed mode.

Both bankings should be similar but I imagine cwars would be a bit quicker. And then whichever potions really, besides regular energy potions probably.
 
A

amour

Joined
Aug 18, 2020
Messages
17
Hey Cuppa, nothing wrong with your bot itself constituting this, working amazing as always, however..
Yesterday I was running when the game happened to update a bit after I started, kept running for over 3hrs while client had to be restarted.
Any chance you could refund those 3hrs?
247b2c12e6d5e101599f452dddbc74a0.jpg
 
A

amour

Joined
Aug 18, 2020
Messages
17
Appreciate you Cuppa. I wanted to make you aware, this was the first time this has ever happened to me with your herbiboar bot and I do keep my NPC attack options hidden, but woke up to a gravestone here;
upload_2020-11-7_4-54-56.png

08:58:42 DEBUG Hovered Coordinate.Minimap(3686, 3891, 0) on the first attempt.
08:58:43 INFO Stepped using minimap path.
08:58:43 INFO Trying to figure out what our next traversal point is...
08:58:43 INFO Using bresenham.
08:58:44 DEBUG Hovered Coordinate.Minimap(3691, 3893, 0) on the first attempt.
08:58:44 INFO Stepped using minimap path.
08:58:44 INFO Trying to figure out what our next traversal point is...
08:58:44 INFO Using bresenham.
08:58:45 DEBUG Hovered Coordinate.Minimap(3695, 3893, 0) on the first attempt.
08:58:45 INFO Stepped using minimap path.
08:58:46 INFO Trying to figure out what our next traversal point is...
08:58:46 INFO Using bresenham.
08:58:47 DEBUG Hovered Coordinate.Minimap(3700, 3894, 0) on the first attempt.
08:58:47 INFO Stepped using minimap path.
08:58:47 INFO Trying to figure out what our next traversal point is...
08:58:47 INFO Using bresenham.
08:58:48 DEBUG Attempting to hover Coordinate.Minimap(3700, 3894, 0) since the target of InteractablePoint(694, 80) is less then 4 pixels away.
08:58:48 DEBUG Attempted to hover Coordinate.Minimap(3700, 3894, 0) since InteractablePoint(694, 80) was less than 4 pixels away (success: true)
08:58:48 INFO Stepped using minimap path.
08:58:48 INFO Trying to figure out what our next traversal point is...
08:58:48 INFO Using bresenham.
08:58:49 DEBUG Attempting to hover Coordinate.Minimap(3701, 3893, 0) since the target of InteractablePoint(694, 96) is less then 4 pixels away.
08:58:49 DEBUG Attempted to hover Coordinate.Minimap(3701, 3893, 0) since InteractablePoint(694, 96) was less than 4 pixels away (success: false)
08:58:49 DEBUG We're not hovering Coordinate.Minimap(3701, 3893, 0) according to Interactable#isHovered() but our position does equal the desired target.
08:58:49 INFO Stepped using minimap path.
08:58:50 INFO Trying to figure out what our next traversal point is...
08:58:50 INFO Using bresenham.
08:58:51 DEBUG Hovered Coordinate.Minimap(3708, 3895, 0) on the first attempt.
08:58:51 INFO Stepped using minimap path.
08:58:51 INFO Trying to figure out what our next traversal point is...
08:58:51 INFO Using bresenham.
08:58:53 DEBUG Attempting to hover Coordinate.Minimap(3712, 3896, 0) since the target of InteractablePoint(694, 88) is less then 4 pixels away.
08:58:53 DEBUG Attempted to hover Coordinate.Minimap(3712, 3896, 0) since InteractablePoint(694, 88) was less than 4 pixels away (success: false)
08:58:53 DEBUG We're not hovering Coordinate.Minimap(3712, 3896, 0) according to Interactable#isHovered() but our position does equal the desired target.
08:58:53 INFO Stepped using minimap path.
08:58:53 INFO Trying to figure out what our next traversal point is...
08:58:53 INFO Using bresenham.
08:58:54 DEBUG Attempting to hover Coordinate.Minimap(3717, 3893, 0) since the target of InteractablePoint(694, 96) is less then 4 pixels away.
08:58:54 DEBUG Attempted to hover Coordinate.Minimap(3717, 3893, 0) since InteractablePoint(694, 96) was less than 4 pixels away (success: true)
08:58:54 INFO Stepped using minimap path.
08:58:54 INFO Trying to figure out what our next traversal point is...
08:58:54 INFO Using bresenham.
08:58:56 DEBUG Attempting to hover Coordinate.Minimap(3722, 3894, 0) since the target of InteractablePoint(694, 92) is less then 4 pixels away.
08:58:56 DEBUG Attempted to hover Coordinate.Minimap(3722, 3894, 0) since InteractablePoint(694, 92) was less than 4 pixels away (success: true)
08:58:56 INFO Stepped using minimap path.
08:58:56 INFO Trying to figure out what our next traversal point is...
08:58:57 DEBUG Attempting to hover Coordinate.Minimap(3726, 3895, 0) since the target of InteractablePoint(690, 88) is less then 4 pixels away.
08:58:57 DEBUG Attempted to hover Coordinate.Minimap(3726, 3895, 0) since InteractablePoint(690, 88) was less than 4 pixels away (success: false)
08:58:57 DEBUG We're not hovering Coordinate.Minimap(3726, 3895, 0) according to Interactable#isHovered() but our position does equal the desired target.
08:58:57 INFO Stepped using minimap path.
08:58:57 INFO Trying to figure out what our next traversal point is...
08:58:59 DEBUG Attempting to hover Coordinate.Minimap(3729, 3893, 0) since the target of InteractablePoint(682, 96) is less then 4 pixels away.
08:58:59 DEBUG Attempted to hover Coordinate.Minimap(3729, 3893, 0) since InteractablePoint(682, 96) was less than 4 pixels away (success: false)
08:58:59 DEBUG We're not hovering Coordinate.Minimap(3729, 3893, 0) according to Interactable#isHovered() but our position does equal the desired target.
08:58:59 INFO Stepped using minimap path.
08:58:59 INFO Inspecting a target.
08:59:00 DEBUG Attempting to hover Seaweed [3728, 3893, 0] since the target of InteractablePoint(421, 235) is less then 4 pixels away.
08:59:00 DEBUG Attempted to hover Seaweed [3728, 3893, 0] since InteractablePoint(421, 235) was less than 4 pixels away (success: false)
08:59:00 DEBUG We're not hovering Seaweed [3728, 3893, 0] according to Interactable#isHovered() but our position does equal the desired target.
08:59:00 INFO Inspecting a target.
08:59:00 DEBUG Attempting to hover Seaweed [3728, 3893, 0] since the target of InteractablePoint(361, 237) is less then 4 pixels away.
08:59:00 DEBUG Attempted to hover Seaweed [3728, 3893, 0] since InteractablePoint(361, 237) was less than 4 pixels away (success: false)
08:59:00 DEBUG We're not hovering Seaweed [3728, 3893, 0] according to Interactable#isHovered() but our position does equal the desired target.
08:59:00 INFO Inspecting a target.
08:59:01 DEBUG Attempting to hover Seaweed [3728, 3893, 0] since the target of InteractablePoint(318, 194) is less then 4 pixels away.
08:59:01 DEBUG Attempted to hover Seaweed [3728, 3893, 0] since InteractablePoint(318, 194) was less than 4 pixels away (success: false)
08:59:01 DEBUG We're not hovering Seaweed [3728, 3893, 0] according to Interactable#isHovered() but our position does equal the desired target.
08:59:01 INFO Inspecting a target.
08:59:02 DEBUG Attempting to hover Seaweed [3728, 3893, 0] since the target of InteractablePoint(284, 170) is less then 4 pixels away.
08:59:02 DEBUG Attempted to hover Seaweed [3728, 3893, 0] since InteractablePoint(284, 170) was less than 4 pixels away (success: false)
08:59:02 DEBUG We're not hovering Seaweed [3728, 3893, 0] according to Interactable#isHovered() but our position does equal the desired target.
08:59:02 INFO Inspecting a target.
08:59:02 DEBUG Attempting to hover Seaweed [3728, 3893, 0] since the target of InteractablePoint(250, 159) is less then 4 pixels away.
08:59:02 DEBUG Attempted to hover Seaweed [3728, 3893, 0] since InteractablePoint(250, 159) was less than 4 pixels away (success: false)
08:59:02 DEBUG We're not hovering Seaweed [3728, 3893, 0] according to Interactable#isHovered() but our position does equal the desired target.
08:59:02 INFO Inspecting a target.
08:59:03 DEBUG Hovered Seaweed [3728, 3893, 0] on the first attempt.
08:59:03 INFO Inspecting a target.
08:59:03 DEBUG Attempting to hover Seaweed [3728, 3893, 0] since the target of InteractablePoint(224, 164) is less then 4 pixels away.
08:59:04 DEBUG Attempted to hover Seaweed [3728, 3893, 0] since InteractablePoint(224, 164) was less than 4 pixels away (success: true)
08:59:07 INFO Traversing towards the nearest tracking start location.
08:59:07 INFO Trying to figure out what our next traversal point is...
08:59:07 INFO Using bresenham.
08:59:08 DEBUG Attempting to hover Coordinate.Minimap(3735, 3880, 0) since the target of InteractablePoint(666, 136) is less then 4 pixels away.
08:59:08 DEBUG Attempted to hover Coordinate.Minimap(3735, 3880, 0) since InteractablePoint(666, 136) was less than 4 pixels away (success: true)
08:59:08 INFO Stepped using minimap path.
08:59:09 INFO Traversing towards the nearest tracking start location.
08:59:09 INFO Trying to figure out what our next traversal point is...
08:59:09 INFO Using bresenham.
08:59:10 DEBUG Attempting to hover Coordinate.Minimap(3737, 3878, 0) since the target of InteractablePoint(662, 136) is less then 4 pixels away.
08:59:10 DEBUG Attempted to hover Coordinate.Minimap(3737, 3878, 0) since InteractablePoint(662, 136) was less than 4 pixels away (success: true)
08:59:11 INFO Stepped using minimap path.
08:59:11 INFO Traversing towards the nearest tracking start location.
08:59:11 INFO Trying to figure out what our next traversal point is...
08:59:11 INFO Using bresenham.
08:59:13 DEBUG Attempting to hover Coordinate.Minimap(3741, 3871, 0) since the target of InteractablePoint(658, 140) is less then 4 pixels away.
08:59:13 DEBUG Attempted to hover Coordinate.Minimap(3741, 3871, 0) since InteractablePoint(658, 140) was less than 4 pixels away (success: true)
08:59:13 INFO Stepped using minimap path.
08:59:14 INFO Traversing towards the nearest tracking start location.
08:59:14 INFO Trying to figure out what our next traversal point is...
08:59:14 INFO Using bresenham.
08:59:15 DEBUG Attempting to hover Coordinate.Minimap(3742, 3872, 0) since the target of InteractablePoint(662, 136) is less then 4 pixels away.
08:59:15 DEBUG Attempted to hover Coordinate.Minimap(3742, 3872, 0) since InteractablePoint(662, 136) was less than 4 pixels away (success: true)
08:59:15 INFO Stepped using minimap path.
08:59:17 INFO Traversing towards the nearest tracking start location.
08:59:17 INFO Trying to figure out what our next traversal point is...
08:59:17 INFO Using bresenham.
08:59:18 DEBUG Hovered Coordinate.Minimap(3742, 3872, 0) on the first attempt.
08:59:18 INFO Stepped using minimap path.
08:59:20 INFO Traversing towards the nearest tracking start location.
08:59:20 INFO Trying to figure out what our next traversal point is...
08:59:20 INFO Using bresenham.
08:59:21 DEBUG Hovered Coordinate.Minimap(3742, 3872, 0) on the first attempt.
08:59:21 INFO Stepped using minimap path.
08:59:23 INFO Traversing towards the nearest tracking start location.
08:59:23 INFO Trying to figure out what our next traversal point is...
08:59:23 INFO Using bresenham.
08:59:24 DEBUG Hovered Coordinate.Minimap(3742, 3872, 0) on the first attempt.
08:59:24 INFO Stepped using minimap path.
08:59:26 INFO Traversing towards the nearest tracking start location.
08:59:26 INFO Trying to figure out what our next traversal point is...
08:59:26 INFO Using bresenham.
08:59:27 DEBUG Hovered Coordinate.Minimap(3742, 3872, 0) on the first attempt.
08:59:27 INFO Stepped using minimap path.
08:59:29 INFO Traversing towards the nearest tracking start location.
08:59:29 INFO Trying to figure out what our next traversal point is...
08:59:29 INFO Using bresenham.
08:59:30 DEBUG Hovered Coordinate.Minimap(3742, 3872, 0) on the first attempt.
08:59:30 INFO Stepped using minimap path.
08:59:32 INFO Traversing towards the nearest tracking start location.
08:59:32 INFO Trying to figure out what our next traversal point is...
08:59:32 INFO Using bresenham.
08:59:33 DEBUG Hovered Coordinate.Minimap(3742, 3872, 0) on the first attempt.
08:59:33 INFO Stepped using minimap path.
08:59:34 INFO Traversing towards the nearest tracking start location.
08:59:34 INFO Trying to figure out what our next traversal point is...
08:59:34 INFO Using bresenham.
 
K

kickpointy

Joined
Jan 1, 2019
Messages
132
^ i had this happen to me on leagues and I believe I caught a ban from it. didn't mention it because I figured it was a one-off incident, as I have 4500kc on the main game and I never experienced this. I was banking at the fossil island chest on leagues though, vs. castle wars on the main game. So I'm guessing it's related to banking on fossil island?
 
cuppajava

cuppajava

cuppa.drink(java);
Joined
Mar 13, 2018
Messages
6,661
Damn, okay yeah this is probably the bot's pathing messing up when it runs out of space really close to the top right. I'll try to tweak the bot's traversal logic to more explicitly avoid this issue.
 
A

amour

Joined
Aug 18, 2020
Messages
17
No worries. It wouldn't be as large an issue if it wasn't for the herbi pet possibly being gained and loss during a session due to it, however like I've mentioned, it works amazingly other than the occasional thing like this here and there. Really well done.
 
Status
Not open for further replies.
Top