Made with Nano Banana 2 Lite · CC0 · 2 Oct 2026

Flat colour

Generated from: a scene from a small video game about: build a mobile, real-world-based geopolitical strategy game. Players take control of a nation, expand through real-world provinces, and attack other players' nations. ## 1. CORE CONCEPT - The real world is the game board. Every country is split into its real administrative divisions (provinces, states, regions, departments, oblasts, prefectures, counties). Use the finest level available (ADM1, and ADM2 where it makes sense) so the world has thousands of provinces (target: 4,000+). - Each player picks or is assigned a nation and rules it. Players can also capture provinces belonging to other players or to AI-controlled nations. - The game is persistent: one shared world, running 24/7, with seasons/rounds that end with a winner and a reset. ## 2. IRL / LOCATION-BASED MECHANICS - GPS: physically being in or traveling through a province gives that province bonuses (resource generation, faster troop training, scouting vision). - Walking/steps convert into "logistics points" used to move armies. - Visiting a province that belongs to an enemy lets you spy on it or start a "ground-contact siege" that weakens its defense. - Real-world events (weather, time of day, day/night) modify provinces (e.g. snow slows armies, night grants stealth). - Anti-cheat: detect GPS spoofing, emulators, mock-location apps, teleporting. Provide a "remote play" mode with weaker bonuses so people who can't travel can still compete. - Strict safety rules: no mechanic ever requires entering dangerous, private, restricted, or military areas. Include a warning system, and cap rewards for rapid movement (no driving-based exploits while in a vehicle). ## 3. NATION MANAGEMENT - Resources: money, food, oil/energy, manpower, steel/industry, tech. - Each province has stats: population, economy, terrain, infrastructure, stability, strategic resource, defense level. - Nation-level systems: government type, laws, taxes, research tree, diplomacy, national morale, war exhaustion. - Buildings per province: barracks, factory, farm, fortress, airfield, port, research lab, radar. ## 4. MILITARY & COMBAT - Unit types: infantry, armor, artillery, air, navy, special forces, cyber, missiles (limited), plus spies and diplomats. - Attack flow: declare war -> pick target province -> assign units -> travel time based on distance -> battle resolves with a transparent formula (attack, defense, terrain, supply, morale, tech, randomness) -> province captured or defended. - Battles resolve asynchronously (players can be offline). Defenders get push notifications and a window to reinforce. - Fog of war: you only see provinces you own, border, or have scouted. - Occupation system: captured provinces need garrison and stability or they rebel. - Balance tools: war-declaration cooldowns, protection for new players, anti-snowball mechanics, coalition bonuses for underdogs. ## 5. DIPLOMACY & SOCIAL - Alliances, non-aggression pacts, trade deals, embargoes, sanctions, UN-style global council votes. - Alliance chat, shared maps, joint wars, coordinated attacks. - Global leaderboard: nations, alliances, individual players. ## 6. WORLD MAP & DATA - Use real open geodata (Natural Earth, GADM, OpenStreetMap, geoBoundaries) for province boundaries. Explain licensing for each. - Render with a vector map SDK (Mapbox, MapLibre, or Google Maps), province borders as polygons colored by owner, zoom levels: world -> country -> province. - Handle disputed borders neutrally (configurable per region, no political statements). - Pre-compute adjacency graph between provinces for pathfinding and borders. ## 7. TECH STACK (propose and justify, then implement) - Client: Flutter, React Native, or Unity (pick one and explain why). - Backend: server-authoritative (Node/TypeScript, Go, or Kotlin), PostgreSQL + PostGIS for geodata, Redis for real-time state, WebSockets for live updates. - Game loop: tick-based simulation on server, event queue for movement/battles. - Push notifications, analytics, cloud hosting, CI/CD. - Everything validated server-side; the client never decides outcomes. ## 8. MONETIZATION (ethical) - Cosmetics: flags, skins, map themes, unit visuals. - Optional battle pass and speed-ups with strict pay-to-win limits. - No loot boxes. Clear, honest pricing. ## 9. LEGAL, SAFETY & PRIVACY - Location privacy: never show exact player positions to others, only the province level, with delays. - Age rating, GDPR/COPPA considerations, content moderation for chat. - Avoid real-world harm: fictionalize conflicts, don't use real ongoing wars as gameplay scenarios, no real-person leaders without permission, no hateful content. ## 10. DELIVERABLES (produce in this order) 1. One-page game design document (pillars, target audience, unique hook). 2. Full systems design (economy, combat formulas, progression, balance numbers). 3. Data model / database schema for provinces, nations, units, battles. 4. Architecture diagram and API spec. 5. Step-by-step MVP plan: what to build in 2 weeks, 2 months, 6 months. 6. Working MVP code: map screen with real provinces, nation selection, province capture, one unit type, attack resolution, GPS bonus. 7. Risks, cheating vectors, and how to mitigate each. 8. A list of 20 creative features that would make this game go viral., as an in-game screenshot in flat colour 2D shapes with a bright limited palette. Palette: sky blue #8ecae6, grass #3a7d44, player sunflower #ffb703, threat red #d62828, accent white #fdfcdc. Everything is original: never draw or resemble characters, places or logos from existing games, films or brands (no red-capped plumbers, no famous mascots), even when the idea names one. Keep the pictures honest: they promise what a small first version of this game, made in a game engine in a few days, can look like. Simple readable shapes, clear silhouettes, few flat materials, the in-game camera view. Never film stills, photoreal renders, AAA key art, detailed textures, cinematic lighting, or anything that looks like a big-studio game. No text, UI, HUD, logos or editor screens inside any image.