Leaderboard
Popular Content
Showing content with the highest reputation on 09/07/24 in all areas
-
1 point
-
'the intelligent choice' By @Czar CURRENT RECORD: 201 HOURS ALSO SUPPORTS SANDSTONE MINING & GRANITE MINING AT THE HOPPER. Lifetime updates and support, request a feature either on the main thread or on our active discord! For advice and strategies, join our discord! You can also purchase the bot with GP if you'd like. 84 HOUR PROGRESS ON A LEVEL 20 ACCOUNT Suicided account with mirror mode near rock crabs, 81 mining! I will probably go for 99 Even supports Ancient Essence Crystal mining! Preview: Mine 1 drop 1 item drop pre-hover feature: (it's faster in the actual update)1 point
-
NEW 2024: supports new south + east shortcuts, new hopper (upstairs), and mouse invokes!!! (just like runelite!) 'the intelligent choice' By Czar 63 Hours Runtime!! Agility Shortcut 70 hours run time https://i.imgur.com/wiF6VPO.png1 point
-
PRICE NOW 25$ LIFETIME, NO MORE MONTHLY! NEW! ADDED GRAND EXCHANGE BUYING/SELLING ADDED FIGHT BACK TO PKERS Screenshots BEST RECORD: 121 HOURS! Disclaimer: We cannot guarantee that you won't be pked ever. Setup Preview: Features coming soon: Muling Auto-bonding Imbuing MSB After Death Progressive Levelling1 point
-
The only Runecrafting bot you will need Purchase this INSANE bot here You can setup a master account (preferably your main account, can be any account) and a worker account (a throwaway bot account, or any account) will trade the master account and go to bank to get more runes etc. The main account (master) does not need to bot, and can be achieved through the normal RS client without a bot client. Supports: Air runes (1) (normal) & (abyss) Mind runes (2) (normal) & (abyss) Water runes (5) (normal) & (abyss) Earth runes (9) (normal) & (abyss) Mud runes (13) (earth altar) Lava runes (23) (fire altar) Fire runes (14) (normal) & (abyss) Body runes (20) (normal) & (abyss) Cosmic runes (27) (normal) & (abyss) Chaos runes (35) (normal) & (abyss) Astral runes (40) (normal) & (abyss) Nature runes (44) (normal) & (abyss) Law runes (54) (normal) & (abyss) Blood runes (abyss) & (zeah) Auto Arceuus Favour Solver Gets 100% arceuus favour for you Auto GE Restocking Sells runes, buys more supplies automatically Auto-equips chosen armour/robes Use Blood Essences Death Handler gets items from Death's office and repeats (Abyss) Glory mode, ferox mode, house spell/tabs Avoids pkers and hops worlds Uses mouse invokes for quicker runecrafting (stealth) Muling (BETA) will give money to your mules every X hours or profit Creates colossal pouch if you have the needle Results and screenshots1 point
-
Hey any word on stealing from homes with house keys and pickpocketing wealthy citizens1 point
-
1 point
-
Oh well that's cool! How about allowing the user to change more settings to customize its behaviour (like mouse movements)? Basically I think the robotic quality (in the mouseprofile I'm observing) comes from seemingly instantly accelerating to high speed, sharp angles when not moving in a straight line.1 point
-
1 point
-
efficient & flawless Link: Script now live: Here Features Bypasses Jagex's camera movement bot trap. new! Uses ESC key to close the interface new! Uses the higher xp method (aligns the camera to the target so it closes the menu when it pops up) NEVER gets in combat, 'tower' method of getting out of combat isn't even there (deliberately). Logs out when no money left Equips bronze arrows when necessary Displays 'goal' information, e.g. (at 77 range it will also show details for 80 range, time left, xp left, etc) Automatically equips higher level gear such as d'hide chaps and vambs Runs away just in case of emergency! ................................................................................................................................ With the bots on OSBot, Czar promises to deliver yet another incredible piece to the CzarBot empire. This means you will get to run the script with no worries about bans and xp waste. LEGENDARY HALL OF FAME 100 hour progress report Configuring the bot and the result: Set the npc attack option to 'Hidden' if you want to avoid deaths forever! For extra XP FAQ Why should I use this script when there are millions out there? It is the best script. Simply. Why are you releasing this now? It's time to make it public, it was privately shared with some friends and has been working flawlessly. Instructions There are no instructions. We do the all the work for you. CzarScriptingβ’ Tips If you are low level, you can use a ranging potion at level 33 ranged to get in the ranging guild. Try and have as high ranged bonus as possible. Gallery ANOTHER 1M TICKETS GAINED !!1 point
-
This is why "States" suck: What looks cleaner, this: enum State { CHOP, WALK_TO_BANK, WALK_TO_TREES, BANK } @Override public int onLoop() throws InterruptedException { switch(getState()) { case CHOP: chop(); break; case WALK_TO_BANK: getWalking().... break; case WALK_TO_TREES: getWalking().... break; case BANK: bank(); break; } return 0; } private State getState() { if (whatever) { return State.BANK; } else if (whatever) { return State.WALK_TO_BANK; } else if (whatever) { return State.WALK_TO_TREES; } else { return State.CHOP; } } Or this? : @Override public int onLoop() throws InterruptedException { if (whatever) { chop(); } else if (whatever) { getWalking().... } else if (whatever) { bank(); } else { getWalking().... } } Unless you are completely blind, I think you would agree the second is far more readable and much less code. Instead of having to look in a different method for the conditions, they are right there next to the code I am executing when they're satisfied. I don't need to maintain a redundant enum either. People will argue that using "States" are cleaner, however this is probably because they are not making use of the DRY principle, not making effective use of methods etc. and without "States" they would just throw all of their code into onLoop. As for "Tasks" or "Nodes", they have the exact same issues as "States" and more. People will argue they are cleaner because now each of their actions is in a nice self contained class, and the condition is in there too. However using this pattern you have now even less of an overview of the script as you did with states, and it's even harder to debug. Consider this: List<Node> someRandomAssNodes = new ArrayList<>(); @Override public int onLoop() throws InterruptedException { for (Node node : someRandomAssNodes) { if (node.validate()) { node.execute(); } } return 0; } The problem with this is that now in order to figure out how this script will execute I need to go into each of those Node classes, in the same order that you add them to the List and look at each of the validate methods and try and figure out how they all fit together: I mean, that pattern is pretty bonkers don't you think? Instead of having: WalkToBankNode ChopNode BankNode WalkToTreesNode DoSomeOtherShitIDKNode Why not just just write something simple, and easy to understand like my previous example. IF your script gets massively complex, then you should be making use of OOP principles to simplify it. You still don't need to use a weird 'Node' or 'Task' pattern, you can have a generic banking class without needing to add a validate method inside of it, and you can have a mining class without having a validate method in there either. Sorry if the some of the syntax is off, or I rambled.1 point