Welcome!

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

Sign up now!

MaxiOrbs TRIAL [Deleted]

Status
Not open for further replies.
Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,770
Last edited by a moderator:
Joined
Feb 7, 2017
Messages
269
This bot looks amazing. Is there any chance you could add an option to walk for ironmen that do not have multiple glories? In other words instead of teleporting back just take the same path back and bank? Obviously this would be worse gp and xp per hour but would be an amazing option.
 
Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,770
This bot looks amazing. Is there any chance you could add an option to walk for ironmen that do not have multiple glories? In other words instead of teleporting back just take the same path back and bank? Obviously this would be worse gp and xp per hour but would be an amazing option.
Thanks for reminding me, I was going to do this. Please note that the web isn't currently working for the path to the obelisk so this bot currently gets stuck once it goes down the edgeville trapdoor. Cloud will be looking into the web in this area today, so hopefully, it will be fixed soon. Feel free to use this trial version as a way of testing if it's been fixed yet :p
 
Joined
Feb 7, 2017
Messages
269
Thanks for reminding me, I was going to do this. Please note that the web isn't currently working for the path to the obelisk so this bot currently gets stuck once it goes down the edgeville trapdoor. Cloud will be looking into the web in this area today, so hopefully, it will be fixed soon. Feel free to use this trial version as a way of testing if it's been fixed yet :p
Any update on this?
 
Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,770
Any update on this?
Cloud was looking into it yesterday and saw what the problem was so hopefully it will be fixed shortly
 
Any update on this?
It's working now!

I'm currently working on a backup web that it can use if the RuneMate web is down. It won't work from anywhere on the map but it should work perfectly so long as you're in edgeville, the dungeon, ge or in front of lumbridge castle (where you spawn after dying).
 
Joined
Feb 7, 2017
Messages
269
Cloud was looking into it yesterday and saw what the problem was so hopefully it will be fixed shortly
 

It's working now!

I'm currently working on a backup web that it can use if the RuneMate web is down. It won't work from anywhere on the map but it should work perfectly so long as you're in edgeville, the dungeon, ge or in front of lumbridge castle (where you spawn after dying).
There still is only support for Glories though i'm assuming? No implementation of the walking to and from the obelisk yet?
 
Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,770
There still is only support for Glories though i'm assuming? No implementation of the walking to and from the obelisk yet?
Correct. That will come soon. I haven't produced any updates, that fix was on RuneMates side.
 
Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,770
Thank you for the info. Looking forward to trying it out.
Hey! I've just been working on implementing the feature you requested but I don't have any accounts to test with.
I'm going to release the update but please babysit and let me know if it works or not.

Edit: Updates out.
 
Last edited:
Joined
Feb 7, 2017
Messages
269
Hey! I've just been working on implementing the feature you requested but I don't have any accounts to test with.
I'm going to release the update but please babysit and let me know if it works or not.

Edit: Updates out.
I'll run it for a bit and let you know any issues it may be having, or if it runs completely smoothly. Thanks for the update.
 
I'll run it for a bit and let you know any issues it may be having, or if it runs completely smoothly. Thanks for the update.
Ok so just an update here. First of all the bot ran perfectly to the obelisk. It went down the trapdoor great, opened all the doors leading to the wilderness, made it to the obelisk and started making the air orbs. After the bot completed making all the orbs it ran into trouble. I'll link the logs below but it seems like it struggled with going back down the ladder, it stopped and the feedback was "max failed path rebuilds reached, stopping the bot." If theres anything else you'd like me to test let me know.

00:04:17 DEBUG Timed action (WebPath#getNext()) took 36ms
00:04:17 DEBUG [WebPath] getNext() returned null, construct a new path.
00:04:17 DEBUG Max failed path rebuilds reached, stopping the bot
00:04:17 INFO [MaxiBots] ---MaxiOrbs TRIAL V1.1.12 [OSRS] ---
00:04:17 INFO [MaxiBots] Runtime: 00:04:17
00:04:17 INFO [MaxiBots] Last status: Walking to banker (18)
00:04:17 INFO [MaxiBots] Total profit: 71334
00:04:17 INFO [MaxiBots] Shutting down all executors.
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-Executor': java.util.concurrent.ThreadPoolExecutor@a8dc73[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 29]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-VersionChecker': java.util.concurrent.ScheduledThreadPoolExecutor@1e48d67[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-RuntimeUpdater': java.util.concurrent.ScheduledThreadPoolExecutor@12f25f4[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 259]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-RuntimeUpdater': java.util.concurrent.ScheduledThreadPoolExecutor@1bfd425[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 229]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-UIUpdater': java.util.concurrent.ScheduledThreadPoolExecutor@18ad4a5[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 229]
00:04:17 INFO [MaxiBots] ---Thanks for using MaxiOrbs TRIAL!---
00:04:17 INFO Max failed path rebuilds reached, stopping the bot
 
Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,770
I'll run it for a bit and let you know any issues it may be having, or if it runs completely smoothly. Thanks for the update.
 

Ok so just an update here. First of all the bot ran perfectly to the obelisk. It went down the trapdoor great, opened all the doors leading to the wilderness, made it to the obelisk and started making the air orbs. After the bot completed making all the orbs it ran into trouble. I'll link the logs below but it seems like it struggled with going back down the ladder, it stopped and the feedback was "max failed path rebuilds reached, stopping the bot." If theres anything else you'd like me to test let me know.

00:04:17 DEBUG Timed action (WebPath#getNext()) took 36ms
00:04:17 DEBUG [WebPath] getNext() returned null, construct a new path.
00:04:17 DEBUG Max failed path rebuilds reached, stopping the bot
00:04:17 INFO [MaxiBots] ---MaxiOrbs TRIAL V1.1.12 [OSRS] ---
00:04:17 INFO [MaxiBots] Runtime: 00:04:17
00:04:17 INFO [MaxiBots] Last status: Walking to banker (18)
00:04:17 INFO [MaxiBots] Total profit: 71334
00:04:17 INFO [MaxiBots] Shutting down all executors.
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-Executor': java.util.concurrent.ThreadPoolExecutor@a8dc73[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 29]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-VersionChecker': java.util.concurrent.ScheduledThreadPoolExecutor@1e48d67[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-RuntimeUpdater': java.util.concurrent.ScheduledThreadPoolExecutor@12f25f4[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 259]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-RuntimeUpdater': java.util.concurrent.ScheduledThreadPoolExecutor@1bfd425[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 229]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-UIUpdater': java.util.concurrent.ScheduledThreadPoolExecutor@18ad4a5[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 229]
00:04:17 INFO [MaxiBots] ---Thanks for using MaxiOrbs TRIAL!---
00:04:17 INFO Max failed path rebuilds reached, stopping the bot
Bummer. Would you be able to lend me your account so i can debug it? I don't have any members accounts at the moment.
 
Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,770
Aidden updated MaxiOrbs TRIAL with a new update entry:

MaxiOrbs TRIAL v1.1.14 Released!

MaxiOrbs TRIAL updated to v1.1.14.

Read the rest of this update entry...
 
I'll run it for a bit and let you know any issues it may be having, or if it runs completely smoothly. Thanks for the update.
 

Ok so just an update here. First of all the bot ran perfectly to the obelisk. It went down the trapdoor great, opened all the doors leading to the wilderness, made it to the obelisk and started making the air orbs. After the bot completed making all the orbs it ran into trouble. I'll link the logs below but it seems like it struggled with going back down the ladder, it stopped and the feedback was "max failed path rebuilds reached, stopping the bot." If theres anything else you'd like me to test let me know.

00:04:17 DEBUG Timed action (WebPath#getNext()) took 36ms
00:04:17 DEBUG [WebPath] getNext() returned null, construct a new path.
00:04:17 DEBUG Max failed path rebuilds reached, stopping the bot
00:04:17 INFO [MaxiBots] ---MaxiOrbs TRIAL V1.1.12 [OSRS] ---
00:04:17 INFO [MaxiBots] Runtime: 00:04:17
00:04:17 INFO [MaxiBots] Last status: Walking to banker (18)
00:04:17 INFO [MaxiBots] Total profit: 71334
00:04:17 INFO [MaxiBots] Shutting down all executors.
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-Executor': java.util.concurrent.ThreadPoolExecutor@a8dc73[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 29]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-VersionChecker': java.util.concurrent.ScheduledThreadPoolExecutor@1e48d67[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-RuntimeUpdater': java.util.concurrent.ScheduledThreadPoolExecutor@12f25f4[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 259]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-RuntimeUpdater': java.util.concurrent.ScheduledThreadPoolExecutor@1bfd425[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 229]
00:04:17 DEBUG [MaxiBots-ThreadManager] Shutting down executor 'MaxiBots-UIUpdater': java.util.concurrent.ScheduledThreadPoolExecutor@18ad4a5[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 229]
00:04:17 INFO [MaxiBots] ---Thanks for using MaxiOrbs TRIAL!---
00:04:17 INFO Max failed path rebuilds reached, stopping the bot
Hey mate, this was fixed a couple of days ago. Let me know if there are any more issues!
 
Joined
Jun 1, 2019
Messages
1
Hey this bot looks great but I'm a bit paranoid to use it. Is there anything different in the trial version that might make it more susceptible to detection?

Any thoughts on the only listed review?
letitbe got perm banned after 1 hour of use. Didn`t use other bots, and it wasnt on a new account (it was on my main xd).
 
Author of MaxiBots
Joined
Dec 3, 2013
Messages
6,770
Hey this bot looks great but I'm a bit paranoid to use it. Is there anything different in the trial version that might make it more susceptible to detection?

Any thoughts on the only listed review?
letitbe got perm banned after 1 hour of use. Didn`t use other bots, and it wasnt on a new account (it was on my main xd).
There's no difference between the trial and the premium version.

That review shouldn't even still be up. Bans aren't cause for a poor review. He hasn't given any information at all to prove that this bot was the cause of the ban.

Because there are so many factors involved you can't just assume a ban was caused by a specific bot. Jagex often delay bans to cause confusion about what caused it (They stated this in an article years ago). If you've botted on a computer that's been flagged in some way, or on an IP that's been flagged, those things can also cause bans. Some people have even had bans (not from this bot) on an account that wasn't even botted on, just because they botted on a different account on the same machine or IP. You could also speculate that logging in to an account that's been flagged or previously banned on a machine and IP that's never been used for botting could result in bans on other accounts used on that machine/IP
 
Status
Not open for further replies.
Top