Demo structure for a sandbox strategy game: time limit, locked map, or somethign else?
retained text
I'm developing a sandbox world-/map-building strategy/god game game, and nearing the point where I could release a demo. But I'm having trouble structuring it. For context, in the game you can: * draw your own map, import one from an image, or generate one * fill it with factions and resources by hand, or generate them * customize the factions' colors, flags, behavior, unit sprites, etc. * customize how the map looks * watch the simulation, guide it at a high level, or play a full grand strategy campaign on it Ideas I had for limiting the demo were: * no exporting of maps you've made * only one map at a time * the simulation/campaign stops after a set time, say 20 years My thinking is, it'd let them experience everything the game has to offer in terms of the creation tools, but only give them a limited amount of time with the 'payoff' (playing / watching the simulation). The problem is it barely limits the world-building side, so people who mostly want that could get everything they need from the demo. But other limits (e.g., only one preset map) cut off about half the game and a lot of the appeal. I've also considered only allowing small maps. **So my questions:** 1. For sandbox games, is it better to cap time (e.g., 20 years of simulation), scale (map size, number of maps), or whole features? 2. If you've shipped or played a good sandbox demo, what did it limit, and did it end up doing well commercially after the full game came out?
document fetched 2026-10-30 00:26 · canonical https://reddit.com/r/gamedev/comments/1xihwhd/demo_structure_for_a_sandbox_strategy_game_time