NotoriousPP

Ahh I already got cancer, so too late.... Also I got no respect for illiterate backwash like yourself. So mad? Why so serious?

Shit* I just said I don't care about you, doesn't mean I can't prove you wrong.

1. You look at images, not watch them, it's not a movie. 2. I still don't understand what the fuck your on about. 3. I don't care about you either. So what the fuck are you doing?

I completely failed to see your point. I'm still selling just as much as before, so what has changed, besides the updated client, and you* bitching?

Your speaking from a bias perspective, because your fellow users do not seem to feel the same. I'm getting the same sales rate as before the switch, so once again the only things that have really changed, is more people are bitching than before, and we have a better client in the long run.

You put it in the microwave before you head off to take the test, and it comes with a heat pack that holds it at the perfect temperature for about a about a hour! It also comes with a sticker temperature gauge so you know where it at before using it!

Quick-Fix! Synthetic Urine! No joke use it! It works if you follow the instructions, even at labs, I know from experience. You can buy it at smoke shops usually for like $20.

No we are forced to use monthly model now for OS2 scripts, and the prices my scripts have are not what I submitted them as. Also the other client, you have to pay to use it, then buy scripts which prices are really no different than here, then to top the cake, some script are authed per account. A funny thing everyone seems to forget, every script you could ever want can be free; just go learn Java or enough API to get your shit done, and write it yourself, this is a open platform. If you complain about prices, then write it yourself, that's one of the main reasons I took up writing bots.

So I can't write a swamp tar script? You act like we don't have other scripts:

Hahaha did this kid seriously just say we make 400-800?!?!?! Haha I'm fucking lucky to make $50 in a week... GFTO with your shit.

Someone's mad.

Awesome! Also I don't think they were mentioned earlier, but I added some methods that may prove to be useful!!! My additions include: Identifiable (Subclass of Entity) now has: a) getActions[] returns String[] b) hasAction(String... action) returns boolean. ActionFilter was added, so you can filter out based on actions.

Holy shit man..... I'm soo sorry dude.... I tried posting the moment I saw that link to stop it! Just remember if you click a link outside of Jagex, and it asks you to login in, DON'T DO IT! Go to the official website and login in instead.

It was a phishing link! If you logged in using that link, you better hurry up and change your password, or GF you accounts and/or valuables!

Well it's your fault you don't want to believe the truth... Here's a link with Benchmark scores. Window 7's still has a better advantage over 8, so why downgrade to something when you can use the more stable, reliable, and better running Window's 7. Here's proof, if you don't want to take my word for it: http://kotaku.com/5935337/lets-see-how-windows-8-performs-against-windows-7 Go ahead and report for irrelevant content, just shows how much denial your in.

If your talking about the experience tracker, then this should work: @Override public void onStart() throws InterruptedException { experienceTracker.start(Skill.HERBLORE); } @Override public void onPaint(Graphics2D g) { g.drawString(experienceTracker.getGainedXPPerHour(Skill.HERBLORE), 300, 436); //Extra Method, Need timer to format long drawString(Timer.format(experienceTracker.getTimeToLevel(Skill.HERBLORE)), 381, 466); }

This kid above doesn't know how to, or just doesn't like to read. Instead of listening to someone who has no sourcing to back his claims up, and trying to make you believe me. If you really want to know about bans, read the quote I have below, it's a leaked comment from a Jagex employee, and you will see how much OSBot2 will really combat bans. unlimitedorb (Quoted, unknown original) Primitive programs typically recognize the object, but click the same spot (often the same pixel.) This immediately raises the alarm if it is done consistently. Most programs do not do this, though, but rather have an "area of uncertainty" where the click will randomly fall in. This is still easy to detect. There is accuracy, and precision. These programs do not replicate human precision. Consider the dartboard as an example: The goal is to simply "hit it." A human will still aim for the bullseye, to increase the chance of hitting the dartboard. Thus hits will be concentrated towards the bullseye, but there will still be hits nowhere close, and some misses too. A macro does not have human flaws, and can always hit the dartboard. However, if randomized in the "area of uncertainty" there is no such pattern." This will also raise the alarm. More advanced yet, some macros will actually form concentric regions of where the clicks will land. Still, we're always ahead of rulebreakers. Our final line of defense in this criteria is to analyze the regions most commonly clicked. A macro tends to click in a perfect square, circle, or sometimes the shape of an interface icon. Sometimes even the region is randomized. Human behavior is not truly random however. The region most commonly clicked is related to placement, which is all I know about this. Highly advanced bots have made an attempt to replicate even this, but we have not seen anything convincing yet. Admittedly, we're disadvantaged in this aspect, so we cannot fully rely on simple movement and accuracy to detect a macro program. The next criteria is the actual sequence of actions. A player that decides to cut some trees for logs, and sell them for profit actually has a longer list of actions to perform than you'd think. The efficiency of which this is completed can be analyzed, and much more easily compared to the behavior of a macro programs' attempt to replicate it. If each step is merely randomized with the same bounds of uncertainty like virtually all bots seem to do today, the actual time it takes to execute the actions in all converges to a specific value! It's similar to flipping a fair coin multiple times, and converging to a frequency of outcomes (namely 50%.) Humans are generally much less consistent, and once the consistency falls within a certain range, the alarm is raised. One more of many criteria is the effect of total gameplay time. As expected, exhaustion will set in for most players and slow down their actions. This is not a completely reliable method, since some players have been able to keep up their concentration for remarkably long periods of time." "The last criteria I really know of is probably the most obscure and advanced. Human players tend to have much better object recognition capabilities than a macro program, and the limitations of the procedure can be exploited. While a human may be able to recognize a tree at a very unusual and discrete angle, many macros lack this capability, and thus keep the camera angle within a certain range. Some fail to change it entirely. Macros tend to locate objects that are far out of reach by going close to the area in question, and then finding it. Normal players tend to look ahead first. There are probably many more techniques employed, and the genius and innovative capability of my coworkers is simply amazing. I am very confident in their ability to enforce the rules, and keep RS a fair, and equal environment. The detection system is definitely conducive to such, but that is not our only method. The next is abuse reports. There are many new and better bots, just written, that can avoid at a few of the criteria, and not be flagged. The intuition of a human being can never be surpassed, and abuse reports give us an all seeing eye that brought many rule breakers to justice. Abuse reports are also helpful for locating the archives, and comparing the new behavior of the new macro that was previously able to avoid detection. We can update accordingly. We highly encourage abuse reporting, and we will not punish players who send in reports with a reasonable cause to suspect the player in question is using a macro. Circumstances (such as the usual range of playing time) is taken into account as well.

Think about where that work was going to end up sooner or later? Playing RS is all wasted energy at some point. It's not like 20 years from now your going to say, thank god I still have my fire cape.

Yee! Two years if Varsity in HS. Hahaha I might of been sober, or in between peaks. ;) This was taken at a rave!

I'm the really tall kid in the back, my GF is the one on the left. P.S. I'm 6'7"

Working on my 48 hour proggy. No bans!

Dude if you never heard this; get ready, shit is heavy.

https://www.youtube.com/watch?v=O-ol9Xlyn2U Your welcome. Make sure to blare this loud enough for your neighbors, thank me later!

So whatever this GPU hog is, it seemed to be implemented around 2.1.10 release, I've checked OS1 1.8.9 and was running this: Also, had a consistent pattern until I hit 2.1.10, then: Something funky is happening here.