Leaderboard

Hello dear botters and script developers. We feel it's becoming time to announce that OSBot will begin officially transitioning over to the OSBot 2 platform along with commencing the start of the new SDN. Today's message is simply a reminder and fair warning to every script developer that the SDN will no longer be selling OSBot 1 scripts starting 2 weeks from now (aka June 16th)! What does that mean? Well if you paid for an OSBot 1 script, you will still be able to use it on either OSBot 1 natively (as the script was designed) or on the emulator which OSBot 2 provides. Transition Date: June 16th, 2014 For customers: If a script is deemed equivalent to your OSBot 1 script and added onto the OSBot 2 SDN, you will be granted access to the OSBot 2 version as well! If you paid for a script that does not renew ever (aka a lifetime script) and an OSBot 2 equivalent script is available, you will only have a free-trial of 30 days for the OSBot 2 version! You may decide freely whether to keep using OSBot 1 scripts for botting or the OSBot 2 equivalents. For script-developers: OSBot 1 scripts will no longer renew or be sold on our store! In order to keep your customers and status as a developer on the SDN, you will be required to convert your scripts to the OSBot 2 platform and ensure their quality and standards. It does not take very long to convert scripts, OSBot 2's API is simply a little bit different with additional features. There is no reservations for certain scripts (i.e. AIO fighters, merchers, etc.). It's a free-for-all. Only the best scripts will be accepted for premium sales. Additionally, any script which is to be sold on the OSBot 2 SDN/Store will have to meet certain standards of quality and reliability. What to expect after OSBot 2 is released: We've been developing OSBot 2 for a long time now and we're close to getting a fully operational dynamic web-walker. OSBot 2.2.X will feature a bot scheduler which takes full advantage of web-walker API being written currently. Additionally, the API will be added so that developers may use web-walking in their scripts as well! The next generation scripts for OSBot will feature requirement logistics and starting points on the map. The built-in bot scheduler will allow you to load up an unlimited amount of compatible scripts concurrently and and allow the bot to transition between the loaded scripts freely and randomly based on certain probabilities and configurations done before-hand. This new style of automatic scheduling will allow your bots to behave more human-like during long periods of time by constantly having a pool of different available behaviors. How are we doing it?: Here in the development line we're creating tools which facilitate the analyzation of the game's maps and object spawns. Much of the logic behind the proposed web-walkers and bot schedulers is easily automated when data from the game is analyzed properly and efficiently. Conclusion: We want to start seeing lots of script submissions for the OSBot 2 SDN! OSBot 1 scripts will no longer be sold on June 16th. Newly added OSBot 2 scripts will replace our current repository with better, more reliable scripts! The OSBot 1 client will still be supported for several months and will be discontinued once the OSBot 2 repository is satisfactory! Thanks, Sincerely Laz and the OSBot Team!

This may probably the last batch of OSBot 1 scripts being released, so grab them while you can! ATFletcher by AlphaTeam dThieving by NKFletcher by @Nitrousek DNAIOFisher&Cooker by APA Yak Killer by @Apaec Extreme AIO Cooker @Divinity Man Killer by @Molly Well-Endowed Elder Druids by TheMadScientists Swizzbeat's Auto Quester by @Swizzbeat Precise Air Orbs by @Precise Thanks for your patience!

By the way scripters, instancing/selling tabs will be available on the OSBot 2 SDN. This means most scripts will be dirt cheap for one tab and relatively moderate in cost for gold farmers running many bots.

..well shit I thought the purpose of the emulator was so OSBot 1 scripts would still work? Why are you forcing OSBot 1 scripts to not be sold anymore? Counter logic. I hope you enjoy having 3 scripts on the SDN.

All this hate. 1) For those of your complaining about the API not working, @Eliot and I have basically coded a fully working AIO Fighter, and am about to release a beta for an AIO Miner. Yes, the interact methods are a bit weird, but it still works. 2) For those of you who have been complaining about things like ColorPicker throwing exceptions... don't access it in a static context. Don't use ColorPicker.isColorAt, use this.colorPicker.isColorAt (assuming this refers to your script which extends Script), otherwise you'll need some sort of reference. But the point is, you need to access it through the instance of color picker that's stored within Script. 3) What's this complaint about no incentives? That's the whole point of making scripts monthly paid, so that even if (and I highly doubt) your script has reached 100% saturation, you'll still get money. Also, @Swizzbeat, where did you hear that only 5% of users renew? That's only assuming the script is terrible, so users no longer want to use it... (not saying that your scripts are bad)

Well I thought today I would release some of my private collection of different classes/snippets hopefully help new writers learn a little bit, and to maybe see a rise in quality of scripts throughout this forum. For my fifth release is another great learning experience I undertook last month, creating a mouse movement algorithm using a bézier curve algorithm I created with the help of Google, a tutorial on here, and @Merccy & @Swizzbeat helping me understand how the mouse interacts with the canvas, how to send my own events to the canvas. The reason I'm releasing this is because of the rise in bans as of recent, and I feel mouse movement plays a significant role in bans, though some people doubt this. I have to admit I didn't always think this was true either, and like some that still don't believe, I thought of profiling mouse movements as completely impossible due too the extensive resources that it would take to profile each player, though I will post some quotes from respected members of RS Hacking community that completely changed my thoughts about this. (Posting in text to avoid subliminal advertisement) #1 #2 #3 Those excerpts from above are some of the better material I have found regarding bans, but there is much much more on the topic, just a matter of digging deep enough to find it! Though a mouse change alone won't completely remove the chances of a ban, it gives you a better chance of going undetected. Now lets get started! What does this actually do? Well simply make your mouse completely different, using a bézier curve algorithm I created using a framework Swizzbeat and Merccy supplied me with. The final result, should look somewhat like this: Though this could be highly improved upon, it is a huge improvement to the default, and there are also other mouse controllers such as the SRL Mouse and WindMouse which are available on Google, just may require some porting over. How does is work? Well when creating this instead of starting by looking through RS examples, I instead went and study the math behind bézier curves, to find out they were quite simple to grasp. Then after seeing a idea for a mouse controller posted that I thought would be suited perfect for my use, I decided to replicate it. This is the basic guideline I followed when creating this. Finally, how the hell do I use this?: Well even though I took out most of the work, it still takes some on your side, just mostly copy/pasting, thought I recommend that you edit this mouse algorithm because the more similar patterns the more chances of you being detected. Well this tutorial will partially coincide with @Merccy's tutorial on Creating your own Mouse Controller, though I have made edits and extended some other areas he did not. First off we need to create a interface which we can use later to create new mouse algorithms easily and making changing them a snap. In Merccy's tutorial he creates a MouseController class which handles moveMouse and moveMouseTo methods, though this is also where we assign our new MouseController as well. We are adding this class becasue it seems that Merccy didn't mention it, though we need a class that can send our new mouse events to the canvas to have it move the mouse. Now we Object hold this new mouse we created, so for this I created ModMouse, which basically reflects and sets our mouse controller to replace the original. This is similar to Merccy's though we also set our MouseEvent as well. Finally we have everything we need to set use our own mouse algorithm, but we need a Mouse algorithm to use it! I named this NotoriousMouse purely to change the name other a Mouse controller sent by Swizz beat, which I then ripped all the internals out and rewrote using the new found knowledge I learned while studying bézier curves! This may not be the best, but it's a big step up! So we have all these files ready to go, and you should have something looking like this: For the hardest part of all is implementing it, please pay attention as this may be difficult for some to understand. @Override public void onStart() { new ModMouse(this); } Done. If you manage to follow all the directions and copy/pasted everything just right you should have a whole new mouse in your script! You now are on the road to having a more diverse mouse controller, though please be warned this is only for OSBot1, I have already tried implementing this into OSBot2 but the mouse methods are now declared as final and are no longer able to be overridden (If there's another way please let me know). I really hope you enjoyed the read, and I hope it helps all of you! I would post my sources and references but I withheld from doing so in fear of ban due to accidentally advertising, though I'm sure could be found with someone interested in the subject. Questions/Comments?: If you see anything I messed up on, or should be improved, please let me know, but be respectful about it, we have too many keyboard warriors thinking their hot shit, yet do nothing but bash others and never give any useful resources. Even if you have a question, free to ask me, just please refrain from asking me blatant obvious questions, or ones you did little to no research on before asking, I'm not here to spoon feed you, though I am willing to help someone is trying.

Please, elaborate. Your wisdom will not fall on deaf ears.

This. Script writers are dissatisfied because of the lack of strong financial incentives (the ability to resell a ported OSB1 script as a new product would have been beneficial to everyone including the customer, if you want me to expand on this I gladly will). On top of the financial dissatisfaction they would get penalized by you because they refuse to upgrade all their products for free. Customers will be dissatisfied because their scripts won't be working anymore even though you promised them they would.(most premium script writers won't update their scripts if there's no financial incentive, you can threaten us with demotions as much as you want, low move by the way) I'm not saying none of the script writers will update their scripts (matter of fact I ported 2 out of my 3 scripts already), but the ones getting one sale per week because they reached 99% of their target market just won't bother. Your strategy is disappointing, I wish you would have discussed this with the community and script writers. There were numerous threads full of suggestions and questions in the script dev forum yet you chose to ignore those, I can't say I'm surprised about that. I'm absolutely grateful and have a lot of respect for your work on the bot but the lack of communication and proper business management is seriously starting to irritate me. Respectfully False: (quote by Laz)

So much drama but i think both sides have valid arguments. A compromise will have to be found imo. But once again: Will scripters be penalized if they don't update their scripts? I don't have the time right now to do such thing ( great release date on this btw... in the middle of exams for 3/4 of the community -.-)

i noticed some great cpu change on osbot 2..

"There is no reservations for certain scripts (i.e. AIO fighters, merchers, etc.). It's a free-for-all. Only the best scripts will be accepted for premium sales. Additionally, any script which is to be sold on the OSBot 2 SDN/Store will have to meet certain standards of quality and reliability." If I understood correctly, I have the right to release a Staker script in this case? I find this to be a fair rule as it allows everyone to have an equal chance of succeeding. Thank you.

From my experience is because of how detectable the client is, makes people like me not want to invest in scripts anymore

The OP was poorly worded, so I don't think anyone besides the developers even know what's going on, but in overall it seems that were going to have to rewrite our scripts for free. Even if they just get it for 30 days that's still a free month of access to our scripts and only like 5% of buyers actually renew a script. Don't quote me if the topic doesn't even concern you. Just manage the forum big boy.

As cool as map data is, it is still gonna take months of interaction between us and you guys to tweak out unsafe/bad paths since there are no set way-points. I know I speak for many developers when I say priority should be bug fixes rather new features. Current bugs make it hard for us to test scripts. *Interaction - Most of us can overcome this by making our own method. *Walking in bad regions - same as above *randoms - We can't test the scripts for hours of time, some of them don't work right. *antiban - it is too intrusive and unregister does not seem to work it also messes up random events. for example: it tries to open inventory when one isnt present or does something and closes an interface that a random needs to function. *canreach *random mouse spasms *errors that require a restart such as ERROR][05/30 08:31:31 PM]: Uncaught exception! java.lang.IllegalMonitorStateException at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(Unknown Source) [ERROR][05/30 08:31:31 PM]: Uncaught exception! java.lang.IllegalMonitorStateException at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(Unknown Source) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(Unknown Source) at java.util.concurrent.locks.ReentrantLock.unlock(Unknown Source) at java.util.concurrent.LinkedBlockingQueue.take(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

They can be emulated but we don't want to sell unstable software. Scripts can be converted easily so it shouldn't be an issue to the script developers, especially if they're being paid.

Would be nice if devs hooked the mouse recording flag field. Because the code has obviously been there for ages, but we have no idea if it ever used..

Porn website

Arctic's SOCKS 5 Proxy Store If you are looking for cheap proxies look elsewhere, these proxies are extremely fast and have quite low down time! Package Pricing (Monthly) 1 Proxy - 4.8M 07 GP each. 5 Proxies - 18M 07 GP (3.6M 07 GP each). 10 Proxies - 30M 07 GP (3M 07 GP each). It is advised you allocate one proxy per account to minimise the risk of chain bans. Terms of Service - If the Proxies are down for over 48 hours then you will be reimbursed for the remaining amount of time you purchased. - You can not use the proxies for Torrents, mailing, fraud, abuse and illegal activities. - I will be available for any technical assistance from 6-11PM Australian Eastern Standard Time. - Delivery of Proxy information will take typically between 0-12 hours after me placing the purchase. - Please allow me up to 24 hours to deliver your purchase, after that I can refund the order if I have failed to deliver. - No refunds will be given simply because you changed your mind, either during the delivery waiting period or during the life of the proxy. To purchase Proxies from me simply contact me by click the add Skype button below! Interested in buying OSBot store Vouchers? Click Here! Want to buy LoL/XBL/PSN/WoW/Steam/iTunes products? Click here!

Is it safe to call BBB a scam now? Anyone have an idea of what really happened? Joopi is trying to host a new site and iZinc says Joopi was the scammer, which I am believe cause he is hosting a new site...

You really think that the TOS is followed? Refer to this thread: http://osbot.org/forum/topic/51972-age-of-osbot/ If we were to strictly enforce the TOS 60% of the community would cease to exist on this website. You can't just choose which part of the TOS you want to enforce, you (the staff) should be enforcing all of it. And it would not be a lose - lose situation, if the developer would not want to update his script he would be losing out on the money that he could potentially be making. Where as the user of the OSBot 1 script would have to lose either way, either he re-buys the script or he doesn't buy the script at all and gets a broken script because it wont be udpated. We can make it a win-win situation by giving the people who have already purchased it access to it, and a win situation for the developer by earning a monthly fee from new customers. I think by upgrading to OSBot 2 it will keep us ahead of the competition, which will bring plenty of new users to OSBot.

Ye, u paid for a lifetime of OSBot 1 and that's what you'll get. Just be glad that you're not having to pay the initial fee as well like many of the scripters here are proposing.

LMFAO I remember that thing. I begged my mom to buy for me when i was young. Turned out to be shit, i already knew everything in the book -.-

These are all my entries . 7 entries highest to lowest. 1. http://i61.tinypic.com/zwdmxy.png 2. http://i57.tinypic.com/jrw405.png 3. http://i58.tinypic.com/16k9zcj.png 4. http://i62.tinypic.com/fxcmeu.png 5. http://i61.tinypic.com/qz0oeg.png 6. http://i57.tinypic.com/j64f0y.jpg 7. http://i57.tinypic.com/ixqrvd.png

Not sure what the need is for a new api/bot, imo woulda just been better and easier for all to update the current bot. either way, we'll see what happens.

I don't think that using this transition as a way to re-sell our current scripts as a whole new product is great n'or strategic. I think that idea is quite selfish and money-whorish TBH.

Overall it does, but as for the section you're attempting to come into you know nothing about.

This script will be released this weekend. There are probably things I have to change to make it even more user friendly, but currently there are just a few things you have to have in the back of your mind when you are creating scripts with this script. 1. When you add conditions to a bundle, ALL of the conditions you add have to be met for the actions to be executed (The script will execute these actions cronologicly). 2. If you want to create a script that for example alchs, you dont need to add any conditions only actions, because the script will always execute the bundle if there are no conditions attached to it. 3. If you want to make an advanced script, split the script up into pieces. E.g: If you want to make a druid killer. Make a seperate bundle for walking to druids, walking to bank, attacking, loot and eating. This way the script will be very stable and very safe. (Please note that if you split the script this much, you must make sure that they dont have conditions that overlap eachother (E.g you must make the script attack NPCs only if there are no loots available, then you must make the script loot only if there are loots available)

Ehh. #1. This week feels kinda dry.

This is bullshit. We have to rewrite/port our scripts so you can hand them out for free? Absolutely fucken not.

I have a problem now, as i said earlier in the scripters subforums i have no time to invest in scripting for another good month. I will not be able to convert/rewrite my current scripts as i just don't have the time (exams). Will this affect me? I hope not considering that when someone buys a script they pay for the current version and i feel i am not obliged to provide a script on the new osbot (if i could i would do it obviously but i really can't). TL:DR Will scripters be penalized if they don't transfer their current SDN scripts over?

Can't wait c: I'm ready for some change

Very interesting, +1.

good guy Notorious. Cares about community.

Nice read. I remember the windmouse created by Ben for SRL wich was quite amazing. I have already seen a similar code in pascal but I am gonna take a closer look at your new implentation that I bet will be teh shit. It was about time that someone started discussing about the obvious problem that the actual OSbot mouse represents. Most interesting post I have read on this forum since I joined.

nice work! very interesting read

We had it turned on it with 30 + people leaving and joining every hour it gets annoying.

Wow, this won't change anything.