Start Building
Challenge/community hook May 11, 2026

7-Day Vertical Slice Demo Challenge for Steam Next Fest October 2026 - One Build Quality Gate per Day Before Festival Submission

Run this 2026 seven-day Steam Next Fest October submission-week drill - one demo polish quality gate per day covering scope freeze, first 60 seconds, fuzz pass, store-page parity, controller glyph, Steam Input default config, and traffic spike rehearsal.

By GamineAI Team

Knight Ninja Character artwork - hero image for the 7-day vertical slice demo challenge for Steam Next Fest October 2026

Why this matters now

Steam Next Fest October 2026 opened its submission window in early September with a tighter metadata gate than any previous Next Fest, and Q3 2026 stacked three other partner pressures on top of the festival: Gamescom-adjacent partner reviews, the Steam autumn Deck Verified refresh with tightened controller glyph and Steam Input action-set rules, and the Meta holiday window opening earlier than usual. A demo that ran clean for the August closed test will not automatically clear October's gates.

The teams who turn the festival traffic into wishlists are not the teams who shipped the most content in October. They are the teams who rehearsed the full polish stack on a fixed cadence in the final week so the demo behaves predictably when ten thousand strangers click play.

This challenge is the seven-day final-week drill. One quality gate per day. Each day produces a single pass-fail artifact you can stick to the demo branch as evidence the gate ran. By Day 7 the demo branch metadata, controller-glyph parity, store-page parity, retention funnel instrumentation, and traffic-spike rehearsal all match the binary you are about to flip visible.

If you are still six weeks out, read Steam Next Fest October 2026 Timeline - What to Lock 6 Weeks Before Demo Launch first - this challenge runs inside the last week of that timeline. If you already love daily release-week discipline, pair this with the 7-Day Release Candidate Freeze Challenge (2026) so demo quality and partner upload governance reinforce each other instead of fighting.

Who this challenge is for

  • 2-8 person indie teams shipping a Steam demo for Next Fest October 2026.
  • First-time Next Fest teams who treated August's closed-friends test as confirmation that the build is "ready."
  • Returning teams whose previous Next Fest demo bled refunds on a controller-glyph bug, a crash-on-first-pickup, or a Steam Input default config no one verified.
  • Anyone whose October calendar still has more "I think we're fine" than "I have a screenshot of the green gate" on it.

What you will produce by Day 7

  • A demo branch with frozen scope, identity, and metadata - no last-minute additions, no parallel test branches mid-traffic.
  • A first 60 seconds that hooks players without a tutorial wall.
  • A crash and soft-lock fuzz pass with a regression-seed corpus that the demo never crashes against.
  • Store page parity between capsule, screenshots, trailer first 6 seconds, and what the demo actually shows in its opening minute.
  • Controller glyph parity for Xbox, Xbox Elite, PlayStation, and Steam Deck (LCD and OLED) under the autumn 2026 Deck Verified refresh.
  • A Steam Input default config validated on the demo branch, not just the main branch.
  • A traffic-spike rehearsal with retention funnel instrumentation that survives a Steam featuring shelf placement.

Beginner Quick Start - vocabulary you will use all week

If "demo branch" and "Steam Input default config" are new phrases, memorize four terms before Day 1:

  • Vertical slice - the narrow, polished, end-to-end gameplay slice the demo represents. Not a level. Not a build. The shippable thirty-to-sixty minutes that prove the game.
  • Demo branch - the depot branch on Steamworks tied to the Next Fest visibility toggle. Separate from default. It has its own metadata, its own controller config folder, and its own SteamPipe promotion path.
  • Steam Input default config - the VDF action manifest that Steam picks up the first time a player launches the demo on any controller. Missing or mismatched on the demo branch is the single most common autumn 2026 submission rejection.
  • Controller glyph - the on-screen button image (A, X, square, etc.) for the actively connected controller. The autumn 2026 Deck Verified refresh tightened glyph identity rules so generic Xbox glyphs cannot stand in for Xbox Elite or PlayStation DualSense Edge prompts anymore.

Three more terms that prevent mid-week arguments:

  • Featuring shelf placement - the visibility lane Valve allocates to a demo during Next Fest. Whether or not your demo gets one is a Valve decision, but the traffic spike on Day 1 of the festival assumes you might.
  • Retention funnel - the ordered stage gates of player experience: download, launch, past-title-screen, first-input, first-pickup, first-checkpoint, finish-demo. Each one drops players. The point of instrumentation is to know which step bleeds, not just total.
  • Regression-seed corpus - the small set of inputs (save files, input sequences, controller hot-swaps) you preserved from previous bug reports that the demo must not crash against.

The challenge format

  • Time per day: 90 minutes to 4 hours, depending on team size and how much pre-work you did during the 6-week plan.
  • Owner per day: Assign one named owner per gate before Day 1. Shared ownership is how Day 5 silently does not happen.
  • Artifact per day: Each gate produces one pass-fail file or screenshot you stick in a shared final-week-evidence/ folder. By Day 7, the folder is the evidence the gate ran.
  • Refusal rule: If a gate fails, do not stack a new gate on top of it. Resolve or formally accept the failure with a documented carve-out before moving on. The refusal-to-stack rule is what keeps the challenge honest.

Day 1 - Scope freeze

Goal: End the day with a written list of what is in the demo and what is out, signed by every team lead, with no ambiguity about either column.

What "out" means: No partial features. No "we'll patch it during the festival." No "if there's time on Wednesday." The festival traffic spike on Day 1 of Next Fest is when your reputation lands; this is not the week to introduce a new mechanic and hope.

Gate steps:

  1. List every gameplay system in the current demo build (combat, movement, save, dialogue, etc.).
  2. For each system, mark GREEN (ship as is), YELLOW (fix this week), or RED (cut from demo).
  3. For every RED, either delete the code path the demo touches or feature-gate it off with a hard-coded false. Soft-deleting is worse than hard-deleting because YELLOW always wants to creep back to GREEN.
  4. Producer signs the scope sheet.

Artifact: final-week-evidence/day-1-scope.md - the GREEN/YELLOW/RED table plus producer signoff line.

Common failure mode: A YELLOW that secretly should have been RED. If a system needs more than one focused day of polish to ship, it is RED.

Day 2 - First 60 seconds player onboarding pass

Goal: Five new playtesters (friends-of-friends, not your team) can each pick up the controller, start the demo, and play meaningfully within 60 seconds of pressing A on the title screen.

The Next Fest traffic spike has no patience for tutorial walls. A demo that bores players for 90 seconds before letting them act loses them.

Gate steps:

  1. Watch each playtester's first 60 seconds over their shoulder. Do not coach.
  2. Note the timestamp of: title screen acceptance, first character motion, first hostile encounter (or first meaningful interaction), first feedback the player understands.
  3. Compute the median of all four timestamps across the five playtesters.
  4. The gate passes if: title screen to first motion is under 8 seconds; first motion to first meaningful interaction is under 30 seconds; total to first satisfying feedback is under 60 seconds.

Artifact: final-week-evidence/day-2-first-60-seconds.md - the five timestamp tables + median + pass/fail.

Common failure modes:

  • Studio logo unskippable. Skip it. Always allow input to skip.
  • Tutorial text that demands reading. Replace with one icon hint or a non-blocking tooltip.
  • Title screen requires controller-detection sleep. Detect on the first button press and route from there.

If the gate fails, this is Day 2 work, not Day 5 work. Fix it today.

Day 3 - Crash and soft-lock fuzz pass

Goal: Run the demo against every saved bug report from the past three months plus a small property-based fuzz sweep, and emerge with a regression-seed corpus the demo cannot crash against.

Gate steps:

  1. Open your bug tracker. Filter to "closed" bugs in the last 90 days. Replay each one against the current demo branch. None should reproduce.
  2. If you have property-based fuzz tooling wired (see the upcoming save-system corruption fuzz resource list - linked from the new resource list when it ships), run a 10,000-iteration sweep on save load, input replay, and controller hot-swap.
  3. Test five specific controller hot-swap sequences: Xbox in/out, Xbox to PlayStation, PlayStation to Steam Deck dock, controller battery dies mid-input, two controllers connected simultaneously.
  4. Preserve every input that crashed or soft-locked as a permanent regression seed in final-week-evidence/regression-seeds/.

Artifact: final-week-evidence/day-3-fuzz-pass.md - bug-tracker rerun table + fuzz iteration count + crash count (should be zero) + controller hot-swap table.

Common failure modes:

  • A two-month-old "fixed" save corruption bug returns. This is exactly why you keep the regression-seed corpus.
  • Demo crashes on controller hot-swap during the title screen. Fix the controller detection lifecycle, not the symptom.

This day pairs with the help-plan item Unity Test Framework property-based fuzz Editor hang via FsCheck.Unity - planned this cycle.

Day 4 - Store page parity

Goal: What the trailer's first six seconds promise, the demo's first sixty seconds delivers - and the capsule, screenshots, short description, and tag set all match.

The autumn 2026 Steam discovery refresh weighted page-visit-to-wishlist conversion heavier than impressions. A mismatched store page costs you double in 2026 because the visit goes uncounted toward the algorithm.

Gate steps:

  1. Open the demo's Steam store page (in private browsing, not your account).
  2. Watch the trailer to second six. Note what the trailer is selling: combat, exploration, narrative, puzzle, vibe.
  3. Launch the demo. In the first sixty seconds, does the player encounter what the trailer's first six seconds promised?
  4. Open each screenshot. For each, find the actual moment in the demo where that screenshot was captured (or could be captured today). If a screenshot is "from an earlier build," replace it.
  5. Read the short description. Does the first sentence match the trailer's first six seconds and the demo's first sixty seconds?
  6. Open the tag list. Cross-check the top five tags against what a player who finishes the demo would have called the game.

Artifact: final-week-evidence/day-4-store-parity.md - the four-corner alignment table (trailer, demo, screenshots, description) + tag review.

Common failure modes:

  • Trailer leads with combat. Demo opens with thirty seconds of menus. Reorder the demo opening, not the trailer.
  • Screenshots show a level the demo does not include. Replace them.
  • Top tag is "Roguelike" but the demo has no roguelike loop. Fix the tags, not the demo.

This pairs with Steam Capsule A-B Wishlist Click-Through One-Week Experiment (2026) for the deeper capsule-conversion treatment.

Day 5 - Controller glyph parity for the autumn 2026 Deck Verified refresh

Goal: Every controller archetype in the autumn 2026 Deck Verified refresh shows the correct glyph in-game, including Xbox Elite, Xbox Series 2, PlayStation DualSense, DualSense Edge, and Steam Deck (LCD and OLED).

This is the single most common autumn 2026 cert-lane rejection: a build that worked under the previous Deck Verified rules now fails because the game still calls GetGlyphForActionOrigin_Legacy and gets a generic Xbox glyph for an Xbox Elite controller.

Gate steps:

  1. Migrate any remaining GetGlyphForActionOrigin_Legacy calls to GetGlyphPNGForActionOrigin per the autumn 2026 Deck Verified refresh API.
  2. Extend the VDF action manifest with xbox_elite_one, xbox_elite_two, xbox_series_two_*, and ps_dualsense_edge rows.
  3. Subscribe to SteamInputDeviceConnected_t and refresh the glyph cache on connect.
  4. Test each archetype on a Deck (paired via Bluetooth where physical hardware is not available). Screenshot the action prompt UI for each.
  5. Test controller hot-swap: connect Xbox Elite, swap to DualSense, verify the glyph updates within one frame.

Artifact: final-week-evidence/day-5-glyph-parity.md - five screenshots (one per controller archetype) plus the hot-swap timing note.

Common failure modes:

  • Glyph cache stale until scene reload. Fix by clearing the cache on every SteamInputDeviceConnected_t.
  • DualSense Edge falls back to generic PlayStation glyph. Add the ps_dualsense_edge VDF row.
  • Steam Deck OLED behaves differently than LCD. Test both. They share most behavior but driver-stack differences surface here.

This day pairs with the help-plan item Steam Deck Verified 2026 autumn refresh Xbox Elite glyph wrong via Steam Input fix - planned this cycle.

Day 6 - Demo branch metadata parity and Steam Input default config

Goal: The demo branch on Steamworks has its own Steam Input default config in controller_base/, its own library assets, and its metadata matches the main branch where it should and differs where it must.

Why this is its own day: The autumn 2026 Steamworks portal rejection rate for STEAM_INPUT_DEFAULT_CONFIG_MISSING on the demo branch spiked in early October 2026 because teams set the VDF on default and forgot the depot promotion stripped it from the demo depot.

Gate steps:

  1. Confirm the VDF action manifest lives in the demo depot's controller_base/ folder, not just the main depot.
  2. Re-promote the demo depot from a clean SteamPipe run with explicit --include-config if your tooling supports it.
  3. Regenerate demo library assets via Steamworks portal (header capsule, library hero, library logo).
  4. Verify the demo branch beta password (if any) is documented; festival visibility flip should be the only late-week change.
  5. Run the Steamworks validate against the demo branch metadata. Document any warning, even green ones.

Artifact: final-week-evidence/day-6-demo-branch-parity.md - Steamworks metadata green-bar screenshot + VDF presence confirmation + library assets verification.

Common failure modes:

  • VDF lives in default but not demo depot. Re-promote with the controller config explicitly included.
  • Library assets show "main game" branding on the demo branch. Regenerate them for the demo SKU specifically.
  • Festival visibility toggle accidentally already on. Turn it off until Day 7 passes.

This day pairs with the help-plan item Steam Next Fest October 2026 demo upload rejected missing Steam Input default config metadata fix - planned this cycle.

Day 7 - Traffic spike rehearsal

Goal: Behave like the festival has already started - run the demo against the analytics and telemetry path you will have during the spike, and confirm the retention funnel instrumentation produces useful numbers.

Gate steps:

  1. Open the analytics dashboard you will be checking during the festival.
  2. Run the demo end-to-end three times, with three different play styles (rush, explore, get stuck).
  3. Confirm each retention funnel stage records an event: download (Steam-side, implicit), launch, past-title, first-input, first-meaningful-interaction, first-checkpoint, finish-demo.
  4. Confirm crash telemetry routes to a place a human will see within 1 hour during the festival window.
  5. Confirm the demo's update mechanism is off for the festival - no surprise patches during the spike.
  6. Confirm at least two team members can be on-call (or asleep with crash alerts routed to a phone) for the first 48 hours of the festival.

Artifact: final-week-evidence/day-7-spike-rehearsal.md - retention funnel table with sample counts per stage + crash alert routing diagram + on-call schedule.

Common failure modes:

  • Retention funnel records "launch" but not "past-title." Fix the event registration in the title-screen-exit code path.
  • Crash telemetry goes to an email no one reads on weekends. Route to Slack, Discord, or SMS for the festival window.
  • Update mechanism left on. A surprise patch mid-spike will confuse return players and reset some streak data.

This day pairs with Steam Next Fest Demo Retention Funnel Instrumentation 2026 Small Team Playbook for the deeper retention treatment, and with Steam Next Fest Demo Stability 2026 72-Hour Hotfix Freeze Checklist for the post-submission stability lane.

Common mistakes across the whole challenge

  • Treating Day 1 scope freeze as guidance, not a hard cut. YELLOW always wants to creep back. The producer signature on the scope sheet is the enforcement mechanism.
  • Skipping Day 2 because "we've already playtested." Five new playtesters this week is not the same as five playtesters six weeks ago against a different build.
  • Running Day 5 on Xbox only. Xbox Elite, DualSense, and DualSense Edge are the specific autumn 2026 refresh failure modes. Generic Xbox is the easy path; it is also the rejected path.
  • Promoting the demo depot without the controller config folder. This is the single most common Day 6 rejection in October 2026.
  • Letting auto-update stay on during the festival. A mid-spike patch reseeds player state and confuses the retention funnel.
  • Doing all seven days as one person. One named owner per day. Three or more people on a day is fine; zero is how Day 5 silently does not happen.

Pro tips for a working final week

  1. Pre-mint the demo branch evidence folder. Create final-week-evidence/ on Day 0 with one empty file per day. The empty files make missing artifacts impossible to ignore.
  2. Block calendars for the spike. Days 1 through 7 of Next Fest (the festival itself) should have engineering on triage, not on feature development.
  3. Keep the regression-seed corpus version-controlled. Day 3's seeds belong in your repo, not on a producer's laptop.
  4. Use a private Steam beta branch for the rehearsal. Day 7 should not flip festival visibility on. Keep the beta password fresh and unshared.
  5. Take screenshots of green dashboards. Future-you needs evidence the gate ran, not your memory of running it.
  6. One festival, one demo. Resist the temptation to ship a "tiny update" mid-festival. The traffic spike is short; stability beats novelty.
  7. Write the festival retrospective on Day 7. It is much easier to fill in "what went well" before the festival actually happens. Edit it after with what changed.

How this fits the broader 2026 indie production stack

Three production-side topics pair naturally with this challenge:

If the demo is also your slice toward partner submission, queue the 7-Day Release Candidate Freeze Challenge for the week after the festival closes.

Key takeaways

  • Next Fest October 2026 is denser than previous Next Fests. Q3 cert intake density + Deck Verified autumn refresh + Meta holiday early window all stack on top of the festival week.
  • One quality gate per day, one named owner per gate. Shared ownership is how Day 5 silently does not happen.
  • Day 1 scope freeze is hard, not soft. RED means delete-or-feature-gate, not "fix-this-week."
  • Day 2 measures the first 60 seconds with real new playtesters. Studio logos, tutorial walls, and unskippable intros lose the festival traffic spike.
  • Day 3 needs a preserved regression-seed corpus. Replay every closed bug in the last 90 days against the demo branch. Keep crash seeds in the repo.
  • Day 4 aligns four corners: trailer first six seconds, demo first sixty seconds, screenshots, short description.
  • Day 5 covers Xbox Elite, DualSense, DualSense Edge, and Steam Deck OLED specifically. Generic Xbox glyph is the easy path; it is also the autumn 2026 rejection path.
  • Day 6 lives or dies on the demo depot having its own controller config folder. STEAM_INPUT_DEFAULT_CONFIG_MISSING on the demo branch is the dominant October 2026 rejection.
  • Day 7 rehearses the analytics path during a fake traffic spike. Auto-update should be off; on-call routing should be set; retention funnel events should fire end-to-end.
  • Each day produces one evidence artifact. final-week-evidence/ is the answer to "did we run the gate?"
  • Refusal rule: A failed gate stops the stack. Either fix it today or document a carve-out before moving on.

FAQ

1. We are a two-person team. Can we still run all seven gates? Yes - but compress two gates into one calendar day where you must. Days 1 and 2 are non-negotiable; they shape the rest of the week. Days 3 and 4 can run in parallel (one person on fuzz, one on store parity). Days 5 and 6 can run on the same calendar day if you have one Deck and a few hours. Day 7 is the day before festival open. Skip nothing; combine carefully.

2. We already shipped the demo for an earlier closed test. Do we still need Day 1 scope freeze? Yes, harder. A previously-shipped demo carries hidden YELLOW from when "we'll just patch it" was acceptable. The October Next Fest traffic spike is not acceptable for that pattern. Run the GREEN/YELLOW/RED pass against the current demo branch.

3. What if the Day 5 glyph parity gate fails and we have not migrated to GetGlyphPNGForActionOrigin yet? Migrate this week. The autumn 2026 Deck Verified refresh is the difference between "demo runs on Deck" and "demo passes Deck Verified during October." The migration is mechanical: replace the legacy call site, extend the VDF action manifest with the new controller archetypes, and subscribe to the device-connected event. Allocate a focused four hours.

4. We do not have analytics wired. Should we ship the demo without it for Next Fest? Ship with minimal instrumentation rather than none. At a minimum: a launch event, a "past-title" event, a "first-meaningful-interaction" event, a "finish-demo" event, and a crash telemetry route to a place a human reads within an hour. Even four events plus crashes will tell you which step of the funnel bled during the spike. Without any instrumentation, the festival traffic vanishes into a black box.

5. Should we patch the demo during the festival if a bug surfaces? Default to no, unless the bug is a hard blocker (crash on launch, save corruption, save-game loss). A small visual or balance bug is not worth a patch during the spike because: (a) Steam's update mechanism reseeds session state for return players, (b) crash telemetry signal-to-noise rises temporarily after a patch, (c) the team is tired and patches under fatigue cause more bugs than they fix. Keep a hotfix branch ready; do not ship from it unless the bar is hit.

Found this challenge useful for your Next Fest October 2026 prep? Share it with the team lead who has been the loudest about "I think we're fine" - and bookmark it for the February 2027 festival cycle, which will follow the same shape.