Leaderboard
Popular Content
Showing content with the highest reputation on 03/05/15 in all areas
-
8 points
-
REQUIREMENTS: CPU: Dual core+ Operating System: Windows/Linux/OS X(MAC) Java: At least java 8 VIP, Sponsor, Scripter or Staff rank NOT HAVING THE REQUIRED RANK WILL NOT LET YOU START IT! HOW TO USE: Start runescape client on your browser or the official OSRS launcher Open new bot tab on OSBot and select to use mirror client Make sure you are not logged in before starting your script. Preferably with a freshly loaded OSRS client. And continue like you are used to! HOW TO REPORT BUGS: Reports missing the following will get ignored and deleted: Mirror client version Console output / terminal output Crash report if a crash occurred Script that you ran Hooks that failed JVM/Browser bit version (32 / 64) Known bugs & suggested/required fixes: Scripts are not starting/buggy: Please attach to rs client right after it loads BEFORE logging in.7 points
-
Dear community, We are happy to announce the release of the Mirror Client technology written by @MGI. You can read about the Mirror Client here: Article on Mirror Client and ban rates. This feature will be available for VIP, staff and scripters. You can read how to use it here: OSBot Mirror Client Guide Also there were various little patches regarding widgets in this update. NOTE: Do not post errors related to the Mirror Client here but post in the designated forum section here: Mirror Client Bug Report Section Make sure you read the rules here: Article on Mirror Client and ban rates. Sincerely, The OSBot team4 points
-
4 points
-
Dear community, With the new widget system affecting a large area of our code it was inevitable there would occur performance issues. I have profiled the bot and applied a first set of optimisations. I know there are more optimisations to be done on the new system, but this should already make a big difference. Scripts might spike a little cpu usage on start up when the system caches some data. If you still experience issues with performance, please report in detail so I can investigate and optimise further. Your help is appreciated. I will upload the javadocs shortly after. Sincerely, The OSBot team Edit: API java docs have been updated. A packaged version of the docs to use in your IDE's can be found here: https://osbot.org/api/javadocs.zip4 points
-
4 points
-
4 points
-
I can verify that simply updating the banking/inventory from script.getBanking/script.getInventory to script.widgets.getBanking/script.widgets.getInventory will work fine. I have changed Omega script over to use the new methods and it seems to be running just fine now. ^_^3 points
-
Go ahead and do what you what I can't stop you from doing. We are doing necessary maintenance that all scripters were aware of ahead of time. I have spent 36 hours straight in mitigation of the issues that occurred as I couldn't foresee all of them with over a 100 classes changed, partially rewritten in an effort to not break scripts. The other option was to just not try port the old to the new system and force all the scripts to be broken and wait for the script writers to update. Customer is always important, but don't take it too far calling bullshit. This is not a help thread. Please post in the correct section of the forums with programming related questions.3 points
-
I lost my main to the banhammer about a year ago... Never bot a main. After about a year long hiatus, I think I'm finally ready to get back to Runescape. I really like this community, I did miss it being apart of it for so long. Looking forward to talking to you guys again. Cheers!2 points
-
This does not make you invincible, so please don't think that you are. This just gets around one banning system that JaGeX has placed which is the client detection.2 points
-
Dear community, This update contains further patches to the port between the old and the new interface system. I would like to point out that we should all encourage scripters to update their scripts to the new system. We are doing our best to make sure the old system will work as it used to however in some cases we won't be able to do so. Also there is a temporary widget explorer available again. R stand for root, - is second level and -- is third level id. Any reports are welcome. Sincerely, The OSBot team2 points
-
That doesn't matter at all, both instances of bank are the same. widgets is an API instance like all other API instance containing references to other API instances. Major change should be RS2Interface/RS2InterfaceChild -> RS2Widget && MethodProvider.interface.blabla -> MethodProvider.widgets.blabla2 points
-
So, if you buy a broken iPhone and pay for your dataplan for a month and the phone is broken for a week of those 30 days you're just supposed to be grateful about getting an ex-good phone? I'm paying, I don't need to be grateful and he gets paid, quit acting like he's doing us all a favour. With that being said, scripts are working now (guessing .37 fixed it), thanks for the quickfix!2 points
-
2 points
-
2 points
-
Thanks guys, but if I get banned for no reason, then so be it. Maldesto is the Community Manager.2 points
-
"With the new widget system affecting a large area of our code it was inevitable there would occur be performance issues" 10/10 would read again, amazing!2 points
-
Dear community, In this release a bug with banking that Mysteryy pointed out to me was fixed. It's regarding the issue where you withdraw multiple items consecutively it would fail after 3 or 4 items. This should be fixed now. Please report any bugs with a proper report in detail and we will review them. Sincerely, The OSBot team P.S. My internet is shit atm so the upload was corrupted. Please wait a couple of minutes and redownload the jar from the main page. P.S.S. Second attempt my internet did not fail. Download should work now.2 points
-
Dear community, This update took a while to round up. We have introduced a new interface system that gives full and correct access to all interfaces. We have called its class RS2Widget and its API can be accessed through the Script.widgets instance. The old system points to the new system and I hope we didn't break any scripts in the transformation, porting this wasn't easy as there are some major differences between the two systems. I can't say for sure that it has not broken any scripts. Never the less, the scripters will have to upgrade their scripts to use the new widget system, regardless of the fact whether this update affected their scripts. This update affected a rather large part of the client. It is possible that scripts using the old interface system possibly face problems. However the entire internal API is now mostly based on the new widget system. What is left of the interface system will get removed once there are no dependencies on the old system anymore in scripts on the SDN. Scripts that are broken by this update should be updated rather quickly as all developers have been notified of this update to come. I have also addressed the issues with banking. I haven't been able to reproduce any of the mentioned problems. However like I said, the scope of this release is so big that it is hard to say if we've missed something in the porting of the old interface system. So please report any bugs you come across with a detailed description of the bug and I will review them tomorrow. If everything is fine, I will rewrite the interface debugger to be useful again. This will most likely happen tomorrow or the day after. I will upload and update the javadocs af fast as possible for the script developers. I hope that you as a community understand that this might cause problems with certain scripts and I'm sure the script developers will update their scripts to the new system as soon as possible if this update affected their scripts. In that case we are sorry for your inconvenience. Sincerely, The OSBot team2 points
-
naaa http://osbot.org/forum/topic/66535-macrosuite-the-ultimate-private-script-environment/ is literally Superscript 20152 points
-
Congratulations, you just advanced a No Life level. Your No Life level is now 10 Click here to continue2 points
-
2 points
-
Makes no sense. Didn't know I can be banned from a bullshit claim. Sad.2 points
-
Since last semester ended, I have been working on a little project for a couple of weeks to learn and have some fun. I didnt actually intend to add it to the osbot client, I just started it as a separate project. Yesterday I decided I would add it on to the client for fun. Basically I wrote a server application in java, its hosted on a remote host. Anyone who has the client application can connect to the server. This is just a beta stage still, but its coming along nicely (in my opinion). It will keep track of online users etc. When you type '/online' it will print out a list of online users, as you can see in that image. It just pulls your username from the osb client and logs you on to the chat as that user. Current commands: '/online' - Prints the current online users. '/clear' - Clears all of the previous chat history from your client. What do you guys think? Would this be cool to add on to the client/scripts, or would it just be annoying if it poped up? Of course there could be an option when you run the script to connect or not.1 point
-
1 point
-
1 point
-
I'm glad I read your post. Thanks for letting us know.1 point
-
1 point
-
1 point
-
1 point
-
Just got a 2 day ban. Pretty happy seeing as I got 70 Att, 81 Str and 70 Range from it1 point
-
1 point
-
Welcome mate hope you enjoy your stay and gl with the rebuild we have plenty of scripts that can allow you to make some gains, check the script list in the client and see what you fancy!1 point
-
inven.getItemInSlot(i).interact("Deposit-all") but changed it to : inven.interact("Deposit-All", inven.getItemInSlot(i).getId()); and it works1 point
-
1 point
-
Guys, the point is to get RID of interfaces. So get your scripts updated! In the meanwhile I'll be working my ass of to see if I can minimise damage by checking out bugs and see if I can make a quick fix for it.1 point
-
[ERROR][Bot #1][03/05 10:47:33 AM]: Error in script executor! java.lang.NullPointerException at org.osbot.rs07.api.Widgets.get(nj:204) at org.osbot.rs07.api.DepositBox.close(do:115) Getting this error while it tries to close the deposit box interface.1 point
-
You won't be able to load any version prior to 2.3.34 because the hooks were changed and are not compatible with those versions. Scripts that are broken by v2.3.34 and later will have to get patched by the script writers. They are aware of this and any scripts affected should get updated soon. If you're experiencing problems with scripts post on the script threads of the specific script and script developer.1 point
-
I recently got my lvl 122 main unbanned (a hacker who was buyin my acc got into it and fucked up my acc) recently got it back 2-3 days ago and made 70m bank staking from being cleaned1 point
-
Duuuuuuuuuuude.... wellcommee baaaahhhhhck! (in the turtle from your ava's voice) Jk I'm retarded I thought that was the nemo turtle now i look dumb1 point
-
1 point
-
Would be great if you could leave a real reply, instead of just looking to increase your post count.1 point
-
1 point
-
1 point
-
Was sleeping when you added me, I've accepted you now. 100m+ stock atm1 point