@OP
Bring it to blizzard's attention on the official forums if you expect anything to be done about it... posting about it on a fansite is pointless..
This has been explained ad nauseam on these forums so I'll give you the short version ...Originally Posted by wysinwyg
Files being left on, or sent to, the client machine (your computer) are what makes these hacks possible. The only reason that speed hack is possible is because character movement is calculated on the client machine using variables sent to the client.
To allow single player Blizzard would have to also put the mob files, mob spawning scripts, item files, item drop scripts, stat modifying scripts and pretty much everything else on the client machine.
Do you understand why that would be a lot worse? Do you understand why Diablo2 is such a hacked up piece of crap right now? It's because of the single player mode.
For the same reason that D3 has taken forever to develop - no one that worked on the originals is around, so they basically have no idea how to maintain it, nor did they have much of a clue on how to develop a game in that genre.
You're right that they didn't have much of a clue on how to develop a game in that genre. They made many horrible mistakes with Diablo2, the most egregious being the idea that the game should be maintained client-side.
There was no real point in even having a closed battle-net if they were just going to hand all their scripts and files over to every single player. No reason to do that and then waste a ton of money on a losing battle against hacking, which is why they eventually just gave up on D2.
You think Blizzard likes the idea that code breaking scammers have completely taken over one of their games, and to this day are still preying on their loyal customers? Blizzard just can't do a thing about it because by handing over single-player clients they royally ****ed up.
Yes, I understand that by running some of the code on their server they reduce the ease of hacking. Maps were stored locally in D2 and that's why maphack worked right?
For what you've said to make sense, being able to see how the code runs would have to allow hackers to do stuff they wouldn't have been able to do anyway. How many D2 hacks were based on being able to see single player code? The main problem was duping. Would that have been impossible without a D2 single player?
Btw, Diablo2 is still an awesome game. I haven't run across hacks since I stopped playing on bnet about 5 years ago
Many of the exploits used in D2 were likely found by code analysis and testing on the single-player client. It's very unlikely that people just lucked into the numerous exploits discovered.Yes, I understand that by running some of the code on their server they reduce the ease of hacking. Maps were stored locally in D2 and that's why maphack worked right?
For what you've said to make sense, being able to see how the code runs would have to allow hackers to do stuff they wouldn't have been able to do anyway. How many D2 hacks were based on being able to see single player code? The main problem was duping. Would that have been impossible without a D2 single player?
Btw, Diablo2 is still an awesome game. I haven't run across hacks since I stopped playing on bnet about 5 years ago
Duping is much more difficult without a single player client or a client heavy infrastructure. Without the client you basically have to luck your way into some kind of obscure coding error, which has happened even in WoW, but it's usually patched up quickly.
The same hacks will eventually be available whether single player is enabled or not. It will just take the hackers slightly longer, but they will easily do it. Duping will not happen even if Blizzard gave the code to the hackers, it is handled differently now.
Actual hacks depend solely on how much the server has to communicate with the client. In a perfect world the server would handle all the scripts and processing and would only require peripheral input from the client.
Now what single player encourages is exploiting game code and mechanics. Giving talented programmers the game client is like giving a master thief the security detail and blueprint to your house. It's stupid.
I posted this on the battle net site. My post has slowly found its way to the bottom of the pile. I guess blizz just wants to sweep this one under the carpet.
- An unknown number of dupe methods (but not all of them). These are mostly moot in D3 anyways due to the change in how items are handled.
- The ability to get an open character into a closed game, and hence create stuff like white items, hex charms, etc. Also moot in D3 as a character can't 'bring' items anywhere.
- Maybe trade hack, but again moot.
- An unknown number of rollbacks / server crashes (again, not all of them). These would be even more important in D3 than they were in D2 thanks to crafting I think. That said, improved Warden + server side auditing should make catching / banning people who do this much easier, but it's tough to say.
Anything else I can think of would not have been at all easier in D2.
Posting Permissions
Bookmarks