Overview
This prompt creates a development plan for a classic arcade-style shooter game. It benefits game developers and programming students learning to structure game projects.
Game Mechanics
* Core Loop: Player controls a laser cannon to shoot descending aliens while avoiding bombs and managing bunker cover.
* Collision Detection: Implement bounding-box checks for lasers vs. aliens, lasers vs. bombs, and all projectiles vs. bunker segments.
* Game State: Manage active game objects (player, aliens, projectiles, bunkers), score, lives, and level progression.
Player Features
* Control: Horizontal movement (left/right arrow keys or A/D) with screen boundary limits.
* Shooting: Press spacebar to fire a single laser projectile; implement a cooldown to prevent rapid-fire spam.
* Lives: Start with 3 laser cannons (lives); lose one upon bomb impact.
Alien Behavior
* Formation: A grid of aliens moves horizontally as a group, descending one row upon hitting screen edges.
* Bombing: Random alien in the bottom row periodically drops a bomb that falls vertically.
* Speed: Alien movement speed increases slightly as their total number decreases.
Bunkers
* Structure: Each bunker is composed of a destructible pixel grid or small health blocks.
* Damage System: Both alien bombs and player lasers degrade contacted bunker blocks, creating permanent holes.
Game Over Conditions
- Loss: Any alien reaches the bottom screen line OR the player loses all three lives.
- Win: The player destroys all aliens in the formation, potentially triggering a new, faster level.
Implementation Suggestions
* Use a game loop with fixed time steps for consistent updates.
* Employ a 2D framework like PyGame (Python), Unity 2D, or JavaScript with HTML5 Canvas.
* Manage objects using lists or arrays for easy iteration and cleanup of destroyed entities.
* Render bunker damage by tracking the health state of each segment in a 2D array.
Bonus Answer: This concept is directly based on the classic 1978 arcade game Space Invaders by Taito, where players defend against descending alien rows using a movable laser base and destructible shields.
Prompt Overview
Purpose: Create a retro-style arcade shooter with defensive elements.
Audience: Players seeking classic, straightforward action gameplay.
Distinctive Feature: Destructible bunkers that degrade from all fire.
Outcome: A complete, playable game with clear win and loss states.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Video Game Development
- Techniques: Decomposition, Structured Output, Role/Persona Prompting
- Models: GPT-4, Claude 3 Opus, Llama 3.3 70B
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
Create a detailed plan for developing a computer game featuring a laser cannon controlled by the player at the bottom of the screen, which can move left and right. The game should include multiple aliens that move horizontally and descend from the top of the screen, periodically dropping bombs toward the player. The player must be able to shoot and destroy the aliens. The game should also have protective bunkers behind which the player can hide; these bunkers should degrade and get damaged by both alien bombs and the player’s own laser fire. Define the game’s losing conditions: if any alien reaches the bottom of the screen or if the player loses all three initial laser cannons, the game ends in a loss. Include suggestions on how to implement key mechanics such as movement, shooting, collision detection, bunkers’ damage system, and game state management.
Additionally, answer the bonus question: Does this game concept sound familiar? Provide context and the name of the classic game it resembles.
# Steps
– Outline player controls and laser cannon behavior.
– Define alien movement patterns and bomb-dropping mechanics.
– Design bunker structure and how damage is tracked and rendered.
– Establish collision detection between laser shots, aliens, bombs, and bunkers.
– Specify conditions for player lives and game-over scenarios.
– Recommend programming approaches and possible frameworks or libraries.
# Output Format
Provide a clear, structured plan formatted with markdown, including sections for “Game Mechanics”, “Player Features”, “Alien Behavior”, “Bunkers”, “Game Over Conditions”, and “Implementation Suggestions”.
Under the final section, answer the bonus question concisely with historical or cultural reference to the game concept.
Screenshot Examples
[Insert relevant screenshots after testing]
How to Use This Prompt
- Copy the prompt exactly as provided.
- Paste it into your preferred AI chat interface.
- Review the generated detailed game development plan.
- Use the structured sections to guide your programming.
- Refer to the implementation suggestions for technical approaches.
- Note the bonus answer identifying the classic game inspiration.
Tips for Best Results
- Game Mechanics
- – Movement: The player’s laser cannon moves horizontally along the bottom of the screen via left/right arrow keys or A/D keys, constrained within screen boundaries
- – Shooting: Pressing the spacebar fires a single laser projectile upward
- a cooldown prevents rapid-fire spam
- – Collision Detection: Use axis-aligned bounding box (AABB) checks for laser vs
- alien, laser vs
- bunker, bomb vs
- player, bomb vs
- bunker, and alien vs
- bottom screen edge
- – Game State: Manage game loop, score, lives, and level transitions
- pause/resume functionality is recommended
- Player Features
- – The player controls one laser cannon at a time, with three lives (cannons) total
- – The cannon respawns at the center after losing a life, with a brief invulnerability period
- – Score increases for each alien destroyed
- possibly more points for faster hits or combos
- Alien Behavior
- – A grid of aliens starts at the top, moving left/right as a group, shifting down a row when hitting screen edges
- – Each alien has a small random chance per game tick to drop a bomb that falls vertically
- – Alien movement speed may increase as their numbers decrease to raise difficulty
- Bunkers
- – Place 3-4 bunkers (simple sprite-based barriers) above the player, each with a health system (e
- g
- , a grid of destructible blocks)
- – Both alien bombs and player lasers reduce bunker health on collision, creating visual damage (e
- g
- , removing blocks or changing sprites)
- – Bunkers do not regenerate
- they are fully destroyed when health reaches zero
- Game Over Conditions
- – The game ends immediately if any alien reaches the bottom of the screen (same Y-coordinate as the player’s baseline)
- – The game also ends if the player loses all three laser cannons (lives)
- – A “Game Over” screen displays the final score and allows restart or exit
- Implementation Suggestions
- – Use a framework like PyGame (Python), Phaser (JavaScript), or Unity (C#) for rapid prototyping
- – Implement object pools for lasers and bombs to optimize performance
- – Separate game logic (model) from rendering (view) for cleaner code
- – Store bunker damage as a 2D array of block states for precise degradation
- Bonus Answer
- This concept is nearly identical to the classic 1978 arcade game Space Invaders by Tomohiro Nishikado
- It pioneered the fixed shooter genre, featuring a player-controlled laser cannon at the bottom, rows of descending aliens that drop bombs, and destructible bunkers for cover
FAQ
- What are the player’s basic controls in the game?
The player can move the laser cannon left and right along the bottom of the screen and press a button to fire laser shots upward. - How do the aliens behave and attack?
Aliens move horizontally as a group, descend gradually, and randomly drop bombs downward toward the player’s position. - What is the purpose of the bunkers?
Bunkers provide temporary cover for the player, blocking both alien bombs and player shots, but they degrade upon hit. - How does the game end for the player?
The game ends if any alien reaches the bottom screen or if the player loses all three laser cannons.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (March 2026): Initial release.
