I was a programmer on Diablo 2 and used the Diablo 1 source code as a starting point for some features - all of the source files I looked at had David Brevik as the author, it was very straightforward C that one person could keep in their head.
Don't leave us hanging, is there a hidden cow level in the Diablo 1 source?!
What are you working on these days? Are you still in the games industry?
But also thanks for your work, still playing D2 :)
> Don't leave us hanging,
Yes, don't leave us hanging!
Did you ever work on the problems of item duping on Closed Battle.Net?
I never understood why some games were "bugged": Certain characters would leave a game and find that their inventory would not save. This meant they could go back in the game, drop all their items, leave the game, and repeat this while the characters that did save could pick it up, creating copies of good items. The mule character could even join another game where it would save, stock up on good items and drop those.
I also never understood what would trigger a bugged game. We used IRC for announcing whenever a "run" turned out to be buggy for a single player. And I wrote an IRC bot for keeping track of item trades for some dudes who gave me several accounts full of characters full of really good items. I gave it to my brother who eventually made thousands selling those items.
> is there a hidden cow level in the Diablo 1 source?!
Diablo I has a ton of lost treasure hidden in diabdat.mpq. I recall that they shipped the game prematurely and simply dropped a large chunk of the storyline; full characters, dialogues, items, plot triggers. Some of that storyline ended up in Diablo II. I can't find a good archaeological overview online - perhaps this isn't as well-documented as I assumed.
If anyone feels nostalgic, there's a really good Diablo I mod called The Hell out there. I believe mods are written by disassembling the original game, extending this with your own, custom assembler code, and reassembling it. What a beautiful consequence of the simplicity of writing games in C.
A lot of the features we added to D2 were things the original creators wanted to do in D1 or even the D1 expansion, the D1 expansion was outsourced and they were really unhappy about the quality of the add-on and were determined to make things right with D2 and do the expansion in house as well. I finished my work early so I added the keyboard customization feature for fun. There's a making of book about Diablo 2 that interviews the guys who also started Blizzard North/made Diablo 1 so a lot of information about the process is in there.
This desynced state resulted in a ton of commonly known dupe methods in 1.11 and 1.12 where you forcefully disconnect the GS from MCP. The popular one was spamming bone wall (creating entities on the map), then spamming AoEs which interacted with said entities. The game server would have to loop over all entities for each AoE spell you cast to determine if the spell applied to it, which caused the single-threaded game server to spend too long in each iteration of the main game loop that caused it to desync from the MCP. Blizzard eventually "fixed" this by adding a check for how long the main game loop took to complete. If it hit a certain value, it would disconnect all players from the game to despawn entities and 'prevent' dupes.
There were more fun bugs between GS <-> MCP as well. For example for many patches there was a size limit on your character. If your character data was over a set size, the GS wouldn't even try saving your character to the MCP and would roll it back to the last valid save. If you joined a game near the limit, dropped an item, picked up an item that was larger in size (had more stats etc) which pushed you over the limit, then left the game, the server would revert your save back to when you had the original item.
D2 was full of esoteric exploits like these. It was made worse by some Blizzard developers going rogue and abusing the buggy state of the codebase to assist third party item sellers for personal profit.
I vaguely remember the strike team talking about those game server issues, it's been so long I totally forgot about it. We had the servers on racks in the data centers running Windows NT and I remember the very first problems were trying to get the game to support hundreds of games per server and finding all sorts of memory issues and network issues that caused the games to crash or run out of memory. I was unaware of the developers going rogue - that's wild.
But there was one guy in our office who got hauled away by the FBI because he was hosting a file sharing node using the office T1.