Iamdan

Since I know how to code, I do know what jagex would do, at least roughly. There is no way that jagex would do every single password separately, or anything else when they can make a variable. If you don't know anything about coding, don't make assumptions about it.

Yay. More updates designed for 10 year olds. Or perhaps, this might sound crazy. Coding something that checks EVERYONE'S password, while keeping it secure, and actually checking each time to block out whole sentences that contain it. "Might" be alittle difficult. How is creating a variable made to be the users password and adding it to the chat filter time consuming?

He is probably not talking about regular text like from randoms, I believe he is talking about syntax. Which is what jagex used in their fatigue system. Again, this is easily bypassed by an OCR. What may I ask, is the point in you saying the same thing I said, except with less intelligence and more cussing? The idea won't work, nuff' said.

A nice little story there, I am sure you put some time into it. Alas I didn't read the whole thing, I read until I saw Thats a wild assumption there. A program cannot read characters? First of all, client hacked macroers will just read the packet sent from the server. They don't need to recognize characters on screen, Runescape's server tells it what they are anyway. If the macro in question is a colour clicker, it can easily bypass it as well. Google OCR for more information.

Sorry for the double post, but has anyone sent a question to jagex about this?

It works via a reflection system, true you can always inject custom CRC values etc for the data file checks, but it is more trouble than it is worth, and there are still many other traps to avoid. They already do something like this, I mentioned it earlier. The problem is that it can still be gotten around with an auto updater. The other problem is that they don't bother, they aren't worried about being caught, that it why they are level 3 with default clothing. Which shows that they are not taking the time to avoid detection, which points to my point before, that jagex already knows they are macroing on login anyway. Actually it is the other way around. The macroers which do the most damage are not worried about being caught, so they macro with 10 accounts at once 24/7. The macroers which really only macro to beat the system, are the ones which spend the time to make it undetectable, they aren't the real problem, as there is much less of them, and since they do care about being detected, they don't macro with 10 accounts at once 24/7. I decided on digging up a deobfuscator and decompiling the runescape client so I can give more precise information. I have a new computer so I have to download Java Development Kit again. (140mb file)

^^It checks for default clothing. N2N: If you want to check out the script it is at SRL. (For anyone else, don't bother googling that, you won't find anything.)

There are two types of auto updaters. One of which simply works like the runescape client, connecting to the applet. If there is a file different or new, it updates the client, same with the macro. The other is simply manually downloading the client, extracting it, and running it through an updater which changes the appropriate files. Manually looking for changes and updating is really annoying, I have done it myself before. Only problem is that there is no way for the server to update, updating the legit client, without being easy for that first type of updater to update as well. The updater doesn't update for "logical things" it just finds any kind of changes. Jagex made a clever update about 4 years ago, which stopped a deob bot for a while before the devs figured out what happened. Every 24 clicks the client sent a secret packet. The macro however did not. Your idea reminded me of this so I thought I might bring it up, it's just that macroing has come just as far as Runescape has so things like this don't usually work.

Jagex has a system similar to that. Small things in the code change all the time, it could even be every 60 seconds. That way, the macroer needs an absolutely perfect auto updater.

The reason why macroing is against the rules, is because it gives players an unfair advantage. My script however does not. Even though it still is macroing, logically there should be an exception, because it doesn't violate the reason WHY macroing is not allowed.

Ok I have a script, (Didn't write it myself) which reports obvious macroers. It is designed to be left at a place such as yews, then reports level 3's and 4's in default clothing. Of course, there is a tiny chance that it will report a legit skiller in default clothing, but 1 bad report out of 100 or so isn't something to complain about. My question: Is this allowed? Rule 7 is "You must not use other software to gain an unfair advantage in the game." Using this macro is not gaining any advantage, in fact it is helping out everyone associated with the game. (Except that macroers) The only way that TECHNICALLY it comes under rule 7 is "Software that generates input to the RuneScape applet. This includes software that automatically moves the mouse pointer or generates mouse clicks or key presses." Though I think this macro should be allowed an exception. Could somebody send a question to jagex about this? I would myself but f2pers don't get answered. At least I haven't.

Everybody has seen many suggestions to stop macroing. Out of all of them, I have only seen 1 which will work. (With a few modifications made) The problem is that people don't understand how macroers work. Jagex is trying to convince everyone that their randoms actually work, which probably contributes to this. Since I hang around on cheating communities, (Some are actually nice places for coding tips) and I know a little programming, I know what will and wont help stop macroers. I have found that if people actually understand more about how macroing works, they will know what to suggest to combat it. For this reason, I will explain very briefly how one particular type of macro works. When you play runescape, you run an applet which runs your runescape.jar file on your computer. (a .jar file is like a .zip or .rar file, except its attached to an applet which is made to open and run it) This .jar file is what gets downloaded/updated when you load runescape. The contents of this .jar file contain the runescape client. ie: the applet runs the .jar file, therefore running the client. When you click something in the client, it sends a message (or packet) to the server. Say you're mining iron. You click the iron rock, your client sends something along the lines of username clicked iron rock at this location (except in java) The server checks that there is in fact an iron rock at that location, that your in the area, and it is not already mined. If it all works out then it changes the rock to a 'being mined' status. Sends the message back to your client and tells it to make your character start hitting the rock...... Im sure now that you get the picture on how runescape works. This particular type of macro is started by extracting the contents of the .jar file, and modifying it to connect directly with jagex's servers without the applet. I will not go into much detail on this, as it would take a while and I doubt many people would read it, but since the user has a working client which does not require an applet, they can edit it however they want. They can do absolutely anything, except change anything server side, so it only serves for looks and funny screen shots. The user can edit this client, so instead of the user clicking the rock, and the client sending the packet, the client read a script (so it knows what messages to send and when) and sends this "username clicked iron rock at this location" without you actually clicking the rock. That is the reason why randoms do not stop these kinds of macros, the server sends the packet telling the client you have a random, so runescape is pretty much telling the macroer "hey you have a MOM, you'd better solve it like this" If it didn't tell the client how to solve it, then what would a legit player's client have to check against if they got it wrong? If you are still with me on this than I am sure you appreciate the vastness of this problem. Jagex landed a huge blow to this type of macroer, with the new game engine. It was actually the main reason of the new game engine. The new game engine makes a check to the client, and basically checks if it is a modified client or not. As soon as somebody logs into a modified client, macro or not, they are automatically flagged, and jagex bans the account in a few weeks when they get around to it. Since the macroer is logged into a modified client, they are automatically breaking rule 7. Jagex is obligated to ban the accounts on login, because they know it is a hacked client, on login. Instead they wait for a manual ban, meanwhile the account has racked up 10 mill from autoing. My solution: If somebody logs into a modified client, they are automatically logged out and banned, jagex currently flags the account, why not just ban them? I believe that jagex first chose to flag the account instead of ban it on login because they wanted to know how their shiny new game engine got hacked. Since there is currently only one working macro of this type which is public, they must already know and there is no point in continuing to flag instead of ban.

Destroyed most of Australia's bananas, prices went way up for ages. I would have to go with water, you don't mess with water if there is enough of it. It can wash away mountains and destroy cities.

Easily fixed. Jagex could just make the tile cover the ditch, and 1 square on either side of it. If the player comes from one side, the default position to stand on will be on the other side, and vice versa. So it is impossible to actually stand on the ditch.

nowadays, people who get lured do not learn, they rant on the forums until their threads get locked, then rant about the forum mod that locked it. i'll agree that players today have it too easy, though, and i wasn't in classic. They rant on the forums and get their thread locked, then rant again, but they still learned something. They learned that rs is tough. They also leaned that get got lured, and roughly about how luring works. Most wont get lured again. Now there might be some morons who didn't learn the first time, and get lured again. Even if they get lured 10 times, somewhere along the lines they will think to themself: "Hey the last 10 times this happened, I got lured and lost my stuff, I don't want to do it anymore." The only people who will never learn would be anybody who is clinically insane. The definition of insanity is trying something over and over expecting different results.

I updated it because the problem got worse, then I fixed it later.

The hatchet repair thing won't stop macroers at all. Firstly the amount of cuts you posted is absolutely ridiculous, it would need to be much higher. Apart from that, as somebody said macroers will stock up on hatchets. Macroers could also auto walk to bob and repair their hatchet easily, so it wouldn't hinder them anymore than it would hinder legit players. About the attack/combat stat requirement, it has already been said many many times before. That idea is nothing new, and neither are skill pures complaining about it. While I don't see the point in skill pures, every noob and his dog seems to have one. They aren't anything special anymore, they will still whine if a combat requirement is added.

I don't agree with the update, but I guess I don't really hate it either. Probably because IMO Runescape has been going downhill since jagex killed classic and I really don't care about it anymore. For starters I think it is really ugly. That ditch looks ridiculous and out of place. The wilderness is supposed to be exactly that: the wilderness. A place where anything goes, a place where it is survival of the fittest. Become stronger or die. The new ditch is one of many changes which is making it the opposite. The wilderness is becoming more and more friendly. Back in classic, you were killed over and over again before you learned how to pk properly. When you did finally learn, pking was intense. With the 3 hit rule, no eating during combat, catching etc. The only way people learned how to pk was by getting killed over and over, because of it, classic vets who still play are some of the better rs2 pkers. If somebody gets lured, they most probably won't again. They died and lost their stuff, but they became smarter. The only way to get better at runescape is through trial and error. Notice the first generation of runescape was much more skilled as a whole than the current? Everybody leaned how to play the hard way, not by reading guides and taking advantage of idiot proof updates. If runescape continues to be updated like it is, the players will just become dumber and dumber. Because they aren't forced to learn anything like we were.

I fixed it. Thanks for all the help guys.

Until yesterday I knew next to nothing about the kernel file. I read up about it, and tried to run the kernel file just to see what it opened. Of course, it didn't like that and gave me an error. I thought nothing of it. This morning, my computer froze when I was downloading a 100mb file, at the same time refreshing a counterstrike source server waiting for a lower ping. After I restarted, my computer wouldn't boot up for some reason. Sometimes it would get to the loading windows screen, sometimes it would freeze on the "boot windows up normally/safe mode screen after I had picked an option. I tried to boot up with ubuntu, which wouldn't work. Then one of the times I tried booting up in safe mode, right before it froze again, the path of my kernel file came up. It was then that I finally realized what had happened. I then tried booting from my xp cd, which overwrites the kernel file to the computer. My computer then booted up fine, but I still don't understand the whole thing. How could the kernel file get corrupted just from me trying to run it? UPDATE: My computer now does not boot up, I turn it on and I don't even get the motherboard logo screen, so I don't think it is anything to do with software or my hard drives.

Talk like a pirate, definitely. How could you even consider anything else?

^^ At 70 range in f2p, you only hit 12 (maybe 13) on rapid. 13 or 14 on accurate.

It's not a matter of how long ago there was a stock market. Runescape is a game about killing monsters, gaining skills and doing quests. A stock market would not suit the theme of the game.

"Just pay for membership" is used much much more by members, than "you wouldn't quit membership" is used by f2pers. Also, what are you being sorry about? It's not like it is your decision or anything... That's the whole point in the threat, to get skill capes available in non member worlds

Considering the average intelligence of runescape, I doubt this update would be used much. Also it is fairly expensive which will put more people off. Also, it doesn't really tie in with the whole runescape theme. It would be really out of place. The idea would be a huge update, especially codewise. Jagex probably wouldn't bother doing it. I don't think it will attract members, which is what updates are for anyway. The stockmarket doesn't appeal to most 13 year olds.