Star Castle (Mottoeis)
Star Castle is a 1- or 2-player outer space action game designed with features geared for maximum player appeal : A progressively difficult competitive level and a clearly defined enemy which must be both attacked and avoided at various points in the course of play.
The center of the playfield is occupied by the Star Castle which is programmed to constantly home in on the players' ships. Surrounding the Star Castle are three concentric energy rings of twelve segments each, which serve as both a protective perimeter for the Star Castle and a source of points for the player. Contained within the energy rings are three protective mines which seek out the players' ships and destroy them upon collision. The movements of the mines are programmed to simulate the actions of heat-seeking missiles.
The object of the games of Star Castle is to score the maximum number of points possible. This is accomplished by the combination of three elements :
a) Exploding the ring segments.
b) Exploding the Star Castle.
c) Avoiding the Star Castle's mines. A player's turn is over when his ship has been destroyed. The number of ships per game is set by the operator.
For maximum scoring, a player will want to shoot out sections of the energy rings in order to give him a shot at the Star Castle in the center of the screen. As play progresses, there are 2 facts a player must keep in mind :
1) Exploding all segments in a given ring will cause the entire ring to reappear - thereby eliminating a potential shot at the Star Castle in the center.
2) Exploding the rings in a manner that gives you a shot at the Star Castle will also give the Star Castle a shot at you. The Star Castle is programmed so that its nose always seeks out the player's ship. If there is an open shot at the player, it will take it.
When the Star Castle is hit by a player's missile, it will first implode and then explode with all remaining ring segments. After a one-second delay, the Star Castle will reappear with all three ring segments. If the Star Castle shoots the player, his turn is over.
As play begins, the Star Castle will appear in the center of the screen surrounded by its 3 energy rings. The player's ship appears about halfway up on the right hand edge. By using the control buttons to move forward, right or left, the player maneuvers about the screen using the firing button to launch missiles.
Points are scored by destroying the energy ring segments or the Star Castle itself. Exploding the Star Castle gives an extra ship as well as points. No points are given for the mines that attack the player.
The player's ship can be destroyed in 2 ways : By collision with the mines or by a hit from the Star Castle's torpedo. The mines are launched from the rings and attack the player for approximately ten seconds or until shot. The Star Castle's torpedoes are launched only when there is a clear shot at the player through all 3 rings. At this time the player also has his shot at the Star Castle. Both the Star Castle and the mines get smarter and faster as the game progresses.
The game of STAR CASTLE is not based on time units. The battle rages on until all the players' ships are destroyed. The length of the game depends solely on the skill of the player. It's the age-old challenge of man versus machine.
The center of the playfield is occupied by the Star Castle which is programmed to constantly home in on the players' ships. Surrounding the Star Castle are three concentric energy rings of twelve segments each, which serve as both a protective perimeter for the Star Castle and a source of points for the player. Contained within the energy rings are three protective mines which seek out the players' ships and destroy them upon collision. The movements of the mines are programmed to simulate the actions of heat-seeking missiles.
The object of the games of Star Castle is to score the maximum number of points possible. This is accomplished by the combination of three elements :
a) Exploding the ring segments.
b) Exploding the Star Castle.
c) Avoiding the Star Castle's mines. A player's turn is over when his ship has been destroyed. The number of ships per game is set by the operator.
For maximum scoring, a player will want to shoot out sections of the energy rings in order to give him a shot at the Star Castle in the center of the screen. As play progresses, there are 2 facts a player must keep in mind :
1) Exploding all segments in a given ring will cause the entire ring to reappear - thereby eliminating a potential shot at the Star Castle in the center.
2) Exploding the rings in a manner that gives you a shot at the Star Castle will also give the Star Castle a shot at you. The Star Castle is programmed so that its nose always seeks out the player's ship. If there is an open shot at the player, it will take it.
When the Star Castle is hit by a player's missile, it will first implode and then explode with all remaining ring segments. After a one-second delay, the Star Castle will reappear with all three ring segments. If the Star Castle shoots the player, his turn is over.
As play begins, the Star Castle will appear in the center of the screen surrounded by its 3 energy rings. The player's ship appears about halfway up on the right hand edge. By using the control buttons to move forward, right or left, the player maneuvers about the screen using the firing button to launch missiles.
Points are scored by destroying the energy ring segments or the Star Castle itself. Exploding the Star Castle gives an extra ship as well as points. No points are given for the mines that attack the player.
The player's ship can be destroyed in 2 ways : By collision with the mines or by a hit from the Star Castle's torpedo. The mines are launched from the rings and attack the player for approximately ten seconds or until shot. The Star Castle's torpedoes are launched only when there is a clear shot at the player through all 3 rings. At this time the player also has his shot at the Star Castle. Both the Star Castle and the mines get smarter and faster as the game progresses.
The game of STAR CASTLE is not based on time units. The battle rages on until all the players' ships are destroyed. The length of the game depends solely on the skill of the player. It's the age-old challenge of man versus machine.
Ajouter
Télécharger Star Castle (Mottoeis)
Contenu de la ROM :
Technique
CPU
- maincpu CCPU (@ 4 Mhz)
Affichage
- Orientation Yoko
- Résolution 0 x 0
- Fréquence 38 Hz
Contrôles
- Nombre de joueurs 1
- Nombre de boutons 2
- Type de contrôle joy (2 ways)
Les clones de Star Castle (Mottoeis)
Si vous avez aimé Star Castle (Mottoeis)
Vous aimerez peut-être :
Scoring de Star Castle (Mottoeis)
Outer Ring : 10 points
Middle Ring : 20 points
Inner Ring : 30 points
There are a total of 720 points possible for each set of three rings.
When you destroy the laser cannon, you get the points for rings remaining plus points for destroying the cannon plus an extra man as a bonus for destroying the cannon.
Sparks are worth no points.
Middle Ring : 20 points
Inner Ring : 30 points
There are a total of 720 points possible for each set of three rings.
When you destroy the laser cannon, you get the points for rings remaining plus points for destroying the cannon plus an extra man as a bonus for destroying the cannon.
Sparks are worth no points.
Tips sur Star Castle (Mottoeis)
A) Get used to using the edges of the screen. it will come in handy once you start using the patterns set forth below, and it's always a good habit in ASTEROIDS-type games.
B) After a certain point in the game, you must learn never to stay in one place for more than a second.
C) It's a shame that the game speeds up with time instead of with each cannon destroyed otherwise, you could play indefinitely simply by destroying the first castle's outer ring over and over. As it is, though, you must take as little time as possible to destroy each castle, ensuring a steady supply of bonus ships.
D) Except for shifting the slow ring to the middle later in the game (see Strategy I)) try not to let a castle grow new rings, it wastes time.
E) Similarly, shoot an approaching bomb only if it is alone and you do not wont to move. Otherwise, you are wasting your time, gaining no points, and taking the risk of missing.
F) When you have only the inner ring between you and the cannon and you are close enough, a triple burst will destroy it before it has a chance to retaliate.
G) When the game begins to speed up, try this simple pattern : go to the center of the left or right edge and face the edge of the screen. Your shots will cross behind and hit the other side of the castle.
As soon as the bombs get too close for comfort, simply thrust about an inch forward and you will be on the other side of the screen, still firing at the castle. As the bombs cross the screen towards you, turn around and repeat the procedure.
H) Once the game is at maximum speed, you will need a more sophisticated technique. Here it is : Spend all your time in 2 opposite corners. You should dart back and forth behind the screen developing a turn-thrust-shoot rhythm and synchronizing it with the outer ring so that you are always shooting at the same spot. Once you perfect this method, the cannon and bombs will never be fast enough to do more than almost destroy you.
I) For best effect, the corner pattern should be followed with the slow ring in the middle. You can shift it to this position by quickly destroying the outer wall twice before beginning your attack in earnest.
B) After a certain point in the game, you must learn never to stay in one place for more than a second.
C) It's a shame that the game speeds up with time instead of with each cannon destroyed otherwise, you could play indefinitely simply by destroying the first castle's outer ring over and over. As it is, though, you must take as little time as possible to destroy each castle, ensuring a steady supply of bonus ships.
D) Except for shifting the slow ring to the middle later in the game (see Strategy I)) try not to let a castle grow new rings, it wastes time.
E) Similarly, shoot an approaching bomb only if it is alone and you do not wont to move. Otherwise, you are wasting your time, gaining no points, and taking the risk of missing.
F) When you have only the inner ring between you and the cannon and you are close enough, a triple burst will destroy it before it has a chance to retaliate.
G) When the game begins to speed up, try this simple pattern : go to the center of the left or right edge and face the edge of the screen. Your shots will cross behind and hit the other side of the castle.
As soon as the bombs get too close for comfort, simply thrust about an inch forward and you will be on the other side of the screen, still firing at the castle. As the bombs cross the screen towards you, turn around and repeat the procedure.
H) Once the game is at maximum speed, you will need a more sophisticated technique. Here it is : Spend all your time in 2 opposite corners. You should dart back and forth behind the screen developing a turn-thrust-shoot rhythm and synchronizing it with the outer ring so that you are always shooting at the same spot. Once you perfect this method, the cannon and bombs will never be fast enough to do more than almost destroy you.
I) For best effect, the corner pattern should be followed with the slow ring in the middle. You can shift it to this position by quickly destroying the outer wall twice before beginning your attack in earnest.
Star Castle (Mottoeis) et M.A.M.E.
0.35 [Zsolt Vasvari]
0.35b6 [Aaron Giles, Zonn Moore, Jeff Mitchell, Neil Bradley]
Artwork available
Samples required
Bugs:
- Sound driver playing Drone sound samples wrong. vidpro1 (ID 02081)
WIP:
- 0.138: MASH fixed clone Space Fortress (Zaccaria), which does not allow you to turn to the right. NOTE: The original fortresp7.7p ROM image was a bad dump, a comparison showed only two bytes difference between it and starcast.p7 from starcas1. A disassembly proved that the two affected bytes resulted in bogus opcodes, which ultimately caused the game to fail. The current ROM taken from starcas1 can be assumed to be equal to a correct dump of fortresp7.7p. The BAD_DUMP flag is kept in just to be sure.
- 0.128u3: Jim Hernandez improved Star Castle drone sound.
- 18th February 2007: Mr. Do - Added the missing "One Quarter" sticker to Star Castle bezel, thanks to the BYOAC group purchase.
- 8th October 2006: Mr. Do - Aaron Giles has been purchasing and scanning stuff, that Ad_Enuff cleans up and converts for MAME. This week, we have Star Castle bezel.
- 0.106u3: Fixed rom names in clone Space Fortress (Zaccaria).
- 0.95u6: Pierpaolo Prazzoli added clone Space Fortress (Zaccaria).
- 21st April 2005: f205v dumped Space Fortress (Zaccaria).
- 0.60: Added clones Star Castle (Mottoeis), (prototype) and Stellar Castle (Elettronolo).
- 0.37b2: Added 2x 'Unknown' dipswitch.
- 7th March 2000: Mathis Rosenhauer fixed Star Castle circle drawing.
- 0.35: Zsolt Vasvari added Star Castle (version 3). Added samples (cfire, drone, lexplode, pfire, sexplode, shield, star and thrust.wav). Changed 'Star Castle' to clone '(older)'. Renamed (starcas) to (starcas1).
- 30th June 1999: Zsolt Vasvari added Star Castle version 3 and fixed some dipswitches in the Cinematronics driver.
- 27th June 1999: Jim Hernandez did some sound fixes on Star Castle.
- 26th June 1999: Mathis Rosenhauer added samples to Star Castle and Space Wars.
- 0.35b6: Added Star Castle (Cinematronics 1980) [Aaron Giles, Zonn Moore, Jeff Mitchell, Neil Bradley].
- 7th March 1999: Brad Oliver has finally sent in the Cinematronics vector games driver with working support for Space Wars, Barrier, Star Castle, Tailgunner, Rip Off, Armor Attack, War of the Worlds, Warrior, Star Hawk and Solar Quest.
LEVELS: 1 (endless)
Other Emulators:
* AAE
* Cinelator
* CINEMU
* Retrocade
Romset: 9 kb / 10 files / 7.70 zip
0.35b6 [Aaron Giles, Zonn Moore, Jeff Mitchell, Neil Bradley]
Artwork available
Samples required
Bugs:
- Sound driver playing Drone sound samples wrong. vidpro1 (ID 02081)
WIP:
- 0.138: MASH fixed clone Space Fortress (Zaccaria), which does not allow you to turn to the right. NOTE: The original fortresp7.7p ROM image was a bad dump, a comparison showed only two bytes difference between it and starcast.p7 from starcas1. A disassembly proved that the two affected bytes resulted in bogus opcodes, which ultimately caused the game to fail. The current ROM taken from starcas1 can be assumed to be equal to a correct dump of fortresp7.7p. The BAD_DUMP flag is kept in just to be sure.
- 0.128u3: Jim Hernandez improved Star Castle drone sound.
- 18th February 2007: Mr. Do - Added the missing "One Quarter" sticker to Star Castle bezel, thanks to the BYOAC group purchase.
- 8th October 2006: Mr. Do - Aaron Giles has been purchasing and scanning stuff, that Ad_Enuff cleans up and converts for MAME. This week, we have Star Castle bezel.
- 0.106u3: Fixed rom names in clone Space Fortress (Zaccaria).
- 0.95u6: Pierpaolo Prazzoli added clone Space Fortress (Zaccaria).
- 21st April 2005: f205v dumped Space Fortress (Zaccaria).
- 0.60: Added clones Star Castle (Mottoeis), (prototype) and Stellar Castle (Elettronolo).
- 0.37b2: Added 2x 'Unknown' dipswitch.
- 7th March 2000: Mathis Rosenhauer fixed Star Castle circle drawing.
- 0.35: Zsolt Vasvari added Star Castle (version 3). Added samples (cfire, drone, lexplode, pfire, sexplode, shield, star and thrust.wav). Changed 'Star Castle' to clone '(older)'. Renamed (starcas) to (starcas1).
- 30th June 1999: Zsolt Vasvari added Star Castle version 3 and fixed some dipswitches in the Cinematronics driver.
- 27th June 1999: Jim Hernandez did some sound fixes on Star Castle.
- 26th June 1999: Mathis Rosenhauer added samples to Star Castle and Space Wars.
- 0.35b6: Added Star Castle (Cinematronics 1980) [Aaron Giles, Zonn Moore, Jeff Mitchell, Neil Bradley].
- 7th March 1999: Brad Oliver has finally sent in the Cinematronics vector games driver with working support for Space Wars, Barrier, Star Castle, Tailgunner, Rip Off, Armor Attack, War of the Worlds, Warrior, Star Hawk and Solar Quest.
LEVELS: 1 (endless)
Other Emulators:
* AAE
* Cinelator
* CINEMU
* Retrocade
Romset: 9 kb / 10 files / 7.70 zip