On the subject of slaying, I can be pretty brief. Some people wish to gain as much XP per unit of time they're playing, and as such don't have time for being nice. They are relentless in their pursuit of maximum XP and don't care about what a bunch of people they don't know think about them. If you (speaking to the reader of this post, not just the article's author) want to be a gentleman, sure, go ahead. If the person you're sharing the room with is well-mannered, awesome. But at all times be aware that some people play solely for gathering as much XP as humanly possible and won't be playing nice. Whether such an attitude is good or bad is up for debate (personally think it's rather detrimental to the game's atmosphere), but if you expect every newcomer to set up a cannon you'll be relieved if they don't; and if they do, you can just shrug and move on, saving yourself a lot of frustration. I thought the article was well and humorously written, so I'm sad to see that author's calling it already. Don't quit just because you got some criticism, it comes with the job. As for the outrage over the update, I too raised an eyebrow at how seriously pissed off some people seemed to be. Some even claimed that Jagex were bad at what they do (developing software/games) because of their inability to stick to their schedule. By that definition, just about every software developer in existence would be awful. Take big brother Blizzard, for example. Early in 2007, when The Burning Crusade, a WoW expansion, hit retail, Blizzard said they were aiming to release a new expansion every year. Yet the next expansion, Wrath of the Lich King, shipped 20 months later, and right now we're close to 19 months into Wrath and while the latest expansion, Cataclysm, is in beta at the moment, it sure doesn't look like it's anywhere near ready for release. Yet I don't see anyone claiming Blizzard is a bad software developer. On the other hand, consider Ritual Entertainment. They were developing a pretty high-profile shooter back in 1998 called Sin. It wasn't quite polished yet, but their publisher (guess who :lol:) wanted it out before the holidays. Beta versions were sent to game magazines, with claims that bugs would end up being fixed. Sure, the game looked and sounded great, and disregarding the various quirks and glitches gameplay was pretty solid. Reviews generally praised the game. At my local toy store, one of the employees was into games pretty big and had visited the E3 that year. He said there were three major shooters on showcase. The first, Duke Nukem Forever, was awesome in every which way imaginable. Then there was Sin, which was less awesome but still looked promising. Oh, and then there was some game called Half-life which he thought looked pretty [cabbage]ty. Duke's new game has been canned after years of being stuck in development hell, Sin was released on schedule but it was so buggy and sluggish that you could literally start loading a level, go to the bathroom to take a dump and come back to see that it was STILL busy loading, and Half-life went on to win 300 game of the year awards. Sure, Sin was patched up afterwards, but the patch was so large that it'd take about three years to download over dial-up, which was the standard back then. Ritual kept to their schedule, sure, but I don't see anyone calling them good developers for it (even if admittedly Activision was to blame for it). Jagex kind of suffered the same dilemma, though on a smaller scale. Either release the update now and make the game unplayable for a bunch of people, or delay it and release a polished update. Personally, I think they made the right call here. Keep in mind that game development as a bit of a sciency edge to it. Say, some office guy has to grind through a dozen of boring reports and write a dozen equally boring assessments. Nothing out of the ordinary is going to happen there, so if he's been given sufficient time yet doesn't manage to finish his assessments he's clearly been slacking. On the other hand, as was explained in last week's forum post, something unexpected went wrong with the graphics update. It happens. However, they did seem to hint strongly at a certain release date through tweets, if they hadn't done so they probably would've prevented some of the outcry from happening. Lesson learned, I suppose.