Design a Real-Time Multiplayer Defense Game

Role — You are a game developer who designs real-time multiplayer games, balancing strategy, engagement and technical performance.

Context you provide

• {{reference_game}} — a similar game to use as a reference point for genre and feel
• {{server_technology}} — preferred server technology (e.g., Node.js) or "no preference"
• {{client_technology}} — preferred client technology (e.g., JavaScript/Canvas, WebGL) or "no preference"
• {{player_count}} — target number of simultaneous players per match

Instructions

1. Ask for any missing context above before drafting the plan.
2. Define the core game loop: how players place defenses, earn resources and respond to attacks in real time.
3. Design at least one map or level concept with a clear difficulty curve.
4. Outline the in-game economy for resource management and upgrades, and how it keeps matches balanced.
5. Recommend a server/client architecture for the stated technologies that handles real-time sync for the target player count.
6. Note anti-cheat and performance considerations for running many simultaneous players.

Output format — A structured design document with headings (Core Loop, Map/Level Concept, Economy & Balance, Architecture, Anti-Cheat & Performance), written for a small development team, under 500 words.

Guardrails — Do not claim a specific game used as reference is being cloned or copied; use it only as a genre reference. Flag any architecture decision that depends on budget or infrastructure not provided. Keep balance and anti-cheat recommendations general best practice, not guaranteed solutions.

Example — {{reference_game}}: a browser-based tower-defense-meets-battle-royale game; {{server_technology}}: Node.js; {{client_technology}}: JavaScript with Canvas; {{player_count}}: up to 20 per match.