Dispatch drops players into a pressure-cooker narrative where every dialogue choice feels like pulling aggro in a boss fight you can’t see. Instead of swords or skill trees, your tools are timing, tone, and judgment, all while managing a city that’s constantly one bad call away from spiraling. The hook is immediate: you’re not the hero on the streets, you’re the one deciding who gets help and who doesn’t.
This is an episodic narrative game built to be consumed in chunks, argued about between releases, and replayed to test how different decisions ripple outward. If you’ve been craving something with Telltale DNA but modernized for today’s pacing and player expectations, Dispatch is very clearly aiming to fill that gap.
A Narrative-First Episodic Design
Dispatch is structured as a multi-episode season, with each episode functioning like a self-contained chapter that still feeds into a larger, branching arc. Choices don’t just trigger flavor dialogue; they actively reshape character relationships, citywide outcomes, and what situations even appear in later episodes. Think long-term consequence tracking rather than quick-time event theatrics.
Each episode is designed to be playable in a single sitting, but with enough narrative density to reward replays. Like managing cooldowns in a tough encounter, knowing when to push, stall, or reroute a situation becomes the core gameplay loop. The episodic format gives the developers room to respond to player feedback and adjust pacing between drops.
The Developer Vision Behind Dispatch
Dispatch is being developed by AdHoc Studio, a team made up of former Telltale Games veterans who worked on genre-defining episodic titles. Their stated goal is to evolve the formula rather than repeat it, focusing on deeper systemic storytelling instead of illusion-of-choice design. This means fewer binary good-or-evil decisions and more morally gray calls with delayed consequences.
The studio has emphasized that Dispatch is built around player accountability. There are no clean I-frames for bad decisions here; mistakes linger, characters remember, and the city adapts. That design philosophy is why the episodic model matters, giving space for tension to breathe between releases instead of rushing players through the fallout.
Release Model, Platforms, and What’s Actually Confirmed
As of now, Dispatch is officially confirmed as an episodic release, but individual episode release dates have not been locked in publicly. What is confirmed is a season-based structure, with episodes planned to launch sequentially rather than all at once. Any specific dates or gaps between episodes circulating online should be treated as speculative unless announced directly by the developers or publisher.
Dispatch is currently confirmed for PC, with console platforms expected but not fully detailed yet. Players looking to stay ahead of episode announcements should follow AdHoc Studio’s official channels, including Steam updates and social media posts, where release windows and platform details are expected to be shared first.
Confirmed Dispatch Episode Release Dates: Officially Announced Episodes
With the release model clarified, the next obvious question is when players can actually get their hands on each chapter. As of the most recent official communications from AdHoc Studio, only high-level release information has been confirmed. That means no hard calendar dates yet, but there are still some important details worth locking in so expectations stay grounded.
Dispatch Episode 1: Status and Release Window
Dispatch Episode 1 has been formally confirmed as the starting point of the season-based rollout, but it does not currently have a publicly announced release date or month. AdHoc Studio has stopped short of even naming a release window, signaling that the team is prioritizing polish and systemic stability over hitting an arbitrary launch target.
What is confirmed is that Episode 1 will function as a full narrative entry, not a prologue or demo-length slice. Expect a complete gameplay loop with meaningful branching, persistent consequences, and enough narrative payload to set aggro for the rest of the season. Anything claiming a specific launch day for Episode 1 should be treated as unverified.
Future Episodes: What’s Confirmed and What Isn’t
Beyond Episode 1, all subsequent Dispatch episodes remain undated. AdHoc Studio has confirmed that episodes will release sequentially as part of a single season, rather than in a binge-style drop, but has not committed to a fixed cadence like monthly or quarterly updates.
This flexible scheduling aligns with the studio’s stated goal of responding to player data and feedback between releases. Think of it like tuning encounter balance mid-raid rather than locking stats at launch. Any leaks or roadmap graphics suggesting episode counts, gaps, or finale timing are speculative unless they come directly from the developer or publisher.
Confirmed Platforms at Launch
At this stage, Dispatch is officially confirmed for PC, with distribution expected via Steam. Console versions have been acknowledged as a goal, but no PlayStation or Xbox release timing has been announced alongside the episodic rollout.
Importantly, AdHoc Studio has not confirmed whether episodes will launch simultaneously across all platforms once consoles are finalized. Until that’s clarified, PC players should assume they’ll be first in line when Episode 1 goes live.
Where to Track Official Episode Announcements
For players who want real-time updates without wading through RNG-level rumor noise, AdHoc Studio’s own channels are the only reliable source. Steam news posts, the studio’s official social media accounts, and developer blog updates are where episode release windows will be announced first.
Once Episode 1 is dated, future episodes are expected to follow with clearer timelines, especially as the studio locks pacing and production flow. Until then, the lack of hard dates isn’t a red flag, it’s a signal that Dispatch is being built for longevity rather than speedrunning its own narrative.
Upcoming Dispatch Episodes: Release Windows, Roadmap Signals, and What’s Next
With Episode 1 still waiting on an official date, the bigger question for narrative-focused players is how the rest of Dispatch will unfold once the season actually starts. AdHoc Studio has been careful not to overpromise, but there are enough signals to map out what’s likely, what’s confirmed, and what’s pure theorycrafting.
This is less about calendar sniping and more about understanding the studio’s release philosophy, because that philosophy will dictate everything from episode gaps to how reactive the story becomes over time.
Episode 1 Status: The Only Real Anchor Point
As of now, Episode 1 is the only episode with any form of acknowledged release window, and even that window remains intentionally broad. AdHoc Studio has stopped short of naming a day or even a locked month, reinforcing that the first drop needs to land cleanly before the rest of the season can line up.
Think of Episode 1 as the baseline build. Once it’s live, the studio can gather telemetry, narrative feedback, and pacing data before committing to tighter windows for future episodes.
Episodes 2 and Beyond: Sequential, Reactive, Undated
Every episode after Episode 1 is officially undated. What is confirmed is that Dispatch will roll out sequentially, with each episode releasing individually rather than as a bulk season pass drop.
This structure gives AdHoc Studio room to adjust narrative beats, mechanical friction, and even character focus between episodes. It’s the episodic equivalent of hotfixing encounter tuning after watching players break your intended DPS checks.
Is There a Roadmap? Reading Between the Lines
There is no public roadmap graphic, timeline, or episode count confirmed by the developer. Any charts floating around claiming a five-episode arc or a specific finale window are speculation unless they’re posted directly by AdHoc or its publishing partners.
What has been hinted at is a single-season narrative with a defined beginning, middle, and end. That suggests a finite episode count, but not how long the gaps between those drops might be.
Release Cadence: Why There’s No Monthly Promise
AdHoc Studio has explicitly avoided committing to a monthly or quarterly cadence. That’s not a red flag, it’s a design choice rooted in flexibility.
Episodic games live or die on pacing. Locking dates too early can force rushed content, narrative inconsistencies, or mechanical debt that snowballs by the finale. Dispatch is being built to adjust its aggro targets mid-season, not face-tank deadlines.
Platform Rollout and Episode Availability
PC is the only confirmed launch platform for Dispatch episodes, with Steam serving as the primary distribution channel. Console versions are planned, but there is no confirmation on when PlayStation or Xbox players will get access to Episode 1 or later chapters.
It’s also unclear whether console releases, once ready, will sync with the current episode or start from Episode 1. Until clarified, the safest assumption is that PC will remain the lead platform throughout the early episodic rollout.
How to Stay Ahead of Official Episode Announcements
If you’re tracking Dispatch episode releases seriously, developer-first sources matter. Steam news updates, AdHoc Studio’s social channels, and official blog posts are where release windows will appear before they hit aggregator sites.
Once Episode 1 is locked, expect communication around later episodes to tighten up. Until then, patience is part of the experience, and in episodic storytelling, that restraint often pays off when the narrative finally hits its stride.
Unannounced or Speculated Episodes: What’s Likely, What’s Rumor, and What’s Not Confirmed
With no official roadmap and only Episode 1 firmly on the calendar, the space beyond that is where theorycrafting kicks in. That’s normal for episodic games, especially ones positioning story beats as their primary DPS. The key is separating what the developers have actually telegraphed from what the community is extrapolating.
What’s Likely Based on Developer Signals
AdHoc has repeatedly framed Dispatch as a single-season narrative with a clear arc. In episodic terms, that almost always means multiple chapters beyond the opener, not a one-and-done drop or a live-service drip feed. Think a beginning that establishes systems and stakes, a middle that escalates mechanics and consequences, and a finale designed to pay off player choices.
It’s also reasonable to expect episode lengths to fluctuate. Narrative-heavy episodes often expand or contract based on branching paths, VO scheduling, and QA on choice logic. That variability is one reason AdHoc isn’t locking cadence, and it suggests later episodes won’t be copy-paste in scope.
The Most Common Rumors—and Why They’re Shaky
The “five-episode season” claim is the most persistent rumor, usually backed by nothing more than screenshots of fan-made timelines or placeholder listings. There is no public confirmation of an episode count, and no partner storefront has published one either. Treat any numbered finale window as pure RNG, not insider knowledge.
Another rumor floating around is a mid-season content drop or side episode. That’s appealing on paper, but there’s been zero indication Dispatch is building optional detours outside the main arc. Episodic teams under this model typically avoid side content until the core narrative is locked.
What’s Explicitly Not Confirmed
There are no dates, windows, or even target months announced for Episode 2 or beyond. Not “late summer,” not “Q4,” not “soon.” If you see a date attached to a later episode, it didn’t come from AdHoc.
Console timing for later episodes is also unconfirmed. While console versions are planned, there’s no word on whether they’ll launch alongside a specific episode or arrive as a full-season package. Until stated otherwise, assume PC remains the lead platform and everything else follows once the hitbox on logistics lines up.
How to Read Between the Lines Without Overcommitting
The safest way to interpret silence is intent, not delay. AdHoc is choosing to ship when each episode is mechanically and narratively ready, not when a calendar demands it. That approach tends to produce fewer retcons, cleaner choice tracking, and finales that actually stick the landing.
If you’re tracking future episodes, ignore leaks and focus on developer-first channels. When an episode window solidifies, it will appear on Steam news posts and official social updates before anywhere else. Until then, anything beyond Episode 1 lives firmly in the realm of speculation.
Platform Availability by Episode: PC, Console, and Any Platform Gaps
If release dates are the first thing players want locked down, platform parity is a close second. Dispatch’s episodic structure makes this trickier than a traditional full-game launch, especially with AdHoc signaling a PC-first rollout. Right now, platform availability is less about what’s missing and more about what’s intentionally staggered.
Episode 1: PC Is the Only Confirmed Day-One Platform
Episode 1 is confirmed for PC via Steam, and that’s the only platform with a hard lock at launch. This aligns with how AdHoc is handling iteration: PC gives them faster patch deployment, cleaner telemetry, and fewer certification bottlenecks if something breaks post-launch. For a narrative-heavy episode where choice flags and state tracking are everything, that flexibility matters more than raw install base.
There’s no ambiguity here. If you want to play Dispatch the moment Episode 1 goes live, PC is the only guaranteed path.
Console Versions: Planned, but Not Tied to Specific Episodes
Console versions of Dispatch have been acknowledged, but critically, they are not attached to Episode 1—or any numbered episode—yet. There’s no confirmation of a simultaneous console drop, no “Episode 2 hits PlayStation” messaging, and no platform-specific windows floating around from official channels. Anything suggesting otherwise is speculation filling in silence.
This usually points to one of two strategies: either consoles arrive once multiple episodes are bundled, or they land after the full season is content-complete. Episodic teams often choose the latter to avoid re-certifying every single episode update, which can slow cadence to a crawl.
What This Means for Episode 2 and Beyond
For later episodes, PC should be treated as the lead platform unless AdHoc explicitly says otherwise. There’s no confirmation that Episode 2, 3, or any later chapter will launch day-and-date on console, even if console builds exist internally. From a production standpoint, it’s cleaner to ship episodes without juggling platform-specific compliance every few months.
That doesn’t mean consoles are an afterthought. It means Dispatch is prioritizing narrative continuity and mechanical stability over simultaneous platform parity, which is often where episodic projects fall apart.
Potential Platform Gaps and Why They’re Not Red Flags
The biggest perceived gap is the lack of a confirmed console episode roadmap, but that’s not a warning sign on its own. Certification timelines, patch approval, and save-state consistency across episodes are all harder on closed platforms. Waiting until the full arc is locked reduces the risk of broken progression or retroactive fixes that invalidate player choices.
There’s also no mention of cloud platforms, subscription services, or handheld-specific releases. If those happen, they’ll almost certainly come after the core PC version proves stable across multiple episodes.
How to Track Platform Announcements Without Chasing Noise
If platform expansion is coming, it won’t leak quietly. Steam news posts, official social accounts, and storefront updates are the first places AdHoc will signal a change in platform availability. Console storefront listings appearing without developer commentary should be treated as placeholders, not confirmations.
For now, the platform picture is clean, if narrow. Episode 1 is PC-only, future episodes are PC-first, and consoles remain planned but unscheduled. Until AdHoc locks that in publicly, anything else is just players rolling the dice and hoping the RNG hits.
How Dispatch Episode Releases Have Rolled Out Historically: Patterns and Cadence
With platform expectations set, the next question players naturally ask is about timing. Episodic games live or die by cadence, and Dispatch is still early enough that every release tells us something about how AdHoc plans to pace the full arc. Even with limited data, there are already clear patterns worth calling out.
Episode 1 Set the Baseline, Not the Schedule
Episode 1’s PC launch established Dispatch as a live episodic project, but it didn’t lock in a rigid timetable. AdHoc positioned the release as a foundation drop: narrative systems, choice tracking, and mechanical hooks first, speed second. That’s a classic episodic move, especially for studios that care more about continuity than chasing a monthly beat.
Because there’s only one episode publicly released so far, players shouldn’t expect a clean “every X weeks” rhythm. One data point doesn’t equal a cadence, and AdHoc has been careful not to promise one.
AdHoc’s Episodic DNA Favors Variable Gaps
Historically, studios building narrative-first episodes tend to operate in staggered windows rather than fixed seasons. Writing revisions, VO recording, cinematic implementation, and branching logic QA all scale non-linearly as episodes progress. The deeper Dispatch goes, the more prior choices ripple forward, increasing dev overhead between drops.
That usually results in earlier episodes landing closer together, with later chapters taking longer. It’s not unlike difficulty scaling in an RPG: early encounters are fast, but endgame bosses demand more prep, tuning, and testing.
What’s Confirmed vs. What’s Educated Guesswork
What’s confirmed is simple. Episode 1 is live on PC, and Episode 2 is in active development with no publicly locked release date. Anything beyond that exists as internal targets, not promises, and AdHoc hasn’t attached public windows to Episode 2 or later chapters yet.
Speculation tends to cluster around seasonal windows, but players should treat those like RNG rolls, not guaranteed drops. Until a date appears in an official Steam post or developer announcement, it’s not real, no matter how convincing the rumor sounds.
Release Cadence Is Being Driven by Stability, Not Speed
Everything about Dispatch’s rollout points to stability-first development. Save-state integrity across episodes, choice persistence, and narrative flag accuracy matter more here than hitting an arbitrary calendar slot. Rushing an episode that breaks prior decisions would be the equivalent of shipping a boss fight with busted hitboxes.
That philosophy usually leads to uneven but safer spacing between episodes. Long waits can be frustrating, but they also reduce the odds of retroactive patches that invalidate player choices or force restarts.
Where Players Should Watch for Real Release Signals
Historically, Dispatch updates haven’t been stealth drops. When an episode is nearing release, AdHoc communicates it directly through Steam news updates and official social channels. Those announcements typically include platform confirmation and a concrete window, not vague “coming soon” language.
Storefront metadata changes or backend updates without commentary shouldn’t be treated as release signals. If a date matters, AdHoc will say it out loud, and that’s the moment players should start clearing their backlog and prepping for the next chapter.
Delays, Changes, and Revisions: Tracking Shifts in the Dispatch Release Schedule
With that stability-first philosophy in mind, it’s no surprise that Dispatch’s release roadmap has already seen adjustments. Episodic development rarely survives first contact with real player data, and AdHoc has shown a willingness to shift timelines rather than brute-force episodes out the door.
Episode 1’s Launch Set the Baseline
Episode 1 is the only immovable data point in Dispatch’s timeline. It launched on PC via Steam and currently stands as the foundation all future episodes are being built on. No retroactive changes have been made to its release date, but post-launch patches did reshape internal expectations for what later episodes would require.
Those patches mattered. Player choice density, save compatibility, and narrative flag checks ended up heavier than originally scoped, effectively increasing the dev team’s workload per episode going forward.
Episode 2: From Target Window to Open Development
Early internal targets for Episode 2 were looser and closer to Episode 1 than many players expected. That changed once AdHoc began stress-testing long-term save progression across multiple branches. As a result, Episode 2 shifted from a soft internal window to an explicitly undefined release date.
What’s important here is what didn’t happen. There was no public delay announcement because no public date ever existed. From the outside, it can feel like a delay, but structurally this was a revision of scope, not a missed deadline.
Why Later Episodes Were Quietly Re-evaluated
Episodes beyond Episode 2 were never given external windows, but internally they were affected the most. Narrative-heavy episodes stack complexity exponentially, not linearly. Every new branch has to respect every old decision, and that compounds faster than most players realize.
Think of it like adding new mechanics mid-campaign. Each episode doesn’t just introduce new content; it has to rebalance the entire game state behind it. That reality forced AdHoc to revisit pacing assumptions for Episodes 3 and beyond before any dates were even considered for public discussion.
Platform Considerations and Their Impact on Timing
Right now, Dispatch is confirmed on PC, and all released content has been built with that platform as the primary target. No console release dates or episode parity timelines have been announced. If and when console versions enter the conversation, expect that to affect episode scheduling across the board.
Cross-platform certification isn’t just paperwork. It introduces new QA layers, build requirements, and submission timelines that can easily push episodic releases further apart if they’re not planned from day one.
Separating Real Schedule Changes From Community Noise
It’s easy to mistake silence for delay, especially in episodic games. Community speculation often fills gaps with assumed windows, which then get treated as broken promises when nothing materializes. In Dispatch’s case, the only real schedule changes have been internal recalibrations, not public reversals.
If a release window isn’t attached to an official AdHoc announcement, it shouldn’t be logged as a shift. The actual schedule, as it stands now, is simple: Episode 1 is out on PC, Episode 2 is in development with no confirmed date, and all subsequent episodes remain unannounced.
How Players Can Track Legitimate Updates Going Forward
Players who want accurate, real-time updates should stick to primary sources. Steam news posts, official social media updates, and direct developer statements are the only places where release timing becomes real. Anything else is just aggro pulling without a tank.
When Dispatch’s schedule changes again, it won’t be subtle. AdHoc has been clear when expectations need adjusting, and future revisions will likely come with explanations tied directly to development realities, not vague PR language.
Where to Get Official Updates First: Social Channels, Store Pages, and Developer Communications
If you want to track Dispatch episode release dates without getting baited by RNG speculation, you need to know exactly where AdHoc actually communicates. Not all updates carry the same weight, and in episodic development, the source matters as much as the message.
This is where confirmed information appears first, where release windows become real, and where changes to the roadmap get explained instead of spun.
Steam News Posts and Store Page Updates
Steam is the primary source of truth for Dispatch right now, full stop. Every confirmed update so far, including Episode 1’s launch and the current status of Episode 2, has been communicated through official Steam news posts tied directly to the store page.
Steam updates matter because they’re synchronized with builds, patches, and backend changes. If an episode date, delay, or content shift is real, it will show up here alongside patch notes or development breakdowns, not buried in a comment thread.
Players tracking release timing should wishlist Dispatch and enable notifications. That’s how you catch updates the moment they go live, not hours later after social feeds start echoing them.
Official Social Media: Signal, Not Schedule Guarantees
AdHoc’s social channels are useful, but they function more like radar than a release calendar. Twitter, Bluesky, and similar platforms are where the studio shares development progress, high-level milestones, and occasional status clarifications.
What they don’t do is lock dates. If a post doesn’t explicitly state a release window, it’s not a confirmation, no matter how confident the wording sounds. Social posts are best read as temperature checks on development, not countdown timers.
That said, social channels are often the first place where a larger announcement gets teased before a full breakdown lands elsewhere. Think of them as aggro pulls before the real DPS hits.
Developer Blogs and Long-Form Communications
When AdHoc needs to explain why something changed, this is where it happens. Developer blogs, extended Steam posts, and occasional interviews are where pacing adjustments, systemic reworks, or episode scope changes get real context.
These communications are critical for understanding why Episode 2 doesn’t have a date yet and why later episodes remain unannounced. Episodic games live or die on narrative cohesion, and when that balance shifts, AdHoc has consistently chosen transparency over rushed timelines.
If a future episode window is announced alongside a detailed dev breakdown, that’s the closest thing Dispatch will offer to a locked-in release plan.
What to Ignore: Aggregators, Datamines, and “Insider” Claims
Third-party tracking sites, scraped backend changes, and anonymous “leaks” don’t reflect Dispatch’s actual release schedule. Episodic development doesn’t move in neat, predictable chunks, and internal testing branches are not release candidates.
Until a date or window comes directly from AdHoc through an official channel, it remains speculative. Treat anything else like a bad hitbox read: interesting, but not something you should build your expectations around.
For Dispatch specifically, the rule is simple. Episode 1 is live on PC. Episode 2 is actively in development with no confirmed date. Everything beyond that exists only when AdHoc says it does, and the channels above are where that confirmation will always appear first.
Quick-Reference Dispatch Episode Release Timeline & Tracker
If you just want the clean facts without parsing dev posts or reading between the lines, this is the snapshot to bookmark. Everything below reflects only what AdHoc has officially confirmed through launch announcements, store pages, or direct developer communication.
Anything not listed here does not have a date, window, or implied lock, no matter how confidently it’s discussed elsewhere.
Dispatch Episode 1: “The Call”
Release Status: Available now
Release Date: Launched on PC
Platforms: PC via Steam
Episode 1 is fully live and playable, establishing Dispatch’s narrative tone, choice-driven structure, and mechanical backbone. This episode functions as both a story opener and a systems onboarding pass, easing players into dialogue pressure, branching outcomes, and the game’s pacing philosophy.
If you’re tracking future episodes, Episode 1 is also the baseline AdHoc uses when discussing scope, cadence, and feedback-driven iteration.
Dispatch Episode 2
Release Status: In active development
Release Date: No confirmed window
Platforms: PC (additional platforms unannounced)
Episode 2 does not currently have a release date or release window. AdHoc has acknowledged its development publicly, but has been explicit about not locking timing until narrative structure, pacing, and implementation hit internal targets.
Any date attached to Episode 2 outside of an official AdHoc announcement is speculative. Treat it like RNG chatter, not a guaranteed drop.
Future Dispatch Episodes (Episode 3 and Beyond)
Release Status: Unannounced
Release Date: Not confirmed
Platforms: Not confirmed
Beyond Episode 2, AdHoc has not announced episode counts, release cadence, or long-term scheduling. This is intentional. The studio has framed Dispatch as a reactive episodic project, where player feedback and narrative cohesion directly influence downstream content.
Until an episode is formally revealed, it should be considered non-existent from a release-tracking standpoint.
Platform Availability at a Glance
Right now, Dispatch is a PC-first experience. Episode 1 is available on PC, and Episode 2 is expected to follow the same path unless stated otherwise.
Console versions, if they happen, will be announced explicitly. There are no confirmed PlayStation, Xbox, or Switch releases at this time.
How to Stay Updated Without Getting Burned
For real updates, stick to AdHoc’s official channels: Steam announcements, developer blogs, and verified social posts that reference formal updates. Those are the only places where release windows or timing shifts will be stated clearly.
If a post doesn’t include a date, a window, or a detailed breakdown explaining why timing changed, it’s not a release update. It’s flavor text.
Dispatch is built for players who value narrative precision over speedruns, and its release strategy reflects that. If you want the best experience, let the episodes land when they’re ready, not when the rumor mill says they should.