-
Posts
21901 -
Joined
-
Last visited
-
Days Won
1934 -
Feedback
100%
Everything posted by Czar
-
Fixed sorry. I was trying to make it compatible with the newer version of osbot (devbuild/new theme) and the old one is no longer starting up. Update will automatically go live within a couple hours, so sorry about this guys
-
Working better now? If not show console logger so we can help ^^ the bot is currently working as we speak btw! And did you have [Hop on crash tile] activated? If not dw about it, I'll try add a case so it knows how to prevent this scenario. Also with world hopper? Much respect ty sir, activated trial enjoy! Activated trial enjoy!
-
Dw about it, if you get another chance to use the script lemme know if it works better for you please ^^ As for trials activated enjoy. Still working on GE restocking guys, my apology for the delay.
-
Awesome! Lemme know if you have any other issues or feedback so I know what to do in the next pest control bot update please ^^
-
Sure, enjoy guys! Activated all, in other thread too
-
Not yet so sorry. It's a super unique/niche method that may as well be a private script by itself. I am going to add it as soon as I can, since I also need this type of system for my fighter bot and the code will be the same. I will let you know when it's added, but there is no promised date. For the record it's not as easy as people think Found the issue, will be in v141. I've talked to devs and other scripters and apparently the osbot webwalker prioritises roads over other paths, should be an easy fix. Will fix, along with the issue of varrock clay mine in terms of webwalking that @Diesal mentioned above It's supported, added trial enjoy Straight after tut (after botting tut) or manually completing tut? It makes a huge difference to be fair. The only data I have with bans is the thread, so we need to go back a few pages and see any reported bans. Are you planning on mass goldfarming or training a main? Please confirm so I can help further Yes activated trial enjoy. I'll update the thread to show that it's supported too, ty for the reminder
-
I'm happy to hear this, any hiccups or issues since then? Weekend's coming up for more blast furnace so I'll be preparing some accounts too I hope muling is ready before friday I know I keep saying this but it's a semi-complex task to add Where/when - questing, blast furnace, grand exchange? I will help Yes, but I recommend only botting blast furnace (in general) on throwaway accounts since it's a hotspot for bans. However if you must, then please keep the botting hours to a minimum of 1-2 hours per session followed by at least 2 hr breaks for the best results in my opinion (in terms of preventing bans).
-
RS Isn't even loading for me rip
-
I think I know exactly why - will be fixed for the update coming today. Any parts of the script which you would like to see sped up or slowed down? ^^ EDIT: Also any good progress (or hopefully not bans) btw? Or any pets? xD
-
Done trials activated enjoy. Yes the npc name for curse alch is fine, just be sure to choose a good place to curse alch
-
private CombatManager cm = new CombatManager(myPlayer(), gearNames, lummyCows, lootables); this needs to be: private CombatManage cm; and then in onLoop, you can do: if (cm == null && myPlayer() != null) { // once player exists, and if cm isn't instantiated, create one. cm = new CombatManager(myPlayer(), gearNames, lummyCows, lootables); } This can also be done in onStart but the player may either be logged out while the script is running and maybe not everything has been initialised just yet so it's better in onloop. If anyone has any recommendations or anything to contribute let us know xD So it's generally recommended to only instantiate stuff after the script starts, so that myPlayer() has meaning/context. Before the script runs it's null so you're essentially giving null parameters to the CombatManager class. Variables declared outside methods will execute before everything else, so you need to be wary of that xD If the above code still doesn't work we may need to see some more code to help
-
Done trials activated good luck!
-
Show us the main script's code, or just onStart/onLoop so we know everything's fine there. It could be an unhandled exception try wrapping your onStart and onLoops around a [try for] catch and log any issues that arise.
-
Will be releasing v136.0 which should be even better today. Trials activated enjoy! Added proggy to main thread good job please bot responsibly
-
@williamrg3temp or perm ban? If perm then don't forget to appeal the ban though it could take up to a week or two to get unbanned. Was it a main or a worker account? I highly recommend farming with workers and not mains, unless you're doing gold bars with goldsmithing gauntlets then I recommend keeping botting hours low, and botting in a non-358 world (that world is the go-to for all bots) and is a bit riskier than the others. If it was a worker then it should be banned later, unless you started botting before the weekend? I usually set up my bots on friday night and stop them just before monday morning to mule, and then the accounts usually get banned a couple hours later on monday. I don't know how others fare with their botting strategy but this my experience for a few years now. I've had a couple hiccups where I get banned if I started on thursday and wanted to bot from thursday -> monday but I just stopped botting from thursday and only prepared them on thursday and then started botting on friday - if that makes any sense @Lewiss119 update v114.0 should be live now the quests and GE aspect should be much much better. As for coins and paying blast foreman - I was worried that it would lose out on xp/profit if we kept banking for coins every 10 mins, should I add an option to choose whether to keep coins or deposit them? I think everyone would be happy instead of forcing the gp to be inside inventory all the time. Personally I felt safer keeping gp in inventory since it's fewer botted actions but that's just tinfoily of me. Guys update v114.0 is now live, enjoy! You should see improvements at GE restocking, questing, staminas and increased stability overall. More updates to come.
-
Done enjoy sir Bear in mind there's an update coming for v114.0 regarding questing and GE, please buy Camelot teleport tabs manually if you're planning on questing until the update goes live.
-
@lukerobbo95 Yes and yes staminas for questing is a huge request that i've seen, as well as buying staminas before questing and buying ore (for blast furnace later) before questing. I recommend waiting for v114.0 if you wanna start new accs, or for a temporary solution to buy camelot tabs manually before enabling the bot (just until we see the new version go live). All of these features will be in v114.0 today Also have you had any issues with teleporting to and from GE anymore? Regarding the [we've visited before...] logger mentioned a couple days back? In any case I'll get back to coding the update now xD Trial activated @annalysekeatin enjoy sir, I did double trial since we have release v114 on the way which affects GE, questing. Death mechanics should be out in an hour or so since it was an easy fix, but the questing/GE will take a couple more hours to update, i'll have it done asap. I wouldn't recommend botting blast furnace on mains since it's high risk, unless you plan on botting safely (and not 24/7 like some of us xD), using perhaps hardware mouse or new mouse botting like 1 hour per session followed by some 1-2 hour breaks or so.
-
EDIT: Amulet of chemistry seems to be working, which option are you using for herblore? Please confirm so I can help/update Lemme know your setup so I can test/debug asap
-
Looking good, please update us on your progress. Any hiccups or deaths/near misses while doing Knights' sword? As for the initial buying part I've found something which needs updating, should be available in today's major version update (v114.0). If you guys notice anything else lemme know! I haven't seen the accounts dying yet but I'm investigating how (& where) the player could have died. If anything I hope it's not related to memory/fps/network.