Leaderboard
Popular Content
Showing content with the highest reputation on 10/13/19 in Posts
-
Thanks for the information & offering for me to leave this be as is right now. That being said, I do want to resolve this issue, by at least implementing the quickfix we talked about. Chance is you'll have to remind me a couple more times before I'll actually be able to do this, but I'm most definitely planning to actually work on this. Please do not hesitate to remind me about this on Discord every 2 days!2 points
-
Stronghold Of Security Completer Thanks To @sheeper22 For the Logo. Features: How To Use: Pictures: Bug Report Form: Changelog:1 point
-
$9,99 for Lifetime use Visit the store HERE! Script Features: Highly customisable solving - continuous solve speed slider and a range of solve order modes Ability to choose exactly which runes to buy (with option to buy all runes without opening store) Real-time profit tracking with live exchange data to accurately model your profit estimates Web-walking - the script can be started anywhere, and will make its own way to Ali Morrisane Quick and easy to configure re-sizeable setup GUI Informative self-generating paint with hourly rate data displayed Smart Sudoku solving logic and board data reading means the script will never fail a Sudoku Error correction - the script can determine and overwrite incorrect rune tiles if necessary Mouse teleportation - If desired, the script can be configured to teleport the mouse between squares to solve sudokus at rapid speeds Optional debug settings show the Sudoku solve process and upcoming generated moves Stops and logs out when out of money to spend Rune Sudoku Requirements: Rune Mysteries Quest The Feud Quest 30 Thieving Start the Rogue Trader Minigame (details below) Before automating the solving process, you will have to start the Rogue Trader Minigame and solve a single Rune Sudoku puzzle. To do this, after the two above quests have been completed, talk to Ali Morrisane, agree to help him, then talk to Aubury in Varrock rune shop. Then, after returning to Ali Morrisane, the script can be started (note that there will be a slightly extended dialogue for the first solve). Things to consider before trying/buying: Due to the nature of this script, it can be considered quite risky to use, especially on the faster solve speed settings - a human would struggle to keep up. However, as we enter the era of third party clients with graphical overlays, the lines between humans and bots for puzzle solving draw closer - provided you use the script carefully with sensible precautions in place, this script should be no riskier than any other. Conditional vs. Unconditional solving - To allow you to personalise your session settings and ensure that the script runs differently every time you start the script, I added a continuous solve-speed slider on the startup interface. This slider, beyond a certain threshold, makes the script run in unconditional mode. This mode means that the script will move on to the next queued action before verifying that the previous action executed correctly. For example, when placing runes, the script will place one then move on to placing the next before ensuring that the previous one was placed correctly/successfully. Why would you want this? Well - when you click to place a rune, that rune appears on the next game tick. As a result, after clicking a rune tile, it can be up to 0.59 seconds before appearing which is 0.59 seconds the script can be doing something productive other than waiting! This means that solve speeds rapidly increase, however there is a very small - but present - chance for error. While this error is not a problem as the script has error-correction (the script will not get stuck no matter what state the Sudoku is in!), this may slow you down based on your latency. Try out different speed settings and see what works best for you! To ensure maximum efficiency, I would highly recommend enabling the 'Esc closes current interface' box in the Keybindings menu: The script uses the OSBot web-walking system. While it has proven very reliable, there are naturally some areas for which the web-walker may struggle. Prior to starting the script, I would recommend manually navigating your player to Ali Morrisane, who can be found here: Script Trials: I believe that trying a script before buying is paramount, however due to the high profitability that this script provides I am limiting the one-time trials to 12 hours in duration. If you're interested in a trial, please follow the instructions on my trials thread which can be found here. Progress reports: Updates: Development process:1 point
-
1 point
-
Will be adding universal support for Coal bag across all my scripts ^^ As for edgeville furnace + ore, please confirm which ore, I will test. Also make sure to use non-bank tabs if using mirror, mirror doesn't like bank tabs + placeholders too. EDIT: New Update (v30) - Adjusted cannonball profit counter - Cannonball interface now handled quicker, uses shortcuts too Update will automatically go live within 24 hours, good luck guys Almost done with coal bag update1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
only 2 more quests to run and ive done em all, this script is seriously beautiful and if we can wish for quests, id say fremmenik trials, then this sexy script could do all quests for zerker pures!1 point
-
1 point
-
@Token, Did MM1. Worked great, a few times got confused at my bank but the log and errors are really easy to read and take corrective action on. Thank you! MM2 when?1 point
-
There is an overarching problem with the way you are designing the script. It isnt mean to go down through the code and execute everything in order. This is how you have it: if (condition) do this if (condition) do this If both conditions result to true, then both actions are performed. IT should, instead, only evaluate one condition to true and perform one action per every time the script loops. This of onLoop as what you want to do in one moment of time based on environmental values at that instance. you should instead do: if (condition) do this else if (condition) do this for example: if (bank is not open) open bank else if (bank is open) deposit logs The first iteration of the loop. the bank is not open. So you open the bank. The next iteration, the bank is open. So you deposit the logs. Inside of each if statement, you can put more if statements to check more conditions, but try to only ever execute one action every time the script loops. After you get the hang of that, you can look into Events to contain certain actions, and execute 'mini onLoops' throughout the script. Edit: after looking at it more, I see that you arent completely ignoring else statements, but the banking function shouldn't be doing everything at once1 point
-
I think the import is: org.osbot.rs07.api.Walking Should be the same import as the standard walker uses.1 point
-
1 point
-
1 point