Skip to content

Instantly share code, notes, and snippets.

@Stuyk

Stuyk/game-launch-blueprint.md

Last active July 2, 2026 21:04
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save Stuyk/5316651b12598525bdcef9c1640155c3 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save Stuyk/5316651b12598525bdcef9c1640155c3 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
game-launch-blueprint.md

Note: This document is constructed by literally just talking to an AI about a whole bunch of shit and having a one-on-one conversation about my thoughts and opinions on the process. This is the outcome of that.

Executive Timeline Overview

 MONTH  | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 |
--------+----+----+----+----+----+----+----+----+----+----+----+----+
 CORE   | [Concept]    |                                            |
 DEV    |    [Lock Core Loop]    |                                  |
        |              [Vertical Slice]    |                        |
        |                                       | [Content Grind]   |
--------+----+----+----+----+----+----+----+----+----+----+----+----+
 MKTG & |              [Grassroots Marketing & Devlogs............] |
 WEB    |                        [Steam Store Page Live...........] |
        |                                       | [Trailer/Stream]  |
--------+----+----+----+----+----+----+----+----+----+----+----+----+
 DEMO & |                                  [Demo Lock]              |
 FEST   |                                       | [Demo Live]       |
        |                                            |[Next Fest]   |
--------+----+----+----+----+----+----+----+----+----+----+----+----+
 SHIP   |                                                      | [X]|

(X = Final Polish & Launch Window)

Phase 1: Core Foundation & Systems (Months 1–3)

Objective: Prove the concept works and lock down the mechanical loop before building secondary systems.

Month 1: Conception & Immediate Execution

  • Establish Scope Constraints: Define the core hook of the game immediately. The game must be targetable for a final scope of 2 to 3 hours of gameplay.

  • Begin Coding Immediately: Avoid architectural over-engineering. Focus entirely on structural framework prototyping.

  • Asset Philosophy: Use placeholder blocks, simple geometry, or basic asset packs. Visual fidelity is irrelevant at this stage.

Months 2–3: The Core Loop Filter

  • Lock the Game Loop: By the end of Month 3, a player must be able to experience exactly one complete loop of the game.

  • Example: If making a movement shooter, the player can spawn, clear an arena using baseline weapons, trigger an end-of-combat condition, and reset.

  • The Scope Gate: If the core loop is not completely dialed in and playable by day 90, the project has spiraled out of control. Chop features or pivot immediately to preserve the 12-month timeline.

Phase 2: Visibility & Grassroots Traction (Months 4–5)

Objective: Pivot an unpolished game into a visually striking vertical slice and build automated community-building pipelines.

The Vertical Slice Sprint

  • Polish for the Camera: Dedicate these two months to building a small, hyper-polished segment of the game. Focus on animations, visual impact, juice, and lighting. It does not need to be final asset quality, but it must look compelling in motion.

  • Visual Assets: Capture crisp GIFs, high-resolution screenshots, and a beautiful key art capsule image.

Low-Friction Marketing Routine

Marketing at this stage should not interrupt development flow. Treat it as a quick, unedited documentation habit.

  • The 10-Minute Habit: Take a screenshot or grab a quick 10-second clip of whatever feature you just coded.

  • Omnichannel Deployment: Instantly post it across all major distribution hubs:

  • Microblogging: Twitter, Bluesky (use relevant hashtags like #gamedev, #indiedev, #screenshotsaturday).

  • Communities: Reddit (specific subreddits matching the genre), Discord.

  • Video: YouTube (Devlogs showing the authentic development journey).

  • Authenticity Over Production: Audiences connect with the raw engineering and design journey. Show failures, unexpected bugs, and rapid iterations to build early evangelism.

  • The Network Push: Explicitly reach out to friends, professional contacts, and peer networks. Every initial wishlist acts as a positive heuristic for the Steam algorithm to favor your project.

Month 5 Milestone: Steam Page Launch

  • Go live with the Steam store page using the polished vertical slice assets.

  • The page serves as a landing net for all ongoing grassroots marketing efforts to accumulate wishlists early.

Phase 3: The Playable Demo & Steam Next Fest (Months 6–9)

Objective: Prepare a high-fidelity demo, deploy telemetry-driven feedback systems, and maximize Next Fest visibility.

+--------------------------------------------------------+
|          Automated Feedback & Telemetry Loop           |
|                                                        |
|   [ Player Demo ] ---> [ In-Game Form ]                |
|                              |                         |
|                              v                         |
|                      [ Discord Webhook ]               |
|                              |                         |
|                              v                         |
|               [ Immediate Developer Iteration ]        |
+--------------------------------------------------------+

Month 8: The Pre-Fest Demo Lock (1 Month Prior)

  • Build an Ironclad Demo: The demo should contain roughly 20 to 30 minutes of your tightest, most engaging gameplay loop.

  • Bake in Feedback Mechanisms: Do not rely on players opening a browser. Code an explicit feedback form directly into the game UI that pushes data instantly via Discord Webhooks or a lightweight database.

  • Trailer Delivery: Finalize and polish your official participation trailer. It should show direct, gameplay-focused action within the first 5 seconds.

Month 9: Steam Next Fest Execution

  • The Golden Rule: You only get one Next Fest opportunity per app ID. If the demo is unstable or lacks hook value 30 days before the fest, pull out immediately and defer to the next event calendar. Do not rush an unpolished demo.

  • Storefront Automation: Utilize RoboStreamer (https://robostreamer.com/) to host a 20-30 minute high-action gameplay video on a continuous loop. This ensures your Steam store page displays active livestream badges and high-intensity visuals to every casual browser 24/7 during the festival window.

  • Iterative Hotfixing: Continuously patch bugs, tune balance, and deploy updates throughout the event based on your real-time Discord webhook feedback pipeline.

Phase 4: The Content Grind & Ship (Months 10–12)

Objective: Leverage established core mechanics to produce content arrays rapidly, achieve polish targets, and push the release button.

Months 10–11: Asset Reutilization & Grind

  • Systemic Content Production: The structural engine, rendering, and tool pipelines are completely finished. This phase is pure content execution—grinding maps, encounters, modifiers, and progression loops.

  • Maximize Reuse: Do not write new code systems. Use your established asset libraries, material sets, and modular architecture to assemble content predictably.

  • Target Scope: Aim for exactly 2 to 3 hours of high-density, highly polished gameplay. For a premiere project within a 12-month lifecycle, this scope provides exceptional value while ensuring the game actually crosses the finish line.

Month 12: The Launch Window

  • Execute Steam backend submission checks.

  • Finalize regional pricing adjustments across global economic zones.

  • Transition the store page from "Wishlist" to "Buy Now" and execute the release.

Core Tooling & Technical Infrastructure

  • Steamworks SDK: Build target integration.

  • RoboStreamer: Automated 24/7 store streaming infrastructure.

  • Discord Webhooks: Native in-game feedback piping for friction-free bug tracking.

  • Social Vectors: Twitter, Bluesky, YouTube, Reddit, Discord.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment