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!

MaxiWoodcutter

Overview Updates (166) Reviews (158) History Discussion
aidden

aidden

Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,771
Michael20 said:
Yeah I have 90+ WC and have used this bot at this spot before.

When i get home I'll give it a crack without urns. Draining my balance really quick as every time I try it charges me haha.

Any other things I could try?
Click to expand...
Test using the trial version so you don't get charged for premium. Alternatively, if you lend me your account I can just debug it directly
 
grometater

grometater

Joined
Nov 8, 2018
Messages
23
Still having the same issue with this bot where it just finishes the activity and logs out right when I start it. I've been using the trial to try and figure it out but no luck and to my knowledge this is the only wc bot that supports crystallize and light form. Any chance this can be fixed?
 
aidden

aidden

Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,771
Fresh Micks said:
Still having the same issue with this bot where it just finishes the activity and logs out right when I start it. I've been using the trial to try and figure it out but no luck and to my knowledge this is the only wc bot that supports crystallize and light form. Any chance this can be fixed?
Click to expand...
Hi. As stated previously, I don't have an account with access to that area so if you could lend me your account i could take a look. Otherwise, there's not much I can do unless it happens in all locations, not just Acadia's at Menaphos
 
grometater

grometater

Joined
Nov 8, 2018
Messages
23
Aidden said:
Hi. As stated previously, I don't have an account with access to that area so if you could lend me your account i could take a look. Otherwise, there's not much I can do unless it happens in all locations, not just Acadia's at Menaphos
Click to expand...
How long would it take for you to fix? And it's not just menaphos vip, outside of vip still doesn't work.
 
aidden

aidden

Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,771
Fresh Micks said:
How long would it take for you to fix? And it's not just menaphos vip, outside of vip still doesn't work.
Click to expand...
It depends on what the issue is and if it's actually an issue with the bot or with the client. If it's something broken in the bot i suspect it won't take more than an hour or two. I don't have an account with access to Menaphos at all. I don't play the game. I suppose i should probably get around to botting up a main on RS3 and OSRS at some point so that i don't have to borrow accounts for these sorts of things. All the questing will be a pain though.
 
grometater

grometater

Joined
Nov 8, 2018
Messages
23
Aidden said:
It depends on what the issue is and if it's actually an issue with the bot or with the client. If it's something broken in the bot i suspect it won't take more than an hour or two. I don't have an account with access to Menaphos at all. I don't play the game. I suppose i should probably get around to botting up a main on RS3 and OSRS at some point so that i don't have to borrow accounts for these sorts of things. All the questing will be a pain though.
Click to expand...
Questing sucks. You can borrow my account if it won't be for too long (plan on being on later tonight).
 
aidden

aidden

Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,771
Fresh Micks said:
Questing sucks. You can borrow my account if it won't be for too long (plan on being on later tonight).
Click to expand...
Thanks, just PM me the details. When is 'later tonight' for you?Just so i can prioritize my time
 
grometater

grometater

Joined
Nov 8, 2018
Messages
23
So I’m not sure if I did it right or if you get the notifications but I did message you. At least I think I did.
 
B

brob4hoes

Joined
Feb 6, 2018
Messages
8
Hey there is an issue with the bot logging me back in when it its coming off of a break. not sure it is something on my end or not. thank you
 
aidden

aidden

Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,771
Brob4hoes said:
Hey there is an issue with the bot logging me back in when it its coming off of a break. not sure it is something on my end or not. thank you
Click to expand...
Which game? As far as i'm aware, the log in handler for RS3 is broken so you'll have to wait for a client update to fix that.
 
F

fubie

Joined
Oct 14, 2019
Messages
7
I didn't know that everytime you start this bot it charges you regardless if you have used it more than one hour or not, dunno if this is just a feature with runemate either way i've been charged 0.60 now for a bot that isnt working for me ._. ... Anyhow, whenever I use this bot it gets stuck on the banking screen. I've tried cutting oaks in varrock, falador, draynor, lumbridge, and even tried cutting willows at edgeville and draynor and it always gets stuck at the banking screen.

upload_2019-11-1_15-50-53.png


Code: 
00:23:08 DEBUG    Attempting to hover Coordinate.Minimap(3103, 3491, 0) since the target of InteractablePoint(690, 60) is less then 4 pixels away.
00:23:08 DEBUG    Attempted to hover Coordinate.Minimap(3103, 3491, 0) since InteractablePoint(690, 60) was less than 4 pixels away (success: true)
00:23:13 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(301, 48) is less then 4 pixels away.
00:23:13 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(301, 48) was less than 4 pixels away (success: false)
00:23:13 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:13 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(304, 59) is less then 4 pixels away.
00:23:13 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(304, 59) was less than 4 pixels away (success: false)
00:23:13 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:14 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(308, 83) is less then 4 pixels away.
00:23:14 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(308, 83) was less than 4 pixels away (success: false)
00:23:14 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:14 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(306, 91) is less then 4 pixels away.
00:23:14 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(306, 91) was less than 4 pixels away (success: false)
00:23:14 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:14 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(301, 86) is less then 4 pixels away.
00:23:14 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(301, 86) was less than 4 pixels away (success: false)
00:23:14 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:14 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(305, 92) is less then 4 pixels away.
00:23:14 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(305, 92) was less than 4 pixels away (success: false)
00:23:14 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:55 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(274, 126) is less then 4 pixels away.
00:23:55 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(274, 126) was less than 4 pixels away (success: true)
00:29:07 DEBUG    [MaxiBots-Walker] Attempting to build a RegionPath. Coordinate(3115, 3497, 0) -> Coordinate(3093, 3491, 0)
00:29:07 DEBUG    [MaxiBots-Walker] Path building finished after 8ms
00:29:07 INFO    [MaxiBots-Walker] Path[Coordinate(3115, 3497, 0) -> Coordinate(3115, 3496, 0) -> Coordinate(3114, 3496, 0) -> Coordinate(3114, 3495, 0) -> Coordinate(3113, 3495, 0) -> Coordinate(3112, 3495, 0) -> Coordinate(3111, 3495, 0) -> Coordinate(3110, 3495, 0) -> Coordinate(3109, 3495, 0) -> Coordinate(3108, 3495, 0) -> Coordinate(3107, 3495, 0) -> Coordinate(3106, 3495, 0) -> Coordinate(3105, 3495, 0) -> Coordinate(3104, 3495, 0) -> Coordinate(3103, 3495, 0) -> Coordinate(3102, 3495, 0) -> Coordinate(3101, 3495, 0) -> Coordinate(3101, 3496, 0) -> Coordinate(3100, 3496, 0) -> Coordinate(3099, 3496, 0) -> Coordinate(3098, 3496, 0) -> Coordinate(3097, 3496, 0) -> Coordinate(3097, 3495, 0) -> Coordinate(3096, 3495, 0) -> Coordinate(3095, 3495, 0) -> Coordinate(3094, 3495, 0) -> Coordinate(3093, 3495, 0) -> Coordinate(3093, 3494, 0) -> Coordinate(3093, 3493, 0) -> Coordinate(3093, 3492, 0) -> Coordinate(3093, 3491, 0)]
00:29:08 DEBUG    Hovered InterfaceComponent [160, 22] on the first attempt.
00:29:08 DEBUG    Attempting to hover Coordinate.Minimap(3101, 3496, 0) since the target of InteractablePoint(604, 127) is less then 4 pixels away.
00:29:08 DEBUG    Attempted to hover Coordinate.Minimap(3101, 3496, 0) since InteractablePoint(604, 127) was less than 4 pixels away (success: true)
00:29:10 DEBUG    Attempting to hover Bank booth [3098, 3493, 0] since the target of InteractablePoint(86, 48) is less then 4 pixels away.
00:29:10 DEBUG    Attempted to hover Bank booth [3098, 3493, 0] since InteractablePoint(86, 48) was less than 4 pixels away (success: false)
00:29:10 DEBUG    We're not hovering Bank booth [3098, 3493, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:29:10 DEBUG    Failed to interact with Bank booth [3098, 3493, 0], turning the camera
00:29:10 DEBUG    Hovered Bank booth [3098, 3493, 0] on the first attempt.
00:29:14 DEBUG    Interacted with Bank booth [3098, 3493, 0] but failed to open the bank interface
00:29:15 DEBUG    Hovered Bank booth [3096, 3493, 0] on the first attempt.
00:29:15 DEBUG    Failed to interact with Bank booth [3096, 3493, 0], turning the camera
00:29:18 DEBUG    Hovered SpriteItem(name:Willow logs, quantity: 1, index: 1,  origin: INVENTORY) on the first attempt.
00:29:18 DEBUG    Attempting to hover MenuItem{4 : "Deposit-All" : "Willow logs" : InterfaceComponent [15, 3, 1]} since the target of InteractablePoint(573, 313) is less then 4 pixels away.
00:29:18 DEBUG    Attempted to hover MenuItem{4 : "Deposit-All" : "Willow logs" : InterfaceComponent [15, 3, 1]} since InteractablePoint(573, 313) was less than 4 pixels away (success: true)
 
aidden

aidden

Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,771
fubie said:
I didn't know that everytime you start this bot it charges you regardless if you have used it more than one hour or not, dunno if this is just a feature with runemate either way i've been charged 0.60 now for a bot that isnt working for me ._. ... Anyhow, whenever I use this bot it gets stuck on the banking screen. I've tried cutting oaks in varrock, falador, draynor, lumbridge, and even tried cutting willows at edgeville and draynor and it always gets stuck at the banking screen.

View attachment 9730


Code: 
00:23:08 DEBUG    Attempting to hover Coordinate.Minimap(3103, 3491, 0) since the target of InteractablePoint(690, 60) is less then 4 pixels away.
00:23:08 DEBUG    Attempted to hover Coordinate.Minimap(3103, 3491, 0) since InteractablePoint(690, 60) was less than 4 pixels away (success: true)
00:23:13 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(301, 48) is less then 4 pixels away.
00:23:13 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(301, 48) was less than 4 pixels away (success: false)
00:23:13 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:13 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(304, 59) is less then 4 pixels away.
00:23:13 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(304, 59) was less than 4 pixels away (success: false)
00:23:13 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:14 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(308, 83) is less then 4 pixels away.
00:23:14 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(308, 83) was less than 4 pixels away (success: false)
00:23:14 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:14 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(306, 91) is less then 4 pixels away.
00:23:14 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(306, 91) was less than 4 pixels away (success: false)
00:23:14 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:14 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(301, 86) is less then 4 pixels away.
00:23:14 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(301, 86) was less than 4 pixels away (success: false)
00:23:14 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:14 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(305, 92) is less then 4 pixels away.
00:23:14 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(305, 92) was less than 4 pixels away (success: false)
00:23:14 DEBUG    We're not hovering Willow [3116, 3497, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:23:55 DEBUG    Attempting to hover Willow [3116, 3497, 0] since the target of InteractablePoint(274, 126) is less then 4 pixels away.
00:23:55 DEBUG    Attempted to hover Willow [3116, 3497, 0] since InteractablePoint(274, 126) was less than 4 pixels away (success: true)
00:29:07 DEBUG    [MaxiBots-Walker] Attempting to build a RegionPath. Coordinate(3115, 3497, 0) -> Coordinate(3093, 3491, 0)
00:29:07 DEBUG    [MaxiBots-Walker] Path building finished after 8ms
00:29:07 INFO    [MaxiBots-Walker] Path[Coordinate(3115, 3497, 0) -> Coordinate(3115, 3496, 0) -> Coordinate(3114, 3496, 0) -> Coordinate(3114, 3495, 0) -> Coordinate(3113, 3495, 0) -> Coordinate(3112, 3495, 0) -> Coordinate(3111, 3495, 0) -> Coordinate(3110, 3495, 0) -> Coordinate(3109, 3495, 0) -> Coordinate(3108, 3495, 0) -> Coordinate(3107, 3495, 0) -> Coordinate(3106, 3495, 0) -> Coordinate(3105, 3495, 0) -> Coordinate(3104, 3495, 0) -> Coordinate(3103, 3495, 0) -> Coordinate(3102, 3495, 0) -> Coordinate(3101, 3495, 0) -> Coordinate(3101, 3496, 0) -> Coordinate(3100, 3496, 0) -> Coordinate(3099, 3496, 0) -> Coordinate(3098, 3496, 0) -> Coordinate(3097, 3496, 0) -> Coordinate(3097, 3495, 0) -> Coordinate(3096, 3495, 0) -> Coordinate(3095, 3495, 0) -> Coordinate(3094, 3495, 0) -> Coordinate(3093, 3495, 0) -> Coordinate(3093, 3494, 0) -> Coordinate(3093, 3493, 0) -> Coordinate(3093, 3492, 0) -> Coordinate(3093, 3491, 0)]
00:29:08 DEBUG    Hovered InterfaceComponent [160, 22] on the first attempt.
00:29:08 DEBUG    Attempting to hover Coordinate.Minimap(3101, 3496, 0) since the target of InteractablePoint(604, 127) is less then 4 pixels away.
00:29:08 DEBUG    Attempted to hover Coordinate.Minimap(3101, 3496, 0) since InteractablePoint(604, 127) was less than 4 pixels away (success: true)
00:29:10 DEBUG    Attempting to hover Bank booth [3098, 3493, 0] since the target of InteractablePoint(86, 48) is less then 4 pixels away.
00:29:10 DEBUG    Attempted to hover Bank booth [3098, 3493, 0] since InteractablePoint(86, 48) was less than 4 pixels away (success: false)
00:29:10 DEBUG    We're not hovering Bank booth [3098, 3493, 0] according to Interactable#isHovered() but our position does equal the desired target.
00:29:10 DEBUG    Failed to interact with Bank booth [3098, 3493, 0], turning the camera
00:29:10 DEBUG    Hovered Bank booth [3098, 3493, 0] on the first attempt.
00:29:14 DEBUG    Interacted with Bank booth [3098, 3493, 0] but failed to open the bank interface
00:29:15 DEBUG    Hovered Bank booth [3096, 3493, 0] on the first attempt.
00:29:15 DEBUG    Failed to interact with Bank booth [3096, 3493, 0], turning the camera
00:29:18 DEBUG    Hovered SpriteItem(name:Willow logs, quantity: 1, index: 1,  origin: INVENTORY) on the first attempt.
00:29:18 DEBUG    Attempting to hover MenuItem{4 : "Deposit-All" : "Willow logs" : InterfaceComponent [15, 3, 1]} since the target of InteractablePoint(573, 313) is less then 4 pixels away.
00:29:18 DEBUG    Attempted to hover MenuItem{4 : "Deposit-All" : "Willow logs" : InterfaceComponent [15, 3, 1]} since InteractablePoint(573, 313) was less than 4 pixels away (success: true)
Click to expand...
That's just how RuneMate charges you, we have no control over that. It's mentioned in the FAQs.
The logs are indicating an issue with RuneMate, not the bot. It's saying it tried to hover the item but failed over and over. I'm assuming your inventory is full of the logs?
 
Did you have your axe in the inventory? I can't replicate the failing to deposit any logs, but i did find a bug that occurs if you have more than 1 of the axe on your player - i.e equipped and in the inventory or multiple in the inventory.
So i've fixed that in the next release.
 
Last edited:
F

fubie

Joined
Oct 14, 2019
Messages
7
Aidden said:
That's just how RuneMate charges you, we have no control over that. It's mentioned in the FAQs.
The logs are indicating an issue with RuneMate, not the bot. It's saying it tried to hover the item but failed over and over. I'm assuming your inventory is full of the logs?
 
Did you have your axe in the inventory? I can't replicate the failing to deposit any logs, but i did find a bug that occurs if you have more than 1 of the axe on your player - i.e equipped and in the inventory or multiple in the inventory.
So i've fixed that in the next release.
Click to expand...
Whatever was in this last update fixed my problems
 
Top