A recent social media controversy within the game development community has ignited a critical examination of the widely used, yet often undefined, phrase "core team." The catalyst for this industry-wide introspection was an in-depth story published by Gamesindustry.biz, detailing the innovative "distributed development" model employed by Fuse Games in the creation of Star Wars: Galactic Racer. This model, designed to manage the complexities of modern AAA game production, strategically categorizes the development team into three tiers, with a "core team" at its operational heart. However, a subsequent Bluesky post from the outlet, proclaiming that "Star Wars: Galactic Racer was made by a core team of 75 people," sparked immediate and widespread frustration among veteran developers, prompting a necessary dialogue about accuracy, recognition, and the underlying power dynamics in an increasingly interconnected industry.
The Spark: A Bluesky Post and a Lingering Question
The Gamesindustry.biz article meticulously broke down Fuse Games’ approach to developing Star Wars: Galactic Racer, a title that quickly garnered attention for its unique gameplay elements and, notably, the viral delight of the character "Biddy Blas." The distributed development framework described involves a central "core team" coordinating efforts with co-development partners, ex-development specialists, and various outsourcing entities. This complex, multi-layered structure is a common, albeit evolving, method for bringing large-scale games, which often require hundreds of specialized developers, to fruition.
The controversy erupted when the accompanying Bluesky post summarized the article by focusing predominantly on the "core team" of 75 individuals. While technically accurate in describing the internal Fuse Games staff, this phrasing inadvertently overshadowed the contributions of the vast network of collaborators. The game’s credits ultimately list approximately 1,100 people, a stark contrast to the 75 highlighted in the social media snippet. This discrepancy immediately resonated with developers, many of whom have experienced similar situations of their work being minimized or uncredited in public narratives. As Bryant Francis, the author of the original article and a senior editor at GameDeveloper.com, acknowledged, he was among those who voiced frustration over the phrasing, underscoring the sensitivity of this issue within the developer community. The incident quickly became a flashpoint, emphasizing the urgent need for precise language in describing the realities of contemporary game production, especially given the rising prevalence of distributed development models across the industry.
The Evolving Landscape of Game Production and Team Structures
Modern game development, particularly for AAA titles, has transcended the traditional model of a single, monolithic studio. The scale, ambition, and technical complexity of today’s leading games demand an unprecedented pool of talent and resources. According to various industry reports, the average AAA game budget can easily exceed $100 million, with development cycles spanning several years. To manage such colossal undertakings, studios increasingly adopt distributed development, co-development, and extensive outsourcing strategies.
This model allows lead studios to tap into global talent pools, leverage specialized expertise (e.g., animation, sound design, UI/UX, quality assurance), and mitigate financial risk. Instead of maintaining a massive in-house team that might face layoffs after a project’s completion, companies can scale their workforce dynamically. For instance, major publishers like Ubisoft, Electronic Arts, and Activision Blizzard frequently orchestrate projects across multiple internal studios and dozens of external partners, with credit lists for their flagship titles often running into the thousands. Red Dead Redemption 2, for example, reportedly involved over 2,000 developers across Rockstar Games’ global studios and partner entities. Similarly, Cyberpunk 2077 and the Assassin’s Creed series are well-known for their extensive co-development and outsourcing networks, reflecting a systemic shift in how large games are conceived and delivered. This distributed framework, while offering undeniable logistical and economic advantages, also introduces complexities in accurately attributing work and recognizing individual contributions.
Decoding "Core Team": Semantic Nuance and Structural Bias
The term "core team" itself is inherently ambiguous. Unlike roles such as "lead designer" or "senior programmer," it lacks an institutional or universally accepted definition within the game industry. Its interpretation can vary wildly between studios, projects, and even individuals. Lewis Packwood, features editor at Gamesindustry.biz, acknowledged this linguistic challenge in an email exchange, explaining that the term "core" was used in their article consistent with how Fuse Games’ CEO, Webster, described his internal team. Packwood clarified that both Webster’s comments and the article itself made it clear that Galactic Racer was the product of many different people in various locations, not solely the 75 staff at Fuse Games. He aptly noted that the industry might simply "haven’t yet developed the proper language to adequately describe it," highlighting a crucial gap in our professional lexicon.
However, the problem extends beyond mere semantics. The phrase "core team" often carries significant political and financial weight, circling dangerously close to creating "in-groups" and "out-groups" within the development hierarchy. Membership in a "core team" can be influenced by factors beyond merit, such as interpersonal relationships, founder proximity, or even exclusionary biases related to race, gender, or sexuality. This informal stratification can lead to tangible disadvantages for those outside the "core."
For instance, investors frequently prioritize the "strength of the core team" when evaluating pitches for new startups. They often view this central group as the resilient, adaptive force expected to steer a project through challenges, regardless of subsequent hires or layoffs. This investor logic, while understandable from a risk management perspective, inadvertently reinforces the idea that only a select few truly "matter." Furthermore, "core team" members are often the last ones remaining after studio layoffs, and they frequently receive the lion’s share of credit and recognition for a game’s success. In the worst-case scenarios, this dynamic can foster cliques of senior developers who take undue credit for others’ work, sometimes shielded from accountability due to their close ties to the central group. This phenomenon is exacerbated in distributed models, where external developers may be contractually barred from direct communication with "core team" members or even from publicly disclosing their involvement in a given game. This power imbalance, where creative direction and funding flow predominantly in limited directions, generates a palpable sense of injustice and anxiety among many developers, particularly those working on a contract or co-development basis, fueling their apprehension about a future built entirely on distributed models.
The Broader Repercussions: Devaluation, Recognition, and Career Impact
The impact of imprecise language and the "core team" narrative extends far beyond mere hurt feelings; it has tangible, detrimental effects on developers’ careers and the industry’s labor practices. When the success of a game is attributed solely to a small "core," the contributions of hundreds, sometimes thousands, of other individuals are effectively devalued. This systemic oversight can impede career progression for "non-core" developers, making it challenging for them to gain recognition, secure future employment, or negotiate better terms. Their work, though integral to the final product, becomes invisible in the dominant public narrative.
This issue is particularly critical in an industry increasingly grappling with labor concerns, including mass layoffs, crunch culture, and calls for unionization. The perception that only a select "core" receives recognition can erode morale, foster resentment, and undermine efforts to build a more equitable and transparent work environment. Developers, whose passion and skill drive the industry, deserve accurate and comprehensive credit for their efforts. The media, as a powerful voice shaping public perception, bears a significant responsibility in ensuring that its narratives reflect the full scope of collaborative creation, rather than inadvertently reinforcing existing power imbalances.
Towards a Precise Lexicon: Redefining Development Language
The need for a more precise and inclusive language to describe modern game development is undeniable. As the original article’s author, Bryant Francis, pointed out, the grammatical choice between active and passive voice plays a crucial role. Stating that "a core team of 75 made Galactic Racer" subtly implies that they were the sole agents of creation, whereas "Fuse Games developed Star Wars: Galactic Racer" allows for the industry’s understanding of subsidiary roles and partner studios without obscuring the main developer.
To achieve greater clarity, alternative phrasings could be adopted:
- "Fuse Games, with its core team of 75, led the development of Star Wars: Galactic Racer through a distributed model involving hundreds of co-development and outsourcing partners."
- "The development of Star Wars: Galactic Racer by Fuse Games leveraged a distributed model, supported by a core team of 75 and hundreds of external collaborators."
- "Fuse Games spearheaded Star Wars: Galactic Racer‘s creation, utilizing a distributed development framework where a core team of 75 directed the efforts of a broader network of co-dev, exdev, and outsourcing partners."
These formulations acknowledge the central role of the "core team" while explicitly recognizing the extensive network of contributors. The goal is not to diminish the work of the core team, but to accurately represent the collective effort that goes into creating a modern video game.
This isn’t merely academic nitpicking; it’s a fundamental issue of professional integrity and recognition. The consequences of misattribution were starkly illustrated by an incident at Summer Game Fest 2025, where founder Geoff Keighley lauded Clair Obscur: Expedition 33, stating it came from "a team of under 30 developers who bravely stepped away from big publishers to forge their own path." While the core team at Sandfall Interactive might indeed be small, the game’s credits reveal that over 500 people contributed to its development in various capacities. With an audience of 50 million viewers watching Summer Game Fest, such a statement, though perhaps well-intentioned, inadvertently dictates whose work "mattered" and whose was deemed "incidental." This example powerfully underscores how a single sentence from a prominent industry figure can shape public perception and potentially devalue the contributions of hundreds of dedicated professionals.
In conclusion, the "core team" controversy serves as a potent reminder that language is not neutral. It constructs reality, shapes perceptions, and directly impacts the livelihoods and recognition of individuals. As the game industry continues to evolve with increasingly complex and distributed development models, there is an imperative for all stakeholders – developers, studios, publishers, and media outlets – to collaborate on establishing a lexicon that accurately reflects the collaborative nature of game creation. By embracing transparent and precise communication, the industry can foster a more equitable environment where every contributor, regardless of their "core" status, receives the recognition they rightfully deserve. This commitment to clarity is not just good journalism; it is an essential step towards valuing the diverse talent that propels the interactive entertainment world forward.
About the Author
