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!

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

The following are suggestions for the graphic designer rank, along with what they are, and why they should be supported. Graphic Designer Section - This would be only accessible to Graphic Designers and staff members. Staff can request work to be done in this section (Like PiPs, logo, etc) - The designers could all create their own version, and we pick the best one, or we can collaborate as designers and create one masterpiece Designers can share PSDs - In the past when a designer has gone inactive it has become impossible to get new pips. By sharing PSD's we as designers can all have access to making perfect PiPs in little to no time Collaborate - Designers and staff members can collaborate to find the best ways to improve artists, hold contents, and manage the graphic designers Sectional Moderators - Giving Graphic Designers very minimal and basic powers in the Graphic Section only [suggested by @Jinx] Powers to - Move, edit, soft delete and lock threads It is logical - Graphic designers know the way it should be used, and understand the graphic section. We know how to grow as artists, and can control and help the community.

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 nice work, it looks good, and that is all that really matters.

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.

Everyone needs to get it through there head he didn't post a rant, he just wanted to know when he's going to get paid, end of story. Only Maxi or Laz can answer that.

Support?

Nice job! Will be using it as my avatar from now on

If you could count, then maybe http://prntscr.com/1ygd0u http://prntscr.com/1ygd36

Love it bro, definitely gonna use this. Great addition

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?

nice, still not joining bigboibets though

Add some failsafes to that.

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

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

^^^^^ usual c4d idiot.Use adobe products. Photoshop, illustrator. Etc. Don't use cinema unless you're making models. You don't need text in your signatures. Look at my tags at www.ztrinity.deviantart.com I rarely use text. so butthurt. saying i just make a simple motext and adding them into a psd. LOLOL. Please stop. but that is what you do.... You use motext, or a template and then put it into someone elses photoshop file you downloaded from a "how to make idiotic c4d text" youtube video and used their filters. I see work like yours everywhere on no name youtube graphics "clans"

Appreciate the update.

Hello everyone, I have returned and I'm ready to contribute to our fire again. I'll be discussing with Laz to decide on our priorities again and I'll be working on some old work left behind when I was out of the country. Today I will be working on fixing up some scripts that require some attention. After that I will be writing an anti ban mechanism which hopefully will prevent many of the manual J Mod bans and possibly also the reports by P Mods. It will detect moderators in your environment and perform unpredictable behaviour, partially defined by you as a user, which should lower the suspicion. Goals we had before were obvious and they are still present, such as 'Hannibal', the first Titan to completely diminish the concept of web walking. Hannibal is a work in progress but will get a lot more attention now than it did before, simply because of the fact that there is room for attention now. Further automation of our administrative work is another goal which will happen behind the curtains, but most definitely very important for all of us. And we are brainstorming about a much easier way of adding scripts to the SDN, creating a web interface where you can submit everything that will create the Nexus store product, the repository module etc, leaving our only job to double check and confirm the entire product to be safe and working. All cool stuff And last but not least, we will be starting on a new little secret this month. What this is and how long it will take for us to show you publicly is not sure, but it has been us excited for sure. Sincerely, OSBot.org