Leaderboard

[CENTER][URL=http://osbot.org/forum/forum/188-superscript/][IMG]http://i.imgur.com/79xCn5X.png[/IMG][/URL][/CENTER] Avatar

Frames

Nice! rip a background, Add some abstract brushes. Then put osbot text on it. And recolour it with the hue/saturation tool. You're a true master!

I understand there's already a topic on this, I find it somewhat difficult to understand. Please understand that using breaks is an important part in keeping your account unbanned. More information on how to bot smart -> http://osbot.org/forum/topic/6894-bot-smart-what-it-is-how-to-do-it/ Defining the parts of a "break" [Average Interval] - The "average interval" is the average time between breaks. It's an "average" because of interval deviations, which i'll be getting to in a moment. This is how much time will be in between your breaks on average. [interval Deviation] - This is a very important part of making sure jagex doesn't notice a precise pattern in our breaks. Lets say your "average interval" is 75 minutes, and your "interval deviation" is 10 minutes. This means that the time between your breaks can be anywhere from 65 - 85 minutes. [Average Break Time] - The "average break time" is the average length of the breaks your account will be taking. It is an average, because there are also break deviations, which I will get to in a moment. Your "average break time" should be how long you want your account to stay logged off per break on average. [break Time Deviation] - Break time deviation is very similar to "interval deviation". Your "break time deviation" is how much the length of your accounts break can deviate from the average time. Lets say your "average break time" is 20 minutes and your "break time deviation" is 5 minutes. This means your accounts breaks will be anywhere from 15-25 minutes long. Here is a picture of my break setup Please be sure that you have the "enable breaks" box selected. Now, let me explain how breaks work going off of my break setup. My "average interval" is 75 minutes. my "interval deviation" is 25 minutes. This means that the time in between my accounts breaks can be anywhere from 50 - 100 minutes. my "average break time" is 25 minutes. My "break time deviation" is 10 minutes. This means that the length of my accounts breaks can be anywhere from 15 - 35 minutes. If you have any more questions, please feel free to ask below. Drop a like on the post if this helped you!

Dear community, I want to give you an idea where OSBot 2 is at. First of all I want to let you know that OSBot 2 is rewritten from the ground up to tackle some problems that you as a community pointed out. Things like CPU usage increasing over time in a scale of hours, something that never was a huge problem to most users but could be annoying for some. Besides that, increased overall performance is something everyone always likes to see. By writing an entire new core and taking time to do so, the client will score better at those points. At the moment, there is an abstract core written which is extendable for the most part to write implementations of other server revisions, such as RS3. Whether we will do so or not doesn't matter, it will be reusable. The entire GUI of the current OSBot was written using Swing. For OSBot 2 we are using JavaFX. JavaFX might not be as developed in certain areas as Swing, however those area's won't affect us. Besides that, JavaFX performs faster and gives more reliable output when it comes to exceptions. Not to mention, I personally and many others agree, I think that the look and feel of JavaFX is far better and promising than Swing. At the moment, a lot of the main GUI features are done. The client loads the applet, injects the client, hacks the canvas and such. So from here on, our first focus will be towards designing and organizing the new API. The API will have the same features as seen in the current OSBot and those features will be ported over. This is not a very hard job, most of it will just be refactoring. Other new features will remain secret and will be revealed as progress proceeds. Besides the API, which its functions will not have to be rewritten, we are planning and thinking about a second scripting engine. The current scripting engine is completely sequential in a blocking fashion. The new scripting engine, don't worry the old one won't disappear, we want to give a fully event driven asynchronous environment where you will dispatch tasks based on events and have control over the queue by using policies for tasks. We are looking forward writing this as Laz and I love writing new and fancy stuff. There are many other things that need to be done for OSBot 2, but the above is the majority. We can't give you an ETA, we don't want to stress any deadlines and instead focus on its quality. Laz has done a great job on it so far and now I'm joining him in this battle progress will speed up. I hope you had a fun read, Sincerely, OSBot.org

All the memories...

A few days ago Opinions?

Terms & Conditions Do not redistribute Do not remove watermark Download the pack here: http://www.sendspace.com/file/0klfpa

Too early for this IMO need more designers first

I support the section idea but I think that giving every graphic designer mod powers in the graphics section is going to cause trouble. Not every designer shares the same opinion, so their judgement is going to be different. I'm assuming the number of graphic designers will be more than 10. So all of them going over the same section will most likely cause conflicts to occur regularly simply because of the fact that there will be too many of them eventually, whereas appointing one or two graphic moderators would also make sure everything gets taken care of without any problems.

Very simple and professional, I love it.

Trying to make them universal with the themes. 1 2 3 Need some ideas!

im pretty sure thats a font.. @ text.

Up yo' game, bitch ********a. Let's safe it like a motherfucker: /** * @param on * The state the run will be set to * @return * <tt>Run is toggled off/on to our desire</tt> * @throws InterruptedException * Interactions were interrupted */ public boolean setRun(boolean on) throws InterruptedException { // Find out the current state of "run" int i = client.getConfig(173); // Declare a new RS2Interface variable for later RS2Interface j = null; // Check to see if the state is on and that's our desired outcome, or // vice versa if ((on && i == 1) || (!on && i == 0)) return true; // Successful state--even if no interactions were // needed. Return true. // Check to see if we "can't" open Setting's tab else if (!openTab(Tab.SETTINGS)) { // We can't, so that's a problem. throw new RuntimeException("Unable to open the Setting's tab!"); // Define the interface variable and check to see if it doesn't // exist or it does, but isn't valid. } else if ((j = client.getInterface(261)) == null || !j.isValid()) { // The interface is either null or invalid, so that's a problem throw new RuntimeException( "We're in Settings, but the interface isn't valid!?"); /* * Final selector state, assume: * 1. Our desired Run state isn't selected * 2. We're in the Setting's tab * 3. The "j" RS2Interface variable exists and is valid */ } else { // Assume that there's no client change, so the child "34" is valid and interact. /* * EDITED CODE (thanks Xavier): * This function WILL ONLY RETURN FALSE if we did NOT interact * with the 'run' toggle-button. This condition will determine * whether another recursive check is exhibited. * * Recurse through this entire method again. The next recursion * should end right at the first selector that checks the desired * state to the actual state. * * Use the same parameter as before */ return j.getChild(34).interact() && setRun(on); } } Without comments, yo': /** * @param on * The state the run will be set to * @return * <tt>Run is toggled off/on to our desire</tt> * @throws InterruptedException * Interactions were interrupted */ public boolean setRun(boolean on) throws InterruptedException { int i = client.getConfig(173); RS2Interface j = null; if ((on && i == 1) || (!on && i == 0)) return true; else if (!openTab(Tab.SETTINGS)) { throw new RuntimeException("Unable to open the Setting's tab!"); } else if ((j = client.getInterface(261)) == null || !j.isValid()) { throw new RuntimeException( "We're in Settings, but the interface isn't valid!?"); } else { return j.getChild(34).interact() && setRun(on); } } Xavier caught a flaw in my first code-post, so I've updated them. The problem being: The old bool method wouldn't have returned false at any point, but rather; return true or throw exceptions. Good catch, Xavier. Hat's off to you, good sir.

Support?

Looks good. Would make a great avatar.

Love it bro, definitely gonna use this. Great addition

Nice icons I found that can come in handy. Link: Edit:Previews Thanks, MD

Well of course some sort of thread will be made to recognize the designer that was picked for that certain job. But we don't want people who KNOW NOTHING about gfx to vote on something that will be official. I suppose not however picking something that 'looks good' doesn't really require skill (if that's what's being looked for in the Graphic piece). Have you seen what people vote for in the SOTW's?

Fuck her onions, they're shit, fucking fuck.

if(script.client.getMyPlayer()!=null && !script.isRunning() ) script.setRunning(true);

Denying the community an element of security is not justified by your lust for superiority. I know you're new here, so I'll be easy on you bud. SINCE WHEN DOES BUYING A RANK MAKE YOU TRUSTED?

That won't work, since it can be bypassed easily. It also has some privacy issues. Sorry, but this just won't work.

Add some failsafes to that.

You know it will keep trying to do this if you reloop it xD? Better to use configs imo.

I feel you Those were the times, when you didn't play for money, you played for fun.

And then the frog got even more lost and eaten by a snake and since frogs are stupid as shit the mommy frog did not notice her missing baby and her baby proceeded to being wounded by the snake then starved to death because he thought you were protecting were he got his food so he did not dare go near. The baby frog died a painful death #pesimist

well i finished it and decided to share because I'm nice took like 20 mins to write this shit down!!! enum Spells { HomeTeleport("Lunar Home Teleport", 0, 16), BakePie("Bake Pie", 65, 15), CurePlant("Cure Plant", 66, 31), MonsterExamine("Monster Examine", 66, 6), NpcContact("NPC Contact", 67, 4), CureOther("Cure Other", 68, 1), Humidify("Humidify", 68, 7), MoonClanTeleport("Moonclan Teleport", 69,20), TeleGroupMoonclan("Tele Group Moonclan", 70, 32), CureMe("Cure Me", 71, 23), HunterKit("Hunter Kit", 71, 8), WaterbirthTeleport("Waterbirth Teleport", 72, 24), TeleGroupWaterbirth("Tele Group Waterbirth",73,33), CureGroup("Cure Group",74,3), StatSpy("Stat Spy",75,9), BarbarianTeleport("Barbarian Teleport",75,0), TeleGroupBarbarian("Tele Group Barbarian",76,34), SuperglassMake("Superglass Make",77,25), KhazardTeleport("Khazard Teleport",78,18), TeleGroupKhazard("Tele Group Khazard",79,35), Dream("Dream",79,10), StringJewellery("String Jewellery",80,22), StatRestorePotShare("Stat Restore Pot Share",81,27), MagicImbue("Magic Imbue",82,13), FertileSoil("Fertile Soil",83,2), BoostPotionShare("Boost Potion Share",84,26), FishingGuildTeleport("Fishing Guild Teleport",85,17), TeleGroupFishingGuild("Tele Group Fishing Guild",86,36), PlankMake("Plank Make",86,11), CatherbyTeleport("Catherby Teleport",87,21), TeleGroupCatherby("Tele Group Catherby",88,37), IcePlateauTeleport("Ice Plateau Teleport",89,28), TeleGroupIcePlateau("Tele Group Ice Plateau",90,38), EnergyTransfer("Energy Transfer",91,5), HealOther("Heal Other",92,29), VengeanceOther("Vengance Other",93,19), Vengance("Vengance",94,14), HealGroup("Heal Group",95,30), SpellbookSwap("Spellbook Swap",96,12); private final int level; private final int childid; private final String name; Spells(String name, int level, int childid) { this.name = name; this.level = level; this.childid = childid; } public String getName() { return name; } public int getLevel() { return level; } public int getChild() { return childid; } public int getParent() { return 430; } }

Hello community. Today I'ed like to finally announce what our development team has been planning on for some time now. When we first started developing OSBot from the ground up, our development team had to rush much of the code that OSBot uses now. Part of the reason why is because we started development two full weeks after 07scape was already released. This meant we gave everyone a 2 week head-start. We had A LOT of competition, more so than we do now. We knew if we had any chance of being successful, we needed to release a working bot with a simple but robust API. Maxi and I would stay up at night for hours straight programming the bot from a day to day basis. We spent hours on Skype developing and planning everything together. We knew that we weren't the first 07 bot out there but we also knew all the 07 bots out there were primitive and undependable. Eventually the bot you use today was released and we've been working hard ever since to keep it up to date and enhance it. We've learned a lot from OSBot. We've gained a lot of experience and we're now ready to announce that we're going to rebuild OSBot from the ground up again, but this time with the experience and knowledge we've gained. Here's a list of goals that we want OSBot 2 to have reached before its release... A new and fresh JavaFX based GUI. Lower CPU and memory usages. A brand new, smart and simple API. Better API documentation. A smaller jar-file size. An advance web-walking/resource-walking system using smart and efficient algorithms. Automatic random event updates from our bot network without the need to re-download OSBot. Support for an integrated RS3 bot on the same platform. Offline support for when our servers become unreachable. OSBot 2 has no ETA at the moment. We will continue to provide full support for OSBot 1. Sincerely, the OSBot Team. Yes, however as stated in the OP, long-term support for OSBot 1 will still be available after the release of OSBot 2. The ability for OSBot 2 to handle OSBot 1 scripts has been considered as well. I've had plenty of time. I'm getting really irritated with all these script developers thinking I don't have enough time or that we're stealing money. We've paid script developers before, we will keep paying them. This is a legal buisness, not an illegal operation. This website's income is taxed and has to go through a process before it falls into the hands of script developers. That takes time. This reply is simply intended for you only, it's for everyone. Simply because I do not reply to the thread within minutes does not mean anything disturbing. I hope that most of your concerns were answered with the previous reply. As for web-walking, we've dumped data from about 1.3K map regions in RuneScape which is about 90% of the world map. We will be using this data with a combination of efficient algorithms to make web-walking fully automated and dynamic. It has not been fully planned however our development team has discussed the various options and we believe the right one will be written for OSBot 2. More info on web walking will be released as more development arises. Also, for those concerned that OSBot will support RS3. RS3 support will not be released right away. OSBot 2 will be designed in a way that an RS3 bot could be integrated. This does not mean that we are not focusing on 07. 07scape will come first. RS3 support will be a special update scheduled for OSBot 2.