User

Who doesn't enjoy multitasking some fun when things are slow? I don't go here at all but I do often work and look through imgur at once.

Or if you don't want to be sacked.

All of these things can be done easily within Windows without the use of external applications though?

You should never use regex for parsing html. Use http://jsoup.org/ instead.

Chrome & IE11. Chrome has been really quite glitchy for me recently (failing to load pages while blaming my connection when it isn't, certain websites crashing often) so IE is a fallback. IE has really started becoming a bearable browser to use...

I have personally written my own *fairly* functional bot in the past, and have worked on a relatively popular one recently (started with a w *cough*), this is what you will need to learn to do and do: Learn about Java bytecode and muck around with the bytecode engineering library of your choice (BCEL=slow & easy to use, ASM=harder to use [very low level], but has great docs to learn or Javassist=haven't tried - plan to do so soon [btw if you're going to use Javassist, DO NOT USE EASYMODE]). Study the client you plan on writing your bot for (maybe start by downloading an RSPS and writing it for that - as a beginner having the source, not having beclouding techniques hindering you, and not having updates thrown at you, will be of considerable use). Look for patterns within the client you are writing your bot for (such as class layouts if appropriate [generally not], bytecode patterns) and start on your "updater" -> it's job is to analyse the client to identify classes, and the fields and methods within them). JBE and the source code of the client will be of considerable use here. Using the information you have gathered using the updater you have written, proceed to inject the client with mutators/accessors for the fields you have found & make the classes containing these fields implement an interface of yours with these mutators/accessors to make everything easier to work with. You should know what to do here when you get to it. ?? This little guide I've written for you is really unsophisticated but yeah. If you wish I can also link you to a website that will probably be of considerable use (PM me for a link as it is another forum). I'm a little drunk atm so I'll probably fix this tomorrow.

If this is implemented, I suggest that the required join date should be moved back a bit. Other than that triviality, I support this.. It seems a bit stupid that people can miss the deadline by a day and have no chance of obtaining the rank.

Swing is not going to be removed - it's a part of the JRE (therefore it is not up to the bot developers on whether it remains or not), and can safely run synchronously with JavaFX.... When OSBot 2 is released, you will be free to continue to use swing - but it sure will look ugly.

You clearly don't live in Australia. Besides, it's just plain bad to not send the file size in the header. I live in Sydney and I just downloaded the bot in like 5 seconds...

There used to be an IRC channel, but it was replaced with the current chat system - so I doubt they will go ahead and change it back.... and they don't really need to anyway - the current chat system is sufficient.

No - glow is annoying as hell. It should be restricted to staff only, if not removed completely. If you ask me, there are too many ranks on this website to begin with, and the Veteran rank is one that should be removed. Registering early is hardly an achievement.

Well you can call it from: System.gc();. But anyways, this is not always the problem; sometimes it is a thread never being closed or a rescoure type like Scanner class or Inputstreams that are never being closed.. System.gc() from what i recall doesn't deallocate the memory used by those objects, not to mention if they are storing things in large array lists (which they are...) Recursive classes will become an issue and have 5 class objects with Arrays that are 10000+ in length lol. The garbage collector will run regardless of whether or not you call System#gc. In fact, calling System#gc does not even guarantee the garbage collector will run at that given time - relying on this statement in your application is usually an indicator of bad code, and a bad programmer. The rest of your reply is not relevant to the thread - Failing to close a stream is trivial, and allocating a huge array, will simply be deallocated from memory when appropriate. Since no one has looked up what these actually do, I may as well tell you that all they do is indicate the operating system to move blocks of memory to your hard disk - something that will automatically occur when you're low on memory. This will incur a huge penalty when the memory is accessed again. These applications may be useful for detecting memory leaks, but are not particularly useful when accidentally creating a memory leak in Java is near impossible.

You guys do know that in Java there is a garbage collector that deallocates unused objects from memory automatically whenever necessary.. What you are all referring to as "memory leaks" are probably not so. As for the application/s suggested in this thread, you should probably do some research on how they actually work.. If anything, they are counter-productive.

I'd go with KFC / Burger King (called Hungry Jack's here) - I used to love Subway, but when I tried it again a few times recently, it just didn't taste as good as I remember. Big reason for Hungry Jack's would be the onion rings and free unlimited refills on drinks (fuck yeah). McDonalds is just bad (but cheap I guess).

More like "as seen in multiple tutorials in 2008". Really OP, you should transform this into something useful, like a toolkit. The code itself is rather novice-ish, so it should be a good challenge for you... The toolkit widgets would of course be standalone... I'm getting a bit ahead of myself here, but you could eventually bridge information dynamically obtained from the client to extent the capabilities of said widgets, and eventually transmute it into a macro.... Maybe make that a (very) long-term goal? There will be plenty of rewrites inbetween lol. TL;DR - Make into toolkit. No. You're missing the point. I just wanted something to play on and not worry about advertisments in the client ( I don't have members ) So you don't plan on working on the code at all, but you're asking for feedback? Seems pretty pointless to me. There are quite a few alternatives in which would have allowed you to play the game without advertisements, in which would have required much less time... Like just downloading one of the other thousands of OSRS loaders floating around the web?

More like "as seen in multiple tutorials in 2008". Really OP, you should transform this into something useful, like a toolkit. The code itself is rather novice-ish, so it should be a good challenge for you... The toolkit widgets would of course be standalone... I'm getting a bit ahead of myself here, but you could eventually bridge information dynamically obtained from the client to extent the capabilities of said widgets, and eventually transmute it into a macro.... Maybe make that a (very) long-term goal? There will be plenty of rewrites inbetween lol. TL;DR - Make into toolkit.

/* * Initializes Nagle's algorithm. */ socket.setTcpNoDelay(true); Disables Nagle's algorithm - it doesn't enable it as you've stated in the documentation. Maybe read up on things like this as you're writing the code? Or did you just C+P this from another RSPS? This kind of ties in with the statement below: Stop with the useless documentation - documenting what you write is great, sure, but documenting self-explanatory statements is just a waste of time. A random example of this, taken from the code you've written, is: /* * While the application is active the thread will be cycled. */ while (isRunning) { Also, you really need to keep consistent in your style. For example, half the time you appear to be using 4 spaces, and half the time a hard TAB. It's a good idea to stick to 4 spaces - as the TAB character may be 4, 8, or anything really, spaces, depending on the environment. Also, the game runs on a 600 millisecond cycle, not a 500 millisecond one. Were you referencing a server from 2005 or something? Good luck with the server, btw - there isn't really much to look at, at the moment, though, so pointing out problems is a little difficult. Edit: This link may also prove useful to you.

I'm calling you out on this one... The company in which you have stated does not exist, the web site of the project your email is set to is unregistered, and the image in which you have posted of a 'model your team has made' is not yours.