We presented Displaced Gamers’/Behind the Code’s video on the jankiness of kusoge disgrace Dr. Jekyll and Mr. Hyde back on Saturday. They did another video on that game, that delves into why the game’s frame rate is so inconsistent. In summary, its engine throttles its framerate in a terrible way, using long delay loops. It’s a pretty awful idea! It’s 19 1/2 minutes long. The video claims it’s even geekier than their first video on the game, but I think it’s actually slightly less technical, at least it doesn’t fill the screen with as much 6502 assembly code.
Another fact about J&H: the Japanese version had two full levels that were cut from the U.S. version, which replaced them with replays of other levels. It made a bad game even worse!
Now, because of Behind The Code, you know more about the Dr. Jekyll and Mr. Hyde game than many much better NES titles. Congratulations!
It’s 19 minutes long, and is even geekier than is usual for us, going into a disassembly of the game’s machine code in its quest to make the game marginally less awful.
While we’re on the subject, did you know that Jekyll & Hyde has a secret ending? Both endings are shown here (4 minutes):
The “bad” ending is the normal one, and shorter, but is arguably a happier conclusion to the story. To get it, all you have to do is get to the end of Stage 6 with Jekyll. That’s all.
To get the other ending, get to Stage 6 with Jekyll, then turn into Hyde and get to the end of his version of the stage. Usually, if Hyde gets as far into his level as Jekyll has gotten into his, he’s struck by lightning and dies. But in this level he’ll be allowed to reach the end of his version of the level for some reason, where there’s a boss! Beat it, and when you return to Jekyll’s world the enemies will be gone, and he’ll be free to finish the level without harassment. However, ending events will be different….
Bad Game Hall of Game is an interesting blog that talks about failed titles without the snark with which they were usually treated in the early days of the Web, or the rancor of The Angry Video Game Nerd. Snark and furor drive hits, of course, so I can respect the desire to give games many regard as kusoge their due, whatever that may be.
When you know it? It’s simple. When you don’t? It’s unfair.
Truthfully, there are lots of games that are perceived as bad that aren’t really so terrible, often due to the audience-chasing bile emitted by folk like Seanbaby and Something Awful. Games intended to be played for challenge, especially those from arcades and the earlier years of consoles, are kind of a pastime for masochists. When you lose, it often feels like it’s not your fault, but was it really? Was that hit telegraphed and avoidable? Was there some clever technique to be discovered, like jumping and slicing through an Ironknuckle’s helmet in Zelda II, that makes seemingly impossible enemies a simple matter to defeat? And when a game is intended to be played many times, not shattered in a single session but returned to many times, getting a bit further each time, isn’t it supposed to be a good thing that you may lose your first time out?
I took these screenshots myself for this post. See what I do for you.
There are lots of armchair game designers, maybe even more than armchair movie directors, since players spend more time with games generally before they put them down, and it’s easier, theoretically at least, to make games yourself without the capital expenditure and outside labor that movies require. (I can tell you though, it’s still plenty hard.) And yet, they are the players, and if they’re not having fun, then the game is doing it wrong. Even if it’s because of some information or training the player hasn’t, in their life, gained, you can’t blame them. Maturity can help a player enjoy games they wouldn’t otherwise. But this is also true of any art form, and the opposite could also be said to be true, there are games where, I’d say, maturity is an outright barrier to enjoyment. It’s complicated. Maybe I’ll talk about this later.
URG URG URG URG AIIEEE
In the article that Bad Game Hall Of Fame talks about that I find interesting today, the game in question is Sword of Sodan, the creation of Finnish demo coder Søren Grønbech, an infamous game with a much longer story behind it than your typical bad game, indeed extremely long. Out of curosity, I pasted BGHoF’s discussion of it into Microsoft Word, and it came up to 67 pages! It’s got two large sets of footnotes, goes back to the Amiga demo scene and gives insight into the difficulties of developing computer games, at the time, in the state of Denmark.
Almost nothing gets through these giants’ defenses, and your encounter with them puts one on either side. As a connoisseur I must say, the frustration is exquisite.
Sword of Sodan for the Sega Mega Drive/Genesis, as it turns out, is a port of an Amiga game. Both games are extremely hard, but the Genesis version actually has more interesting design decisions behind it, in the form of its potion mixing subgame. You can hold up to four potions, each of one of four different colors, and can choose to drink any number of them at once. Drinking different combinations of potions has different effects, most good, some useless, a couple actually bad. (Hilariously, if you drink one of each color at a time your character immediately dies, and the game flashes a message on screen: “WINNERS DON’T DO DRUGS.” Gee thanks, William S. Sessions.)
Many games of the time talked the talk, but Sword of Sodan would outright kill you if you got too experimental with your potions.
67 pages is a lot to read about a game that few people might want to play, but it’s okay to skip around. I won’t tell anyone.
