One of the first games I was introduced to on the 2600 was River Raid, back in 1982. I remember it vividly, as I was at my cousin David’s house, who was older than me, and he’d “baby sit” me so the adults could have some adult time hanging out in the dining room. We’d sit in the family room playing 2600, mainly River Raid.
This is an Activision game, and was later ported to Atari 5200, Atari 8-bit, C64, ColecoVision, IBM PCjr, Intellivision, ZX Spectrum, and MSX. The player controls an airplane in a top-down view over a river and gets points for shooting down enemy planes, helicopters, ships and balloons (for versions after the Atari 2600). By flying over fuel-stations, the plane’s tank can be refilled. The player can shift side to side and change the speed of the plane. Sections of the river are marked by bridges.
The game was highly acclaimed for its ability to stuff tons of map into small amounts of space. The map was huge and it fit on the disk because it’s randomly generated using a common starting seed, basically, imagine some of the Diablo dungeons…they’re randomly generated but the starting seed which starts the random process is also ‘random.’ (probably based on clock time which isn’t too uncommon). Atari, rather than try to make a random level each time used the level random generator to build a procedural based level rather than drawing it and saving it into the cart. GENIUS.
A more highly randomized number generation system was used for enemy AI to make the game less predictable.
Germany consider this game harmful to children, indexing it on their list of games “harmful for children” along with the game Speed Racer. It remained on their list until 2002 (since 1984) when developers petitioned it off the list before the PS2 launch of Activision Anthology (otherwise they’d not be able to put it in the game)
Some of the Germany reasons: Minors are intended to delve into the role of an uncompromising fighter and agent of annihilation (…). It provides children with a paramilitaristic education (…). With older minors, playing leads (…) to physical cramps, anger, aggressiveness, erratic thinking (…) and headaches (wikipedia)
All in all, a great game! To hear all the details on River Raid and our opinions, checkout TD Gaming Podcast Episode 78.
Derrick, that’s Shogun: Total War (it was the first Total War game in its series so the graphics aren’t that good compared to the recent Total War games). I liked that game too.
If you liked Nobunaga’s Ambition you might like Genghis Khan 2, also made by KOEI (http://www.abandonia.com/en/games/505/Genghis+Khan+II+-+Clan+of+the+Gray+Wolf.html)
What’s your take in Valve’s concept of episodic releases? They explained that with that kind of structure they can easily take advantage of new technologies as they come up, and not have to hold back using new technologies until the next reiteration of their game.
The problems with long release cycles, taking it to the extreme, with Duke Nukem Forever (I think) the reason why it was so delayed was by the time they reached mid-development, their game, the graphics, the engine look so obsolete, so they bought a new engine, and by the time they reached back to mid-development, the then new engine they bought gets outdated, and the cycle repeats.
Something like this happened with Blizzard with their Warcraft Adventures (it was never released).
I think episodic structures work well for some games (Sam and Max), and long development cycles for others. So long as I get a game I can enjoy I don’t really care that much
Here’s what *I* think about it, underdog: They take way too friggin’ long. They keep changing the engine, when all you need to do is create levels.
Look at Telltale Games – now they do episodic content right.
@jonahfalcon: yeah I know, the wait is killing me for episode 3.
but from a developer’s viewpoint, improving the engine continually will do good in the long run since it’ll not only help with that game their making at the moment, but they can use it for their future games as well.
keeping the engine up-to-date with new technologies is always good. I’ve worked with commercial engines that, while popular, they start showing their age in that we couldn’t incorporate features we had in mind because of its limitations that could have been fixed with newer libraries