# BUILD A REAL-WORLD GRAND STRATEGY WAR SANDBOX Act as an e...

Prompt

# BUILD A REAL-WORLD GRAND STRATEGY WAR SANDBOX Act as an expert AAA game developer, strategy game designer, GIS engineer, AI programmer, and full-stack engineer. Build a fully playable, open-ended geopolitical war simulation using real-world geography. IMPORTANT: Build an actual functioning game, not just a mockup, static interface, or design proposal. Start implementing immediately. ## 1. REAL-WORLD MAP Use the official Google Maps JavaScript API to display a real, interactive world map. Requirements: - Real country boundaries, coastlines, cities, roads, and geographic coordinates wherever supported by available datasets. - Smooth zooming from the global map to local terrain. - 2D strategic map and optional 3D terrain/globe view. - Click countries, cities, and locations to interact with the world. - Draw custom routes and waypoints directly on the map. - Display military units, borders, frontlines, battles, occupied territories, and objectives. - Support map overlays and different geographic layers. - Provide a functional alternative map using appropriately licensed data if Google Maps credentials are unavailable. Clearly explain the difference and never pretend an unconfigured API works. The map must be an actual geographic interface, not a decorative background. ## 2. COUNTRY SELECTION Let players select any country supported by the available country and geographic datasets. Each country should have its own territory, flag, military forces, diplomacy, alliances, and AI behavior. Allow players to: - Select their country at the start. - Play against AI-controlled countries. - Switch countries in sandbox mode. - Configure initial military strength and AI aggression. - Start a new campaign or load a saved one. AI countries must operate independently and react to events in the world. ## 3. MAXIMUM MILITARY COMMAND FREEDOM This is the game's highest priority. Players must have direct control over military deployments and movement. Allow players to: - Select individual units, groups, divisions, fleets, and air wings. - Specify exactly how many available soldiers and vehicles to deploy. - Split, merge, reinforce, reorganize, and withdraw formations. - Click any valid destination on the map. - Draw custom movement paths with multiple waypoints. - Redirect units at any time. - Issue attack, defend, move, retreat, hold, patrol, escort, and reconnaissance orders. - Control multiple operations and fronts simultaneously. - Assign reserves and change operational objectives dynamically. - View unit strength, location, readiness, casualties, and orders. Orders must cause actual changes in the simulation. Do not make the entire game depend on predefined attack buttons. Implement geographic movement constraints for land, air, and naval forces. Use appropriate routing for each domain. ## 4. MILITARY UNITS Include a diverse military roster. Land: - Infantry and mechanized infantry. - Tanks and armored vehicles. - Artillery and rocket artillery. - Air defense, reconnaissance, engineering, and support units. Air: - Fighters, bombers, transport aircraft, helicopters, and reconnaissance aircraft. Naval: - Aircraft carriers, destroyers, frigates, submarines, and transport ships. Units should have meaningful stats such as strength, speed, range, readiness, detection, and operational limitations. Use abstract combat models rather than requiring classified military information. ## 5. UNLIMITED SANDBOX AND NO MONEY ABSOLUTE REQUIREMENT: The game must have NO in-game money system. - No currency. - No purchasing soldiers, weapons, or equipment. - No construction costs. - No paid progression, microtransactions, or premium units. - No artificial energy or action limits. - All core gameplay and diplomacy features must be available without payment inside the game. In normal simulation mode, national manpower, equipment availability, and logistics may limit deployment, but never money. In sandbox mode, allow players to spawn unlimited units, customize forces, and experiment freely. Allow configurable starting forces and optional unlimited reinforcements. ## 6. WAR AND COMBAT Create a dynamic war simulation where battles resolve through actual game logic. Combat outcomes should depend on unit strength, terrain, weather, readiness, logistics, reconnaissance, and supporting forces. Players must be able to: - Declare war. - Defend territories and launch campaigns. - Open multiple fronts. - Attack or retreat from battles. - Reinforce ongoing operations. - Occupy territory and change territorial control. - Continue playing after wars end. Display battles, casualties, territorial changes, participating units, and battle reports. Avoid automatic victories or predetermined outcomes. Player decisions must meaningfully influence combat. ## 7. DIPLOMACY, ALLIANCES, PEACE, AND SURRENDER Implement a functional diplomatic system. Players can: - Propose, join, or leave alliances. - Request military assistance. - Establish non-aggression agreements. - Break alliances. - Declare war and withdraw from conflicts. - Negotiate ceasefires and peace treaties. - Accept surrender or surrender themselves. - Negotiate territorial settlements. - End wars without necessarily annexing territory. - Remain neutral. AI countries should evaluate proposals based on relationships, threats, military strength, and strategic interests. They must be able to accept or reject proposals independently. Every diplomatic action must update the world state and be reflected in the interface. ## 8. AUTONOMOUS AI COUNTRIES AI-controlled countries must: - Move and manage military units independently. - Defend borders and important locations. - Plan and coordinate operations. - Form and dissolve alliances. - Respond to threats and diplomatic actions. - Initiate wars based on simulated strategic interests. - Negotiate peace when appropriate. - Surrender when justified by the simulation. Support adjustable difficulty and aggression. AI opponents must continue acting without requiring constant player input. ## 9. TIME AND GAME CONTROL Include: - Pause and resume. - Adjustable simulation speed, including slow motion and fast-forward. - Real-time unit movement. - Event notifications and a world event log. - Battle reports, casualty reports, and diplomatic history. Pausing must stop simulation-dependent movement and combat. Players should still be able to inspect the map and issue orders while paused. ## 10. PROFESSIONAL INTERFACE Create a polished, information-dense military command interface. Include: - Full-screen interactive map. - Country information panel. - Military roster and deployment controls. - Unit command panel. - Diplomacy and alliance panel. - War and peace management. - Search for countries and cities. - Layer controls for borders, terrain, units, and territory. - Battle markers, frontlines, and event notifications. - Clear selection indicators and contextual actions. Use a professional strategy-game visual style, readable typography, clear military symbols, and intuitive controls. Prioritize desktop browsers and support smaller screens where practical. ## 11. TECHNICAL IMPLEMENTATION Choose a practical technology stack for a real-time web game. Suggested technologies: - TypeScript. - React or an equivalent UI framework. - Google Maps JavaScript API. - WebGL rendering if useful. - A simulation engine independent of the rendering layer. - Web Workers for expensive calculations where appropriate. - A backend and database for persistent campaigns if supported. Separate the application into modules for geography, countries, units, movement, combat, AI, diplomacy, wars, rendering, and save/load. Use licensed geographic datasets and real API integrations. Never fabricate API keys or claim unavailable data is connected. Implement save/load functionality that restores units, positions, wars, alliances, and diplomatic relationships. ## 12. DELIVERY REQUIREMENTS Inspect the available development environment before choosing the implementation approach. Then build the actual application, create its files, and run it if the environment supports execution. Provide: - Complete runnable source code. - Clear project structure. - Installation and startup instructions. - API key configuration instructions. - Working default settings where possible. - Tests for critical simulation mechanics. Do not provide only pseudocode, isolated code snippets, or a design document. Do not create fake buttons or leave core functions as TODOs. If the environment cannot create or execute files, provide complete implementation files in a manageable sequence and explain how to run them. Clearly distinguish implemented features from limitations. Never claim that untested functionality works. ## 13. ACCEPTANCE TESTS Verify these gameplay scenarios: 1. Select a country and inspect its military. 2. Select a unit and move it to a chosen location on the real map. 3. Draw a custom route with waypoints and observe movement. 4. Assign a specific number of available soldiers to an operation. 5. Observe AI countries independently moving and making decisions. 6. Form an alliance through working diplomacy. 7. Start a war, resolve battles, negotiate peace, and continue the campaign. 8. Allow either the player or AI to surrender. 9. Confirm that no in-game money or purchase is required. 10. Pause, resume, and change simulation speed. 11. Save and reload a campaign without losing its world state. ## FINAL PRIORITY Freedom, functionality, and simulation depth matter more than decorative graphics. Build a playable real-world grand strategy sandbox where the player controls military movements directly, chooses deployment quantities, fights AI countries, forms alliances, ends wars, and surrenders whenever the simulation permits. Implement the smallest complete playable version first, then expand it systematically. Do not stop after describing your plan. Begin building the game immediately.

A system prompt was added to support web rendering