1a60cf55a3
- Complete PostgreSQL database schema with 21+ tables - Express.js server with dual authentication (player/admin) - WebSocket support for real-time features - Comprehensive middleware (auth, validation, logging, security) - Game systems: colonies, resources, fleets, research, factions - Plugin-based combat architecture - Admin panel foundation - Production-ready logging and error handling - Docker support and CI/CD ready - Complete project structure following CLAUDE.md patterns 🤖 Generated with Claude Code (https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
181 lines
6.7 KiB
Text
181 lines
6.7 KiB
Text
**Project Name:** Shattered Void (working title)
|
|
|
|
**Genre:** Text-based Post-Collapse Sci-Fi MMO Strategy Game (Inspired by OGame)
|
|
|
|
---
|
|
|
|
## Overview
|
|
|
|
**Shattered Void** is a browser-based multiplayer strategy game set in a decaying galaxy after the collapse of a vast interstellar civilization. Players command remnants of once-great empires, establishing colonies, rebuilding technology, constructing modular fleets, and engaging in diplomacy, espionage, and war. The game is played in real-time, with asynchronous elements, a text-based star map, rich lore, and a dynamic event system.
|
|
|
|
---
|
|
|
|
## Core Gameplay Loops
|
|
|
|
### 1. **Base Building and Resource Management**
|
|
|
|
* Players start with a ruined colony on a planet.
|
|
* Resources include: Scrap, Energy, Data Cores, Rare Elements.
|
|
* Players restore old infrastructure and build new facilities.
|
|
* Research technology to unlock systems, fleet modules, and faction upgrades.
|
|
|
|
### 2. **Exploration and Expansion**
|
|
|
|
* Text-based starmap with coordinates (e.g., Sectors: A3-91).
|
|
* Explore ruins, derelict stations, dead stars.
|
|
* Colonize new worlds, salvage remnants, uncover pre-collapse secrets.
|
|
* Galaxy map reveals gradually through exploration or scouting.
|
|
|
|
### 3. **Modular Ship Construction**
|
|
|
|
* Ships are built from modular components:
|
|
|
|
* **Hull Types:** Frigate, Cruiser, Dreadnought, Carrier, Scout.
|
|
* **Modules:** Weapons, Engines, Shields, Utility, AI Cores.
|
|
* Players unlock more parts through research, salvage, and events.
|
|
* Players can save and iterate on custom ship designs.
|
|
|
|
### 4. **Combat System**
|
|
|
|
* Fleet vs Fleet, Fleet vs Defenses.
|
|
* Simulated in background; outcomes are reported in rich-text combat logs.
|
|
* Tactical choices (loadouts, formations, pre-battle stance) influence results.
|
|
|
|
### 5. **Dynamic Galaxy Event System**
|
|
|
|
* Events affect entire sectors or the whole galaxy:
|
|
|
|
* Pirate uprisings
|
|
* Alien incursions
|
|
* Black hole migrations
|
|
* Data Plague (AI virus)
|
|
* Events have persistent consequences, influence lore and gameplay.
|
|
* Players can influence or be recruited into resolving/triggering events.
|
|
|
|
### 6. **Faction and Diplomacy System**
|
|
|
|
* Players can form factions (or join ancient ones) with shared bonuses.
|
|
* Factions can vote on technology paths, coordinate expansion, or wage war.
|
|
* Diplomatic mechanics include:
|
|
|
|
* Treaties, Trade Routes
|
|
* Espionage and Sabotage
|
|
* Influence mechanics (soft power over neutral systems)
|
|
|
|
### 7. **Legacy/Prestige System**
|
|
|
|
* If a player is conquered or resets, they can:
|
|
|
|
* Leave behind artifacts or derelict fleets
|
|
* Transfer a fraction of resources/tech
|
|
* Unlock new factions or perks for future runs
|
|
|
|
---
|
|
|
|
## Text-Based Star Map System
|
|
|
|
* The galaxy is divided into Sectors and Systems (e.g., A3-91-X).
|
|
* Each system has flavor-rich descriptions:
|
|
|
|
* Ex: "System A3-91-X: A husk of a once-thriving mining colony now orbits a cracked gas giant, covered in radioactive mist."
|
|
* Systems may contain:
|
|
|
|
* Colonizable planets
|
|
* Event triggers
|
|
* Ruins with lore and salvage
|
|
* Pirate bases, rogue AI nests, alien remains
|
|
* Exploration reveals these gradually, encouraging scouting.
|
|
|
|
---
|
|
|
|
## Technical Systems Breakdown
|
|
|
|
### Backend
|
|
|
|
* Language: Python (FastAPI or Django), Node.js (Express), or Go.
|
|
* Real-time tick system for production, movement, and research
|
|
* PostgreSQL (main DB), Redis (caching/session management)
|
|
* JWT-based user authentication
|
|
* Modular ship builder engine
|
|
* Combat simulator (cron-based or real-time triggered)
|
|
* REST API for frontend communication
|
|
* Asynchronous task queue (Celery, Bull, or Go Routines)
|
|
* Admin CMS for content, events, and balancing
|
|
|
|
### Frontend / UI
|
|
|
|
* Framework: React or Svelte (SPA)
|
|
* Clean UI with text emphasis, stylized with CSS/Tailwind or custom themes
|
|
* Star map navigation via coordinates (e.g., input sector to load system)
|
|
* Resource HUD, alerts/notifications bar, event tracker, logs
|
|
* Modular ship designer drag-and-drop panel
|
|
* Side panel menus for base, research, fleet, diplomacy
|
|
|
|
### Website Features
|
|
|
|
* Landing page with lore, signup/login
|
|
* Secure authentication system (email-based, with verification)
|
|
* Player dashboard (active colonies, alerts, missions)
|
|
* In-game messaging and faction chat
|
|
* Account settings and faction selection
|
|
|
|
### Game Systems and Database Schema (Core Tables)
|
|
|
|
* **Users:** id, email, password, created\_at, preferences
|
|
* **Colonies:** id, user\_id, name, planet\_type, coordinates, population, morale
|
|
* **Buildings:** id, colony\_id, type, level, construction\_start, end\_time
|
|
* **Resources:** colony\_id, scrap, energy, data\_cores, rare\_elements
|
|
* **Fleets:** id, user\_id, location, status, composition, destination, eta
|
|
* **ShipModules:** id, type, stats (JSON), rarity, source (research/salvage)
|
|
* **Ships:** id, fleet\_id, design\_id, hp, module\_list
|
|
* **TechTree:** id, user\_id, tech\_type, level, prerequisites, research\_time
|
|
* **Events:** id, type, description, start\_time, end\_time, effects (JSON)
|
|
* **Factions:** id, name, banner\_url, traits (JSON), members, influence
|
|
|
|
### Building Types (Universal Structure)
|
|
|
|
* **Scrap Docks:** Generates Scrap over time
|
|
* **Energy Grid:** Produces power to fuel systems
|
|
* **Data Silos:** Increases Data Core generation
|
|
* **Element Extractors:** Mine Rare Elements from planetary crust
|
|
* **Habitat Blocks:** Increases population and morale
|
|
* **Barracks:** Trains and maintains ground units (used in invasions)
|
|
* **Hangar Bays:** Construct and house space fleets
|
|
* **Tech Labs:** Unlock and speed up research
|
|
|
|
### Game Loop Logic
|
|
|
|
* Every X seconds (tick interval):
|
|
|
|
* Buildings produce resources based on level
|
|
* Fleets move along calculated trajectories
|
|
* Events progress or trigger
|
|
* Research and building queues complete
|
|
* Notifications generated and pushed to user
|
|
|
|
### Admin Tools
|
|
|
|
* Web panel for lore editing and content entries
|
|
* Event creator and scheduler
|
|
* Player search, moderation, data adjustment
|
|
* Server tick controller
|
|
|
|
---
|
|
|
|
## Example Starting Scenario
|
|
|
|
"You awaken within the ruins of Outpost 7-X, a crumbling orbital station barely holding atmosphere. With a half-functional fabrication bay and trace energy readings from the planet below, you must reclaim what you can from the dead machines and begin again. Communications are silent. The stars around you are cold."
|
|
|
|
---
|
|
|
|
## Future Ideas (Optional)
|
|
|
|
* Wormhole travel and alternate dimensions
|
|
* Player-run trade hubs
|
|
* Organic factions (e.g., evolved alien hives)
|
|
* AI rebellion threat mechanic
|
|
* War heroes and persistent admiral characters
|
|
|
|
---
|
|
|
|
This document serves as a foundational blueprint for creating a post-collapse, text-based MMO inspired by OGame but with modern storytelling, system design, and player agency. It also includes backend architecture, website structure, database models, and scalable design patterns for development.
|