Leaderboard

Script writers love it when you help them find errors in their script. But the usual Doesn't really help well... There is a way to get the full error so you can see exactly where the problem in the script is. As you can see on the screenshot above I can see exactly what and where in the script causes the error. This is way more useful and it would be great if more people used this. How does it work: Open a notepad and type the following text: "C:\Program Files\Java\jdk1.7.0_07\bin\java.exe" -jar osbot_1.4.5.jar -dev Change the directory to your JDK version and change the 'osbot_1.4.5.jar' to the osbot.jar file you downloaded from OSBot's website. Make sure there aren't any spaces in the name because that won't allow it to work. After you found the corrent directory and changed the name of the osbot.jar file to yours SAVE THE FILE AS... run.bat and make sure to select all files(*): After you named it, save it or place it in the same folder as your osbot.jar file

Current version: 2.7.01 Working OsBot revisions 1.7.X NOTE: COMPLETELY BROKEN ON CANNONBALLS, GOLD AMULETS, ROF IRON SMELTING! On another note, as some of you know I am making a complete overhaul on this script, for 3.0. (Or "Ultimate CronSmelter). Due to my exams I can't really finish this up in an efficient way, and altough 2.7.01 will work for you, it will contain bugs that are not going to kill the script, but are annoying to say the least (in a programmer perspective that is). Expect 3.0, which will be a completely new script from scratch, with exactly the same functions, and a couple of new ones I won't tell you for the sake of curiousity within 2 weeks. The version that is currently is being updated for your use will remain updated untill 3.0 is done. PLEASE understand that updates are made when I can afford to cut in my study times. Anyway, for the following updates I made sure CronSmelter will be runnable for atleast 1-2 updates on the current 2.7.01 version. 3.0 has a focus on efficienty and reliability, for me to update the script more easily, and to get the most of the script in general. For people wondering: Yes, 3.0 will be commited to the SDN. And no, it will not become a paid script at all! It will remain free for as long as OsBot exists. Why? This script was my very first big project script, which I found very entertaining and educative at the same time, and it would be selfish to charge you money for it. I hope you understand my situation Changelog Features: * Easy to use GUI * A paint (By DarkzSide) * Supports Bronze, Iron, Steel, Mithril, Addy, Rune * Cannonball support * Ring of forging support * Option to make gold amulets from goldbars * Support for Al Kharid + Port Phasmatys * Auto detects required ore for bar smelt * Walking, banking, smelting (Fast & efficient) * Failsafed *Antiban: Random mouse + camera movements * Handles closed doors 100% To come: * Superheating * More antiban * Support for making versatile jewellery Known bugs: Ring of forging is completely bugged! Progress reports: Source code untill 1.7: Articron's Github After 1.7 the source code is no longer shared. Download Link: https://dl.dropboxusercontent.com/u/9385659/CronSmelter.jar A like keeps me going! Credits Articron - Script Writer DarkZSide - Paint maker Krulvis - Hex value for interface GoldenGates - Method P/H Medic - let me use his account for adding cannonball support LiamBaby - initial Paint maker Toadflax - Made secondary paint Apple - Made secondary paint

OSFletcher - by Daniel Current Version: 3.0 (06/21) - Supports OSBOT 1.7.X Price: FREE Status: Running perfectly Feel free to donate to me if you love this script. Welcome to OS Fletcher! This script supports all type of bow fletching, from regular shortbows, to magic longbows. This script will run for hours on end with no glitches or problems. To use, simply add OSFletcher to your scripts on the store and run it from your remote free scripts on OSBot 1.6.x. If not running on 1.6.x, download the jar file at the end of the post, add it to your script folder (no unzipping or copying/pasting necessary) and run the bot from any bank in Runescape! - I would suggest running it in the Pest Control bank, however, since there are no randoms. Have fun and enjoy the script! Remember to leave an progress report! IF FLETCHING START WITH KNIFE IN INVENTORY. MAKE SURE YOU'RE ON THE LATEST OSBOT VERSION (1.4.2) Report any problems and I'll get on them ASAP. I can't stress this enough. I can't improve this script unless people explain errors with as much detail as possible. Update Log: V1.0: Release - Known issue with banking, bot failsafes and it works anyway though - just slows it down a bit. Will fix next release. V1.1: Fixed banking issues V1.2: Added a method to deal with leveling up V1.3: Stringing is now supported. V1.31 Theoretical fix for leveling up problem. Also switched from zip to jar. V1.32 Some bug fixes, stringing should be flawless now (with double clicks). V1.40 Fixed xp/hr on the paint and now continues on level up. V1.41 Fixed magic bows not fletching. V1.42 Really fixed magic bows. Also added a lot of speed improvements. V2.0 Support for OSBOT 1.4.1 added. Massive amounts more of xp/hr. Support for every bank booth added. Updated paint slightly too. V2.01 Fixed withdrawing bowstring issue. V2.02 Fixed level up on last log/bow. V2.10 Massive speed improvements on stringing. V2.20 Updated to support fletching regular shortbows and longbows. V2.21 Addressed banking issues. V2.30 Addressed more banking issues. V3.00 Completely re-coded, fixing banking and knife issues. (Bot currently says 2.0 not 3.0). Current problems: None To do: Add more anti-ban More sophisticated paint (will do on next bot update)

This is absurd. Everyday we're getting WAY too many people opening 'Services' such as Questing/Minigames/Levelling which is all fine as it's a service and is mutually beneficial to both parties. I try my best to help out every new service provider to start their business out but feel disgusted giving away a vouch(Which i'm very strict at giving) to a person who then goes and scam quits from here. Services should ONLY be allowed to be opened to people who pass a certain filter, for example; - Time of account creation - Post count (Even though this is easily bypassed with spamming so we need good control on that) - Profile 'Likes' (It's fairly easy to prevent people from farming profile likes) - Open a 'Service Opening' thread and then scanned through by a Moderator to then declares whether person is allowed to use or not via a badge. Etc. Etc. I know the 'Everyone must start somewhere' argument will spring up but if you're going to offer a service which might cost us our account security then you better be a trusted member. I really hope this passes through and i think it's better for both Clients and Service providers. Thanks

how are you supposed to improve if you don't know what you did wrong

nvm close :X