Difference between revisions of "Raiden II"
| Line 10: | Line 10: | ||
'''Related games:''' N/A | '''Related games:''' N/A | ||
}}{{PendingHeader}} | }}{{PendingHeader}} | ||
| − | + | A successful life is about hacking the system: working out how to do stuff with what limited resources you have, without regard to proper procedure. And hacking is about probing; feeling out the cracks in the system, watching what drips through, testing your whims and theories, and building your own meta-filter to slot on top. | |
| − | + | Game-Maker's system is made for top-down adventure games like ''[[Overworld|The Legend of Zelda]]''; if you try [[Space Harrier|something else]], you're going to meet resistance. Try to make a shooter, and the system will say to you, that's a strange sort of adventure game. It will run what you plug into it, but it won't know what you're trying to do. | |
| − | + | So, most scrolling shooters are kind of a mess on this engine. What ''Raiden II'' does a bit differently is it takes a step back to think about what it feeds into the engine and how that will be understood, then adapts its input accordingly. | |
| − | + | [[File:RaidenSprite.gif|center]] | |
| − | + | For a template, Alan Caudel broke down Seibu Kaihatsu's seminal ''Raiden'' series and tried to put it back together again. It was a good choice; the ''Raiden'' games are about as pure as a shooter comes. All you do is fly, dodge bullets, shoot enemy targets, and drop the occasional bomb. Power-ups are a simple affair that mostly just change your shot patterns. | |
| − | |||
[[File:raiden2.PNG|thumb|320px|Screenshot from Raiden II'']] | [[File:raiden2.PNG|thumb|320px|Screenshot from Raiden II'']] | ||
| − | + | So with that game as his model, Caudel came to focus on its main action: shooting. There are two components here; outgoing shots, and incoming ones. Game-Maker makes both of these a little twitchy, but one far easier than the other. | |
| − | + | On the player's end, the ship has a choice of several shot patterns: bullets might go straight ahead, or spread like a fan, or other shapes and with different numbers of bullets per keypress. What should happen here is that as you collect power-ups you get to increase the power (i.e., bullet count) of your current shot pattern, or you pick a different pattern. | |
| − | + | Although Caudel did a marvelous job at tracing bullet paths and layering them to create different shot levels, Game-Maker's design ensures that the upgrade path does not take the most logical route. In Character Maker, actions that use the same keystroke are tiered in priority. If you can do action 1, you do it; otherwise you do action 2, and so on. The variables that determine whether you can do an action are whether you have enough of the unique associated shot counter, whether you have the correct inventory item, or both. There is no ambiguity; if you fulfil the requirements, you will always do that action. You can't, for instance, select another inventory item or get a new power-up to switch actions -- unless that power-up knocks you up a level, qualifying you for a "better" action. | |
| − | + | Even for levels of a single shot pattern, this structure causes problems. Each power-up you get can only increase a single counter, and each action has its own counter -- and the thing those counters determine is how many shots you have. Furthermore, Game-Maker does not display most counters in-game, so the player will never have a good idea how many shots are left. The best solution within an individual pattern, then, would be to layer power-ups on top of each other; each power-up would increase one counter of that pattern by a set amount, and the player would automatically use the strongest. When those shots were expired, the second-strongest would take over, and so on. This is a weird behavior, and far from ideal -- but just wait until different shot patterns get involved. | |
| + | Basically, there is no way to dynamically switch weapons and increase the power of those weapons. So, what to do? The only thing available: assign each shot type to a different key. It's not elegant, but at least you'll get to use all the shot types. Maybe you can design a game that works around this concept, rather than trying to force a logic that will never work. Roll with the punches. Maybe in a follow-up project Caudel would have done just that. Here, we have an experiment. | ||
| − | + | The experiment continues with enemy shots. | |
Shooting monster solution developed independently from ''[[Andy in Asunderland]]''. | Shooting monster solution developed independently from ''[[Andy in Asunderland]]''. | ||
| − | + | bomb and death animations: nicely done. | |
| + | Other issues: firing while moving. In this experimemt enemy planes have no behavior to speak of, but games like ''[[Pipes]]'' and ''[[Ego Force]]'' ably fill in that blank. | ||
== Story == | == Story == | ||
Revision as of 06:20, 2 September 2016
Release type: Incomplete
Release date: 1994
Levels: 1
Author: Alan Caudel
Website: DummyDuck.com
Related games: N/A
FULL ENTRY COMING SOON!
A successful life is about hacking the system: working out how to do stuff with what limited resources you have, without regard to proper procedure. And hacking is about probing; feeling out the cracks in the system, watching what drips through, testing your whims and theories, and building your own meta-filter to slot on top.
Game-Maker's system is made for top-down adventure games like The Legend of Zelda; if you try something else, you're going to meet resistance. Try to make a shooter, and the system will say to you, that's a strange sort of adventure game. It will run what you plug into it, but it won't know what you're trying to do.
So, most scrolling shooters are kind of a mess on this engine. What Raiden II does a bit differently is it takes a step back to think about what it feeds into the engine and how that will be understood, then adapts its input accordingly.
For a template, Alan Caudel broke down Seibu Kaihatsu's seminal Raiden series and tried to put it back together again. It was a good choice; the Raiden games are about as pure as a shooter comes. All you do is fly, dodge bullets, shoot enemy targets, and drop the occasional bomb. Power-ups are a simple affair that mostly just change your shot patterns.
So with that game as his model, Caudel came to focus on its main action: shooting. There are two components here; outgoing shots, and incoming ones. Game-Maker makes both of these a little twitchy, but one far easier than the other.
On the player's end, the ship has a choice of several shot patterns: bullets might go straight ahead, or spread like a fan, or other shapes and with different numbers of bullets per keypress. What should happen here is that as you collect power-ups you get to increase the power (i.e., bullet count) of your current shot pattern, or you pick a different pattern.
Although Caudel did a marvelous job at tracing bullet paths and layering them to create different shot levels, Game-Maker's design ensures that the upgrade path does not take the most logical route. In Character Maker, actions that use the same keystroke are tiered in priority. If you can do action 1, you do it; otherwise you do action 2, and so on. The variables that determine whether you can do an action are whether you have enough of the unique associated shot counter, whether you have the correct inventory item, or both. There is no ambiguity; if you fulfil the requirements, you will always do that action. You can't, for instance, select another inventory item or get a new power-up to switch actions -- unless that power-up knocks you up a level, qualifying you for a "better" action.
Even for levels of a single shot pattern, this structure causes problems. Each power-up you get can only increase a single counter, and each action has its own counter -- and the thing those counters determine is how many shots you have. Furthermore, Game-Maker does not display most counters in-game, so the player will never have a good idea how many shots are left. The best solution within an individual pattern, then, would be to layer power-ups on top of each other; each power-up would increase one counter of that pattern by a set amount, and the player would automatically use the strongest. When those shots were expired, the second-strongest would take over, and so on. This is a weird behavior, and far from ideal -- but just wait until different shot patterns get involved.
Basically, there is no way to dynamically switch weapons and increase the power of those weapons. So, what to do? The only thing available: assign each shot type to a different key. It's not elegant, but at least you'll get to use all the shot types. Maybe you can design a game that works around this concept, rather than trying to force a logic that will never work. Roll with the punches. Maybe in a follow-up project Caudel would have done just that. Here, we have an experiment.
The experiment continues with enemy shots.
Shooting monster solution developed independently from Andy in Asunderland.
bomb and death animations: nicely done.
Other issues: firing while moving. In this experimemt enemy planes have no behavior to speak of, but games like Pipes and Ego Force ably fill in that blank.
Contents
Story
N/A
Instructions
There are weapon upgrades which flash yellow and blue scattered around the map. Which weapon you get depends on what color the block is when you pick it up. Yellow weapons have a wider spread range, but require repeated button pressing. Blue weapons have a more narrow range but you can down the button for automatic firing. There are three level upgrades for each weapon.
For best results, use the numerical keypad.
- Arrow keys: Move your ship.
- Q: Fire first level cannons.
- W: Fire second level cannons.
- E: Fire third level cannons.
- B: Drop a bomb.
Credits
Game designed by Alan Caudel.
Background
Alan Caudel:
- One of the hard parts about making this game was making tanks that shoot at you, and then stop shooting once you blow them up. It required a background block that generated a "bullet" monster block, which was covered by a tank monster block.
- If I remember correctly, the tank and the bullet had to be the same level or else one would kill the other upon contact. Then when the tank was destroyed, it was replaced with a "destroyed tank" monster block which was a higher level, and destroyed the bullets which kept generating from the background block underneath, so the destroyed tank would no longer fire bullets at you. This took a while to figure out how to get it working correctly, but I think the end result was good enough.
- Also, I think I had a problem where if you flew over the destroyed tanks, you could still die if a bullet block generated and you touched it in the split second before the "destroyed tank" block killed the bullet. So... I had to make the destroyed tank monster blocks solid. That was kind of a hassle, because it meant the jet couldn't fly over a destroyed tank without running into it. But I sacrificed realism for playability I guess.
Availability
This game is not known to have been distributed in any form, prior to its addition to the Archive.
Archive History
There are two known versions of Raiden II, both very incomplete but one more developed than the other.
On October 20th, 2010, Alan Caudel commented on a YouTube clip of Peach the Lobster, mentioning that he had used RSD Game-Maker. On December 7th the site contacted Caudel for further comment. At that time he was uncertain if his Game-Maker material still existed.
On June 29th 2011, Adam Tyner located and passed on to Caudel a selection of his, Caudel's, and Yurik Nestoly's old games, including the simpler version of Raiden II. That version was uploaded to the archive on July 5th.
Later on July 13th, Caudel found and offered up a further selection games, including the second and more advanced version of Raiden II. After some restoration, that version of the game was uploaded to the Archive on January 28th, 2012.
Links
Downloads
- Raiden II (89.1 kB)
- Raiden II (older version) (84 kB)
- Game map (older version) (11 kB)
