Iamdan

So are you saying that process monitoring is not illegal? There is only one "pre-made code" and it is called SRL, it is just methods for a colour clicker made in pascal. Not VB or C++. No.... They are sweatshop workers. What are you going on about? The level 3's in default clothing are sweatshop workers. VAC works by detects changes to core system files, ([Caution: Executable File], .dll) not process monitoring. Since Runescape is a Java client, it cannot do the same thing. JaGeX already can detect client hacked macros with a reflection system. JaGeX cannot however, detect any programs running on a players computer.

Stupid idea and won't do anything to stop macroers. Firstly how is JaGeX supposed to stop macroers opening a program? Or even detect when somebody opens a program? It is illegal. Again this is illegal. JaGeX has no right to know what you do with your computer. Scares them? Good one. JaGeX can already detect client hacked bots on login, which is why most macroers use colour clickers or java bots using event hooks and injection with BCEL rather than editing the client. Anyone with any knowledge of Java knows how client hacked bots are running, and anybody with any kind common sense knows at least basically how colour clickers run. It won't stop them. Even if it wasn't illegal it isn't hard to change the process name of a program. They could change the process name of the macro to windows media player or something. I think you need to do a little more research.

Jagex does this already. Search for any files called uid.dat on your computer. It doesn't work because macroers can delete it regularly, or have separate uids that they use for macroing and playing on their main.

Guitar hero 2. Best game on ps2. IMO before it came out on 360 guitar hero was the only thing good about ps2.

Is it just me or was the third game terrible? Maybe it was just because we still won the series if we won the third game or not. Much less anticipation

If they run on a rotation of randoms, there are plenty of macroers willing to help make anti randoms. Want me to go to a few cheating communities and pull out a few numbers of registered members? ^^ That is a very public forum, has a lot of idiots but has a decent number of dedicated macroers too. ^^ That is a more private forum which now only lets in the best coders. Only about 100 of those 700 members are active. ^^ That is a forum which is dedicated to 1 specific colour clicker. As you can see there are many people who would help update macroers to solve these randoms, only happening 3 times a day won't be a problem for them. These reserves which will run out sooner or later will often be later rather than sooner, many of them have 50+ accounts on rotation and more are being made every day. The colour clickers are the ones that rarely get banned. They could still kill the bot, and solve the random manually (at the same time collecting data for the anti random) later. A lot won't, but a lot will. Sweatshop workers will be easy to detect, but the colour clickers won't be. If Jagex did have the resources at their disposal they would be using them. Perhaps they have something planned with the game engine update, I don't know because I haven't looked in the client or talked to anybody who has. Colour clickers can be made to read packets, (I think with bcel) but still not edit the client. (So Jagex cannot detect it) So the macro can be made to automatically know what to avoid doing.

It stands for death match. The rules are that you can't run away, and for god's sake take off caps lock.

Then Jagex will not do it, because they will run out of ideas. If they only do 15 or so and rotate them, then it will be no different to the other randoms - people will make anti randoms. We seem to be arguing about 2 different types of macros. I will specify which type and you do the same. For client hacked macros, (the type that multi-log) even if they all fail the random, they will not be banned any faster. Jagex has a reflection system which lets them know when somebody logs into a modified client. So when the account logs in, Jagex knows it is a macro - before the random hits. (In bugs and suggestions, see my thread entitled "Real way to stop macroers, won't affect game play" for more information.) In the case of a colour clicker, the type that runs on a rotation of accounts, the first account (the one logged in when the random occurs) will get banned when Jagex gets around to it - probably another week. The others will not log in because the bot is killed, so they are safe. The macroer will log in on each of them and solve the random manually, then they are safe for another week. As I said before, Jagex will already know the account is macroing in the case of a client hacked macro. In the case of a colour clicker, the account will get banned in a week or so when Jagex gets around to it and the rest are safe. It will take a matter of a couple seconds for the macro to realize it has the random, and inactivity for a couple seconds is not something to look for when detecting macroers. All they have to do is write down a few colours and co-ordinates, compare them to other cheaters and make the anti random. In the case of a client hacked macro, they just have to take down id's. Then just hand it out and get feedback and smooth out bugs. Anti random = done. Jagex can't keep track of every bank, it would take up way too much memory. The players in default clothing aren't macroers they are sweatshop workers, which also rules out the sub combat 20 check. Colour clicker macros (the ones which Jagex does not detect on login) do not concentrate on a couple skills, they generally level up everything evenly. That idea will not work either.

Yeah, for 60 seconds

No they wouldn't. Read my post.

This idea will not work. Google OCR for more information.

Then they will be even more simple and convenient for macroers. If jagex makes their randoms like that, they will have some sort of constant. EG: (10 items) "Which item is (odd one out/blue/square/on the left etc) Then a anti random is easy to make with case statements for each of the variables. It won't know when it will strike, but It will know once it has the random. You never said that before. Anyway, the macro would just force quit, then kill the bot. Then as I said before, the person would log in on each account and finish the random. The account macroing at the time of the random wouldn't get banned for a week or so, and the rest of them are safe. I have said this a few times on these forums, anything a player can do, a program can do better. The macro would use random waits so it would solve the random in around the same time as a human would. If they are being solved simultaneously, then they are multi logging on a client hacked macro. Jagex has a reflection system which lets them know when somebody logs into a modified client. So if the accounts all solve the random simultaniously, and chooses not to use random pauses and clicks etc, (which they will) the the account won't get banned any faster because Jagex already knows it is a macro because it is on a modified client. If they are not using a client hacked macro and are running on a rotation of accounts, then then the macro will have a lot of emphasis on undetectability. This includes different paths to do something, random waits, misclicks and rotations etc. Jagex won't see any similarities.

Just got my learners today, 1 day before the new laws come in.

Umm Think again. Most anti randoms are fairly easy to solve, especially with client hacked macros. Why wouldn't anybody make 15 random events? There are many versions of every random event in many languages made by many different people for the randoms we have currently, why not another 15? Even if nobody does make anti randoms, my first point stands. They will log off, then the person macroing just has to log in on each of them and solve the random, the macro for another week.

A large number of macroers buy membership off others with gp.

If the letters are too distorted then all the morons who play won't be able to do it. I searched CAPTCHA in Google images and I didn't see anything an OCR couldn't solve. An OCR could be made that separates each letter, removes the lines and reads the letter. At least one of the OCR's made in classic for the fatigue system did that.

Won't work. Google OCR

I'm not sure why you double posted, but that idea won't work. Simply because no matter what the random will be, there will be some sort of constant. Even if the constant is that the macro gets lost and It has no procedures to deal with what is happening. When this happens it will log out and switch to the next account. Once all the accounts are at the random and logged out, whoever is macroing will log in on each of them and do the random manually then continue to macro. Also, Jagex is going to run out of ideas for random events. You try and think of 52 unique random events. Anyway, Jagex wouldn't make a unique random for every week because of the work it will take.

Dane Cook and Ahkmal Sali

Don't know about the mute as they dont talk anyways. :P I do agree though. We need undercover mods and a whole new department in Jagex towers that is dedicated to downloading bot porgrams off the internet and figures out how to destroy them from the inside. I am fairly sure already knows about every public bot, if not all then most of them. They just can't do anything about them.

Basically when you trade somebody, you click on the item in your inventory and your client sends the message to the server trade 1 of item 112. The server puts that item in the trade window and takes away yours, if the trade is accepted the server takes the item out of the trade window and puts one in the other persons inventory. Before they fixed it, the server never checked to see if you had the item in your inventory in the first place before taking it away and putting another of the same item in the trade screen. So when they 'duped,' they used a modified client to send the 'trade 1 item 112(or whatever the item id of a pink party hat is) to the server, the server didn't check if they had it in the first place. Jagex didn't think to add this because you obviously can't send a trade item packet to the server when it's not in your inventory with the legit client. So it wasn't really duping, it was item creation because they didn't need to have it in the first place. The banker killing bug happened the same way, there is no right click attack option on a banker, but they sent the packet to the server which would have been sent when a player attacks something. They could attack the bankers because the client just didn't have a right click option, the server never had any 'non-attackable' npcs.

Rule 4 - Cheating/Bug Abuse We have put a lot of effort into balancing the game to make it as fair and fun as possible. Unintended bugs can spoil the effect of the game, so we obviously want to fix them as quickly as possible. Deliberately taking advantage of a bug can unbalance the game economy or devalue other players' achievements, so it is against the rules. As long as you report the bug to us straight away, don't tell anyone else until we fix it, and don't use the bug any more, then you WON'T get in trouble. Indeed, we will be very grateful. If you don't tell us, or deliberately use it again and again, then you would be breaking the rule. You must not use or attempt to use any cheats or errors which you find in our software. Any exploits which you find must be immediately reported to Jagex through Customer Support. Taking advantage of a bug which can unbalance the game economy or devalue other players achievements is against the rules, walking around bent over does not. I used to have a copy of the player mod center, I am almost certain that it said in there graphical glitches are not against the rules, can a player mod confirm this?

It's not bug abuse, its a graphical glitch which you gain no advantages with. How do you do it though?

Just because someone knows more about computers than you do doesn't make them a geek.

If you google OCR then you will realize why your idea won't work.