The future of Halo is once again the subject of intense debate after Frank O'Connor, a longtime creative figure in the series, outlined several ways Activision could approach its promised attempt at creating "the greatest Halo game ever." His thoughts arrive at a difficult moment for Xbox, Halo Studios, and the wider games business, following another wave of job reductions that reportedly affected hundreds of employees, including staff working on Halo.
O'Connor's central message is not that there is a simple formula for reviving one of gaming's defining first-person shooter franchises. In fact, he explicitly cautioned that none of the possible routes are easy, guaranteed to work, or even necessarily practical. Still, his three broad proposals offer a useful framework for considering what Halo needs next: a focused return to the series' original strengths, a bold reinvention that takes the universe somewhere unexpected, or a major live-service push built around models that have already succeeded elsewhere.
Crucially, O'Connor also argued that Activision should look toward the people recently pushed out of the industry. His recommendation was direct: bring in talent from Bungie, Halo Studios, and other teams affected by layoffs--developers he described as full of ideas and ability that have been cut short, constrained, or shelved over the years.
A franchise at another crossroads
Halo has repeatedly had to redefine itself without losing the identity established by its earliest entries. The original game, Halo: Combat Evolved, helped set expectations for console shooters through its mix of readable combat spaces, flexible weapon encounters, vehicle combat, co-operative play, and a science-fiction setting that balanced military spectacle with mystery. Later games expanded that foundation in different directions, but the core appeal was usually clear: players were dropped into encounters with tools that encouraged improvisation.
For useful background on this topic, read Deadlock Reaches 228,000 Concurrent Players as Valve Expands Its Core Game.
That legacy can also make every new Halo release unusually complicated. The community is not one uniform audience. Some players chiefly want competitive multiplayer with classic movement and map design. Others value campaign storytelling, co-op missions, Forge creations, custom games, big-team battles, or the tonal style of a particular era. There are also newer players who may have no attachment to the precise feel of older Halo games but expect the scale, support, and social features of a modern online shooter.
Activision now controls the franchise after it was moved from Halo Studios, alongside a pledge to deliver the series' biggest possible success. Yet the transition comes amid continuing Xbox job cuts. Microsoft's broader plan to eliminate 3,200 Xbox roles remained underway, with 268 employees reportedly affected earlier in September. At the time, Xbox chief content officer Matt Booty said the eliminated positions were spread across Halo Studios, other first-party teams, and Xbox Game Studios management and central functions.
Those circumstances make O'Connor's call to recruit displaced developers especially pointed. A company can change organizational charts or choose a new business strategy, but Halo's next phase will ultimately be determined by the people making its weapons, missions, multiplayer maps, network systems, art, narrative, and community tools.
Path one: build a modern classic Halo
O'Connor's first proposal is arguably the most immediately recognizable: create a "classic" Halo experience focused on the movement, sandbox, and shooter design that built the franchise's reputation. In practical terms, that means a game whose central attraction is not a radical genre shift or a complicated monetization framework, but consistently satisfying combat interactions.
Halo's sandbox has historically worked because its elements overlap in useful ways. A player can alter the course of a battle by swapping from a precision weapon to a plasma tool, stealing a vehicle, using grenades to disrupt an enemy formation, taking a high-ground route, or coordinating with teammates around objective play. The best Halo matches and campaign encounters leave room for plans to fall apart in entertaining ways.
O'Connor's version of this route would be designed around the core audience while remaining accessible enough to expand outward. That distinction matters. A game can respect veteran players without demanding that every newcomer already understands the series' long-established conventions. It can provide the recognizable Halo rhythm--shield management, weapon control, vehicle opportunities, map knowledge, and playful physics--while offering clear onboarding and reasons for less experienced players to stay.
He also emphasized a plain but important reality for multiplayer games: more players generally make the multiplayer experience better. A healthier population improves matchmaking speed, supports more playlists, gives custom communities a larger pool of participants, and makes competitive play more stable across regions and skill levels. No multiplayer shooter survives on nostalgia alone; it needs an active ecosystem.
The risk of this approach is that "classic" can become a vague label rather than a coherent design principle. Simply restoring old weapons, maps, or movement options would not automatically produce a successful modern Halo. The next game would still need dependable technical performance, meaningful social systems, effective anti-cheat measures, strong post-launch planning, and a campaign or multiplayer package persuasive enough to stand beside current competitors.
Path two: reinvent Halo instead of repeating it
The second direction is considerably more ambitious. Rather than trying to refine the familiar formula, O'Connor suggested making something new and contemporary that reimagines the game and universe in a surprising but compelling way. He floated the possibility of a fresh interpretation of the first-person shooter or even an action RPG, provided that the result is fundamentally distinct and supported by strong storytelling and thoughtful use of the Halo setting.
This is the most creatively exciting option and probably the most divisive. Halo has a universe large enough to accommodate experiences beyond another Master Chief-led military campaign. Its fiction contains human colonies, ancient installations, political factions, alien species, explorers, soldiers, civilians, intelligence agencies, and conflicts stretching across centuries. A new genre could examine parts of that world which are harder to explore in a traditional arena shooter.
An action RPG could potentially lean into character relationships, equipment choices, investigation, and travel across diverse worlds. A new kind of sandbox action game could focus on squad tactics, survival, stealth, or factional conflict. Even a first-person Halo title could depart from established campaign structures if it found a new way to make player choice, exploration, and the series' signature combat tools reinforce one another.
But reinvention would require discipline. Halo's name would create immediate attention from curious players and loyal fans, as O'Connor noted, but that early interest only lasts if the game gives audiences a convincing reason to believe in its new identity. A project that changes everything merely to seem modern could lose the distinctive encounter design and approachable sci-fi adventure that make Halo recognizable in the first place.
The challenge, then, would be to identify which parts of Halo are essential and which are flexible. Is the series defined by a particular control feel? By the relationship between infantry combat and vehicles? By the sound and visual language of the UNSC and Covenant? By its sense of discovery? Different players will answer differently, and a successful reinvention would need to make its choices with confidence.
Path three: use Activision's proven strengths
O'Connor's third possibility would translate Halo into Activision's comfort zone: player systems, progression structures, business models, regular content, and major recurring events. It is an approach rooted in the kind of large-scale engagement model that supports annual or semi-annual spectacles while keeping players involved between releases.
There are obvious advantages to applying proven infrastructure and operational experience to Halo. A consistently updated game can respond to community feedback, introduce maps and modes, refresh competitive play, and create events that give players a reason to return. Strong progression can make both casual and dedicated play feel rewarding, while broad social features can help turn a shooter into a place where groups meet regularly.
However, O'Connor warned against two particularly important mistakes: tying Halo too tightly to hardware launch cycles and abandoning the series' sandbox foundations. The first concern reflects the danger of treating a game primarily as a platform-selling showcase rather than a project that should ship when its systems are ready. The second is even more fundamental. If progression and recurring content become the main attraction, while the moment-to-moment combat loses its depth, Halo could end up looking larger on paper while feeling less like Halo in play.
A live-service model does not inherently conflict with the franchise. Halo has always had a long multiplayer tail, driven by competition, co-op, community creations, and social play. The question is whether ongoing content serves the game's core design or attempts to substitute for it. Players will forgive a lack of novelty far less readily if they feel the game is asking for constant engagement without delivering encounters worth revisiting.
Why the people making Halo matter most
Across all three paths, O'Connor's hiring suggestion may be the most consequential. Recruiting developers who know Halo's history, alongside people with experience building other successful shooters and online games, could give the next project a deeper bench of perspectives. That does not mean every former employee would agree on the series' future, nor that prior involvement alone guarantees a successful game. It means expertise should not be casually discarded at a time when the franchise is trying to define its next era.
The gaming industry has seen sustained layoffs, canceled projects, and studio restructures even while experienced developers remain available. O'Connor's point is that this pool includes people capable of bringing valuable ideas to a Halo revival. Some may understand the franchise's creative principles from years of direct work; others may bring lessons from different genres, engines, multiplayer communities, or production environments.
For Activision, the promise of "the greatest Halo game ever" creates enormous expectations. The phrase invites comparison not only with recent entries, but with the games that made Halo a defining name for Xbox and the broader shooter genre. Meeting that standard will take more than a familiar logo, a content roadmap, or a declaration of intent.
It will require a clear answer to a deceptively simple question: what should Halo feel like when players pick up the controller or sit down at a PC today? O'Connor's proposals do not settle that debate. They show that several viable answers may exist--but only if the team has the talent, time, focus, and willingness to build around what made the series matter in the first place.
Community
Discussion
Start the conversation.
No comments have been posted yet.