Related articles

• Intel Processors (Socket 478) 200 MHz FSB (Dual DDR400) Pentium 4 3.20 GHz Extreme Edition (3200 MHz 12-8/512/2048 kB) 200 MHz FSB (Dual DDR400) Pentium 4 3.20 GHz (3200 MHz 12-8/512 kB) Pentium 4 3.00 GHz (3000 MHz 12-8/512 kB) Pentium 4 2.80 GHz (2800 MHz 12-8/512 kB) Pentium 4 2.60 GHz (2600 MHz 12-8/512 kB) Pentium 4 2.40 GHz (2400 MHz 12-8/512 kB) 133 MHz FSB (Dual DDR333) Pentium 4 3.06 GHz (3066 MHz 12-8/512 kB) Pentium 4 2.80 GHz (2800 MHz 12-8/512 kB) Pentium 4 2.66 GHz (2666 MHz 12-8/512 kB) AMD Processors (Socket A) 200 MHz FSB (DUAL DDR400) Athlon XP 3200+ (2200 MHz 128/512 kB) Athlon XP 3000+ (2100 MHz 128/512 kB) 166 MHz FSB (DUAL DDR333) Athlon XP 3000+ (2166 MHz 128/512 kB) Athlon XP 2800+ (2083 MHz 128/512 kB) Athlon XP 2700+ (2166 MHz 128/256 kB) Athlon XP 2600+ (1917 MHz 128/256 kB) Athlon XP 2500+ (1833 MHz 128/512 kB) AMD Processors (Socket 940) 200 MHz FSB (DUAL DDR400) Athlon FX-51 (2200 MHz 128/1024 kB) AMD Processors (Socket 754) 200 MHz FSB (SINGLE DDR400) Athlon 64 3200+ (2000 128/1024 kB) Memory DDR433 (216 MHz) 4 x 256 MB / 5ns / 64 Bit (Corsiar TwinX) XMS3200 (CMX256A-3200C2 CL2 T1) DDR400 (200 MHz) 2 x 512 MB / 5ns / 64 Bit (Corsiar) CMX512-3500C2 CL2 DDR400 (200 MHz) 2 x 512 MB / 5ns / 64 Bit (Legacy Eletronics Inc.) Reg. ECC (88S6HDAR-1TDG 5733) Infineon DDR400 (200 MHz) 2 x 512 MB / 5ns / 64 Bit (TakeMS) MS64D64020U-5 Motherboard Intel 875 (Socket 748) Asus P4C800-E Deluxe Rev: 1.02 Bios: 1011 BETA 006 4 x 256 MB CL 2.0-2-2-5 (200 MHz) 4 x 256 MB CL 2.0-2-2-5 (133 MHz) Nvidia nForce (Socket 462) 2 Ultra Asus A7N8X Rev: 2.00 Bios: 1006 2 x 512 MB CL 2.0-3-3-6 (200 MHz) 2 x 512 MB CL 2.0-2-2-5 (166 MHz) 2 x 512 MB CL 2.0-2-2-5 (133 MHz) Nvidia nForce 3 150 (Socket 940) Asus SK8N Rev: 1.03 Bios: 1003 BETA 002 2 x 512 MB CL 2.5-3-3-6 (200 MHz) VIA K8T800 (Socket 940) MSI K8T Master 1-FAR (MS-9130) Bios: 1.0Bd Rev: 1 2 x 512 MB CL 2.5-3-3-7 (200 MHz) VIA K8T800 (Socket 754) MSI 8KT Neo (MS-6702) Bios: 1.0 Rev: 1.0 2 x 512 MB CL2.0-4-4-8 (200 MHz) Common Hardware Sound Card Terratec Aureon 7.1 Space 96.00 kHz sample rate Graphics Card MSI FX5900U-VTD256 GPU: NVIDIA GeForce FX 5900 Ultra Memory: 128 MB DDR-SDRAM Memory Clock: 620 MHz (256 Bit) Chip Clock: 325 MHz Hard Drive (AMD System) FastTrak S150 TX2plus (Bios: 1.00.0.30) 2 x SATA Maxtor 6Y080M0 (Raid 0) 80 GB / 8 MB Cache / 7200 rpm Hard Drive (Intel System) Intel FW82801ER ICH5R 2 x SATA Maxtor 6Y080M0 (Raid 0) 80 GB / 8 MB Cache / 7200 rpm DVD/CD-ROM MSI MS-8216 16x DVD Network (Intel - I875) Intel 82547ET (CSA) Network (AMD - nForce 3) NVIDIA nForce MCP Networking Controller Network (AMD - nForce 2) NVIDIA nForce MCP Networking Controller Network (AMD - VIA 8KT800) Broadcom BCM5705KFB Software Intel Chipset V 5.00.1012 SATA - IAA V 3.51 Nvidia nForce Nvidia V2.45 Nvidia Graphic Detonator V 45.23 VIA K8T800 V 14.49 DirectX Version: 9a OS Windows XP, Build 2600 SP1 Benchmarks and Settings OpenGL Quake III Arena Patch V1.16 640x480 - 16 bit / 1024 x 768 - 32 bit Timedemo1 / demo demo001 / nv15demo command line = +set cd_nocd 1 +set s_initsound 0 Graphics detail = Normal Quake III Team Arena Version 1.32 640x480 - 32 bit Timedemo1 / demo thg3 "custom timedemo" Graphics detail = Normal SPEC viewperf 7.1a Version 7.1 Patch 7.1a 1280x1024 32 Bit Serious Sam Version 1.07 The Secound Encounter Graphics API: Open GL Preferences: Quality Resolution: 640x480 no Audio Bits per Pixel: 32 Bit Execute Addon: 32bit_HQ++-ansio8-24z.ini Demo: Valley fo the Jaguar Wolfenstein Version: 2.55 Enemy Territory 1024 x 786 - 32 bit timedemo 1 / demo demo4 Graphics detail = Normal DirectX 7 3DMark 2001 SE Version 1.1 - Patch Build 330 1024 x 786 - 32 bit, Default Benchmark DirectX 8 Comanche 4 Demo 1024 x 768 / 32 bit / Audio = off Unreal Tournament 2003 Version 2206 system/benchmark.exe 1024 x 768 / 32 bit / Audio = off Texture Detail = Normal Character Detail = Normal World Detail = Highest Physics Detail = High all = on, Decal Stay = High Splinter Cell Version 1.2b 2_2_1_KalinatekDemo 1024x786 32 Bit / no sound Shdow resolution: low Shadow detail: low Effects quality: low Blizzard Warcraft III Version 1.12 The Frozen Throne 1024x786 32 Bit / no sound Detail settings: high Replay: 3v3 esonlzerter average frames from minutes 1 to 14 FPS captured with FRAPS DirectX 9a 3DMark 2003 Version 3.3.0 Graphics and CPU Default Benchmark 1024 x 786 - 32 bit X2-The Threat Rolling Demo - bechmark Graphic Settings: all off 1024x768x32 (X8R8G8B8) Gun Metal Version: 1.20S (benchmark version) Benchmark 2 640x480 - 16 bit / 2 X FSAA Video Quality LOW Terrain Detail LOW Draw Distance HIGH Cloud Shadows OFF Lens Flare OFF Sun Glare OFF AquaMark3 1024 x 768 - 32 bit Audio = off Advanced Measurement Antialiasing mode: off Anisotropy: off Level Detail: very low Video Mainconcept MPEG Encoder Version 1.3.1 1.2 GB DV to MPEG II (720x576, Audio) converting Pinnacle Studio 8 SE Version 8.8.17 Rendering - DVD Compatible no Audio Xmpeg 5.0.1 build 5.0.8.82 Vdivx 5.10 Pro AMD: Otimized MMX iDCT Intel: Otimized SEE2 iDCT DivX 5.10 Pro Audio: off Psychovisual Enhancements: off Resize: 720x576 Restore Defaults 780 kbps feedback windows: off Windows Media Encoder 9 Version: 9.00.00.2980 436 MB AVI File convert to WMV Windows Media server (streaming) Discreet Cleaner XL Version 6.0.2.402 SP1 416 MB DV to MPEG II NTSC DVD 4:3 Apple Quick Time 6.3 Real One Player V2 Gold Microsoft Movie Maker Version 2.0 416 MB DV to WMV Audio magix mp3 maker 2004 Version 4.11 Build 19593 diamond 65 minutes/44.100 KHz wave file (688,4 MB) Format: MP3 High Quality Steinberg Nuendo 2.0 Version: 2.0.0 - Build on May 6 2003 VST Multitrack ASIO Driver: Aureon sky/space (96.000 kHz) Clock Source: Internal Resulution: 32 bit (float) Smaple Rate: 96.000 kHz File of type: Wave File (.wav) Channels (Stereo Splite) Lame Version 3.93.1 65 minutes/44.100 KHz wave file (688,4 MB) to mp3 Applications Bapco Sysmark 2002 Version 1.0 (Patch) Script Patch for fast CPU from Bapco Winrar Version 3.20 178 MB Wave file, Compression = Best Dictionary = 4096 kB Newtek Lightwave Version 7.5c - Build 572 Render First Frame = 1 Render Last Frame = 60 Render Frame Step = 1 Rendering Bench "variations.lws" Show Rendering in Progress = 320x240 Ray Trace Shadows, Reflection Refraction, Transparency = on Multithreading = 8 Threads Maxon Computer Version 8.100 Cinema 4D XL 8 Rendering in 1028 x 1024, "Stairs.c4d" Seti@home client: V 3.03 (text version) Work Unit with Angle Range: 0,417 HT: bench with two same Work Units Discreet Characters "Dragon_Charater_rig" 3D Studio Max 5.1 Rendering Single, 1024x768 Wolframresearch Version 5.0.0.0 Mathematica 5 MMA 40 Test Synthetic PCMark 2002 Pro Pack Build 101 CPU and Memory Tests SiSoftware Sandra MAX3! Version 2003.7.9.73 CPU MultiMedia / CPU Arithmetic Memory Bandwidth Benchmark We have radically reworked our previous benchmark test suite. We now rely increasingly on benchmarks that are based on real applications. It goes without saying that we use the latest versions of these programs for our measurements. Among the stress-intensive benchmarks is Steinberg Nuendo 2.0: An audio project file with more than 2 GB is calculated using a high-end sound card (Terratec Aureon 7.1 Space) with a sample rate of 96 kHz and 32 bits. The fastest processor - the Intel Pentium 4 - makes it in just under 3 minutes! In the case of Mathematica 5.0 a complex formula is used that would be unbeatable even for expensive, top-ranking calculators - the Athlon 64 FX needs 5.7 seconds for this! As is well known, the three professional rendering programs, 3D Studio Max 5.1 (available soon in Version 6), Cinema 4D XL 8.1 and Lightwave 7.5c (also available soon in Version 8).

• TG Daily: One of the things I've see with bot programs is that they try to appear more human (to lessen the chance of being banned). What are some of the technical measures that Glider tries to do? Mercury: Avoiding detection is rather exciting, to be sure. Since Blizzard does not want bots running at all, it's a violation to use them. Detection is cleanly divided into two methods: software and human. Avoiding human detection is fairly difficult because, let's face it, if another player gives Glider a Turing test in the game, it's not human. Rather than attack that problem at its strength (I'm a big Art of War fan), Glider tries to attack it at its weakness by not causing a player to become curious at all. We try to add little mannerisms here and there, like jumps and random strafing and bits of randomness to combat. For instance, if you tell Glider to use the Bloodrage skill with your warrior, it will sometimes use it before shooting the gun, sometimes after. If it's charging, it'll sometimes use it after the charge - and sometimes not at all. We try our best to make it not set off that first curious look from another player, but it's very difficult. Of course, a good part of avoiding player detection is, ironically, detecting players. Just like if it was your 10-year old nephew, Glider will alert you if there is another player following around for too long. So you can configure to play a sound clip at high volume so you can come and investigate - or simply log off. When it comes to suspensions or bans, discretion is more than just the better part of valor. TG Daily: How difficult is it to stay one step ahead of Blizzard? Also, can you empathize with the GMs who try to catch botters? Mercury: Staying one step ahead of Blizzard is just about impossible because you never know what they're going to do next. The technical nature of the game is that the Warden, which is where Blizzard's hack-detection code lives, is dynamically updated. The code itself doesn't even exist in the game client, but is sent down when you connect, just like your spellbook is. Given that agility and the fact that the game can update any time on a regular or hotfix patch, it's tricky. With all of the focus on the Warden lately, it wouldn't surprise me at all if Blizzard decided to bury a few simple checks in the game code itself. Some clever engineering would make that virtually impossible to find, as nobody can disassemble the entire enormous game client. XOR a few values together to make disassemblers miss the pointer reference and you've got some very stealthy flag-setting happening in the guts of, say, an item trade. So we have to make sure that Glider won't get picked up by anything that simple, which means we can't do a lot of things, like putting code into the game directly or altering its data structures. For us, staying ahead is really about the business decisions for Blizzard. What we do is figure out what's easy for them to detect, such as by changing a simple parameter in the Warden or adding a small bit of code. Then we make sure Glider is not detected as passively as possible, such as using regular Windows security to limit the game's access or randomizing process names. The trick here is that Blizzard has a finite amount of development and test resources, so we want to make it bad business to spend that much time altering their detection code to find Glider, since Glider's negative effect on the game is debatable. A number of people, including myself, are still playing WoW and have even activated second accounts solely because of the opportunity to use Glider to create a level 60 character of another class. When the Blizzard project managers sit down with the issues list, we want Glider to slip down the list behind other work. The bottom line is that Blizzard can detect anything that's available to the public with enough effort, since they control the client. So rather than attack that strength, we attack the weakness and try to make it a bad idea or make their changes very risky, since they don't want to risk banning or crashing innocent customers. As for GM's, it must be an interesting part of their jobs. Being a WoW GM seems like it would be one of the toughest jobs in the world, since they're effectively a level 1 help desk for gamers - and playing a game that they probably love. I imagine a GM has a little more fun when shadowing a suspected botter than simply helping someone get their lost Arcanite Bars back. I know I would. We don't see them as "the cops" or "the enemy" or anything like that. They're just guys doing their jobs.

• TG Daily interview: Chat with a World of Warcraft bot programmer

  Earlier this month, we ran a preview of an exclusive interview with Mercury, a developer of a World of Warcraft bot - a cheat program to accelerate the player's progress within the game. In this full interview, Mercury talks to TG Daily editor Humphrey Cheung about his motivation to create WoWglider, how it works and avoids detection, and his future plans for the bot. TG Daily: Were you an avid World of Warcraft player before writing the program - and what inspired you to write it? Mercury: Definitely. I'm one of the many lifelong Blizzard game owners out there. I started with Warcraft and have played all of their titles. When WoW was finally released, I got it immediately and I've been a fan since. The inspiration behind Glider was really what it's for now - to catch up to level 60 without spending so much real time. I'm in a small guild and my guildmates reached 60 while I was still in the mid-50's. I wanted to get to 60 as well to come along on the instance runs, but I had no time to grind it out between work and social life. When I did finally log in for a few hours on weekends, it was frustrating to see them orgranizing pickup groups for Scholomance and the Blackrock dungeons. I'd be off killing Shardtooth Bears and Crystal Rumblers solo. The original version was very unstable and simplistic, but it allowed me to get my warlock up to 60 pretty fast. My Canadian guildmates knew what I was up to and they encouraged me to turn it into a more well-rounded product so I could sell it. After I showed a few friends the rough version, they all collectively badgered me into marketing it. I promised my guildies that if I sold enough copies of Glider, I'd fly up to Toronto and buy them a round of beer, which I plan to do in January. TG Daily: Did any other programs give you inspiration or a template for developing Glider? Where did you learn the programming skills required to write the program and is Glider a full-time gig? Mercury: None in particular. I ran across a few tools that did some game automation, but nothing struck me as very professional. This was back in April, mind you, and things have changed a bit. But even then, our idea was to use my technology and my partner's marketing/design to position it as a very professional, clean app. So avoiding links to "hax0rs!!11" sites and keeping the design clean was the closest we had to a template. As for my own skills, I've been a full-time developer forever. I started with C, switched to C++ when it came out - that should date me - and just went from there. It doesn't take an enormous amount of talent to make something like this, but you do need to have a solid understanding of software development in general, like understanding business needs, prioritizing issues, source control, and so on. And, no, Glider's not a full-time gig. I've lowered my contracting hours to have more time for Glider, but it's still not making that kind of money. A big part of Glider is still the fun factor of working with the game and the users on our forums. TG Daily: How popular has Glider been? Do you have any estimates on how many times it has been downloaded? Mercury: It's been fairly popular, but not a huge, smashing success. In other words, I've never had to get more bandwidth or upgrade my small server. Without looking at the logs, and I don't want to reveal hard numbers, I'd swag it's been downloaded for evaluation around 3000 to 5000 times since the hard launch in late July 2005.