Squadron 42 Townhall: Co-op, VR Plans and the Road to Star Citizen 1.0
A solo campaign with its own ending, separate combat difficulty settings and the ambitions beyond launch: the key points from a Manchester attendee’s account.
Manchester’s developer discussion offered a clearer picture of the campaign’s ambitions—and the work that could follow it into the persistent universe.
For a weekend dominated by first impressions of Squadron 42, some of the most interesting answers came away from the demo stations. Would friends ever join the campaign? Would the story end cleanly? And what happens to Star Citizen when the single-player game finally ships?
Creator tenpoundfortytwo attended the Manchester event and recounted the townhall in his 11 October broadcast. His account points to a deliberately personal campaign, enthusiasm for more ambitious VR support and a substantial shift of development attention towards Star Citizen after release. Those are different kinds of answer: one describes the game being made, another an ambition, and another the studio’s intended direction.
This report covers that first-hand attendee account. For the hands-on experience itself, our Manchester playtest reactions feature brings together the players’ praise, frustrations and detailed impressions.
A campaign built around one pilot
The answer on co-op was unusually straightforward. At around 18:30 in the recording, tenpoundfortytwo recounts a rejection of campaign co-op, explaining that Squadron 42 is built around the player being the central character. Multiplayer belongs to Star Citizen; the campaign is not being described as a story that a second pilot can simply drop into.
That suits the kind of military drama Squadron 42 is trying to deliver. A conversation in a corridor, a mission briefing or time spent getting to know the people aboard your ship can be paced around a single player. Adding another human to that space would change more than the number of guns in a firefight. For anyone hoping to play the story alongside a friend, though, the practical answer is disappointing: plan on a solo campaign.
The stream also distinguishes the campaign from possible ideas involving Arena Commander. A speculative multiplayer offshoot is not a co-op announcement, and it should not be treated as a workaround to that answer.
)/85/meet-trejo.webp)
A complete story, with room for more
Later in the broadcast, around the half-hour mark, the creator recounts a conversation with narrative director Dave Haddock. The important reassurance is that Squadron 42 is intended to tell a self-contained story, with its character arcs resolved rather than simply stopping on a cliffhanger.
There can still be a future beyond that ending. A setting this large does not run out of stories when one pilot’s campaign finishes. But the stream does not establish that another chapter is already in production: at roughly 1:12:19, tenpoundfortytwo specifically revisits the distinction between having ideas and being in pre-production.
For players, that is a more useful promise than a distant sequel roadmap. The first game needs to earn its ending. Whatever eventually follows should have the freedom to build on a satisfying campaign rather than being required to finish it.
VR enthusiasm is not a launch guarantee
At approximately 14:21, the discussion turns to the ambition for fuller VR interaction, including body and motion-control support. The creator explicitly separates that aspiration from a commitment for launch.
It is easy to see the attraction. Squadron 42’s cockpits, physical controls and close conversations with crewmates invite the thought of being present inside them. Making that comfortable and usable throughout an entire campaign is a much bigger undertaking than demonstrating one impressive moment, however. Players should not buy hardware on the assumption that full motion-control VR will be included on day one.
Difficulty settings that recognise two different skill sets
The account describes separate difficulty choices for on-foot and flight combat, alongside discussion of controller support, aim assistance, subtitles and colour-blind accessibility. These points appear around 16:00.
Separating the two combat settings is especially welcome. Someone who is comfortable tracking a fighter through a dogfight may struggle with an aggressive squad in a corridor; an experienced shooter player can have exactly the opposite problem. Being able to adjust those challenges independently would let more people enjoy both halves of the campaign without making their stronger discipline feel trivial.
What could move across to Star Citizen?
The broadcast’s account of the post-release plan begins around 19:24. Most of the Squadron 42 team would move towards Star Citizen, while a smaller group would remain with the campaign. Rich Tyrer’s stated priority, as recounted by the attendee, was getting the persistent universe towards 1.0.
That is a direction for development, not a release date for Star Citizen 1.0. Nor does it mean every campaign system will arrive in the PU immediately. The recording mentions areas such as NPC scheduling and usability improvements, but a feature working in a controlled single-player mission is not evidence that its multiplayer version is ready to ship.
The prospect is still encouraging. Better interactions, clearer interfaces and more convincing routines would affect the time players spend between the headline missions as much as the missions themselves. The useful follow-up will be specific implementations entering test builds, followed by Live—not an assumption that a staffing change instantly delivers them all.
Watch the attendee’s full account
The strongest news here is the clarity around what Squadron 42 is trying to be: a solo story with its own conclusion. The VR discussion and the route towards Star Citizen 1.0 are worth following, but neither should be turned into a feature list or date that the developers have not committed to.