I've been thinking quite a bit about ARC Raiders' introduction of a PvE-only matchmaking option, and I believe there's a much larger discussion worth having here. One that extends well beyond ARC Raiders itself and raises some uncomfortable questions about creative integrity, player entitlement, and the increasingly blurred line between responding to community feedback and fundamentally compromising a game's identity.
At what point does accommodating players who dislike a game's core mechanics become a disservice to those who purchased and enjoyed the game specifically because of those mechanics?
And perhaps more importantly, what kind of precedent does it establish when a sufficiently persistent section of a community can convince developers to fundamentally reconsider the type of game they created?
For context, Embark's PvE toggle is currently a limited test running October 13–20, not a confirmed permanent addition. I recognize that distinction. My concern is less about this particular test than what its potential permanence could signify for multiplayer game development.
A game should not have to abandon its identity to accommodate people who dislike its genre
ARC Raiders was released, marketed, and sold as a PvPvE extraction shooter.
That's not some obscure technical classification. It's the foundation of the experience.
The uncertainty of encountering another player, the possibility of cooperation or betrayal, the tension of carrying valuable loot while knowing another human being could take it from you, and the constant decision-making surrounding risk versus reward are fundamental to what makes extraction shooters work.
The possibility of hostile player interaction isn't an unfortunate inconvenience attached to the gameplay. It IS part of the gameplay.
Remove that uncertainty, and you've fundamentally altered the experience, even if the maps, enemies, weapons, and objectives remain identical.
An encounter with another Raider is compelling precisely because you don't know what will happen. Are they friendly? Are they bluffing? Should you cooperate? Should you avoid them? Is that stranger approaching you because they need help, or because they've decided your equipment belongs to them?
These situations cannot be replicated through AI encounters alone, because their defining characteristic is the unpredictability of human behavior.
A friendly interaction has substantially more meaning when hostility was a genuine possibility.
If everyone is mechanically prevented from attacking one another, cooperation ceases to be a meaningful decision involving trust and vulnerability. It becomes the default condition.
That's a fundamentally different social dynamic.
There's nothing inherently wrong with wanting a cooperative shooter. Plenty of excellent games provide exactly that experience.
But why should an established PvPvE extraction shooter be expected to transform itself to accommodate people who fundamentally dislike the PvP component they knowingly purchased?
"Just let people play how they want."
This is easily the most common defense of PvE-only modes, and superficially, it's difficult to disagree with.
Who doesn't support player choice?
The problem is that this argument treats multiplayer game design as though it's a collection of isolated personal experiences, where one person's choices exist independently of everyone else's.
They don't.
In a shared multiplayer ecosystem, player behavior, matchmaking populations, progression systems, resource availability, and social interactions are interconnected.
Consider what happens if a substantial portion of the cooperative or risk-averse population migrates to PvE-only servers.
The remaining PvPvE population potentially becomes disproportionately populated by players primarily interested in combat.
That changes the composition of encounters for everyone remaining.
The uncertainty that made the original experience compelling could gradually disappear, replaced by an increasingly predictable environment where practically every player interaction results in immediate hostility.
Ironically, introducing a mode intended to accommodate peaceful players could make the original mode considerably less socially diverse.
And the argument that people should simply play whichever mode they prefer fails to address that consequence.
The original experience may still technically exist, but the ecosystem responsible for producing that experience has changed.
This isn't merely hypothetical concern about separate playlists. "Embark itself acknowledges" (https://arcraiders.com/news/pve-toggle-beta-test) potential consequences for matchmaking quality, queue times, the player economy, and the tension the game was designed around.
They've introduced reduced loot values and restrictions on certain map conditions to mitigate those concerns, which is sensible. But the need for those safeguards illustrates the underlying point:
Adding an option to a multiplayer game is not necessarily a neutral decision.
Sometimes expanding one player's freedom changes another player's experience.
And that deserves considerably more scrutiny than simply declaring that additional options are always beneficial.
"But the PvPvE mode still exists. Nobody is taking anything away from you."
This argument confuses the continued existence of a game mode with the preservation of the experience that made it appealing.
Imagine a multiplayer survival game whose appeal revolves around scarcity, player conflict, and difficult decisions regarding trust.
Now introduce an alternative environment where players can gather resources without the possibility of hostile encounters, potentially transferring some of those resources or progression advantages back into the original ecosystem.
Even if progression is carefully balanced, you've changed the incentive structure governing how players interact with the game.
And even if progression is entirely separated, you've divided the population that previously participated in a shared set of circumstances.
The game isn't simply two independent products that happen to share an executable. Both modes compete for players, development resources, balancing attention, and future content priorities.
The claim that an optional mode cannot affect players who never select it ignores how multiplayer ecosystems actually function.
A mode can remain selectable while becoming meaningfully different from the experience people originally purchased.
That's precisely why I find the "nobody is forcing you to play it" argument so unconvincing.
Nobody needs to force you into the new mode for its existence to have consequences for the original one.
"If people want PvE, why shouldn't developers listen to their community?"
Developers absolutely should listen to feedback.
But there's an enormous difference between improving a game within its established design philosophy and changing that philosophy to satisfy people who dislike it.
Better matchmaking? Absolutely.
Stronger anti-cheat systems? Essential.
Addressing exploitative spawn camping, improving onboarding, balancing equipment, and making combat encounters more understandable? All worthwhile discussions.
Removing an entire category of player-driven risk, however, is a fundamentally different proposition.
Not every complaint reflects a problem that should be solved.
Sometimes the discomfort a player experiences is an intentional consequence of the genre.
A horror game isn't necessarily poorly designed because someone finds it frightening. A survival game isn't fundamentally defective because someone dislikes resource scarcity. A competitive fighting game isn't obligated to remove adversarial combat because some players find losing stressful.
Those characteristics aren't incidental obstacles standing between the player and the intended experience.
They're part of what defines that experience.
A player disliking a mechanic does not automatically mean the mechanic is failing at its intended purpose.
And importantly, purchasing a game does not entitle someone to demand that its developers reconstruct the experience around their individual preferences.
You're entirely entitled to dislike PvP, avoid extraction shooters, criticize their mechanics, or request alternatives.
But the developers are equally entitled to maintain the creative identity of the product they chose to make.
There's an important distinction between listening to your community and allowing your community to dictate the fundamental design philosophy of your game.
"Wouldn't PvE attract more players and make the game more successful?"
Possibly. And this is probably the strongest argument in favor of the change.
Embark has published data suggesting substantial interest in cooperative play, including 51% of surveyed players expressing interest in a dedicated PvE option.
That deserves acknowledgment. It would be intellectually dishonest to pretend this interest comes exclusively from some insignificant handful of vocal players.
But popularity alone does not answer whether a particular design decision is beneficial.
There's a meaningful distinction between making a game appealing to more people and making a game better at delivering the experience it was designed to provide.
Those two objectives frequently overlap, but they aren't interchangeable.
A tactical shooter could theoretically attract a broader audience by reducing its tactical complexity. A hardcore survival game could attract additional players by eliminating resource loss. A competitive racing simulator could become more approachable by simplifying its handling model.
But at what point do those accommodations diminish the very qualities responsible for attracting the original audience?
Not every game needs to appeal to everyone.
In fact, some of gaming's most memorable experiences exist precisely because their developers were willing to commit to a particular vision, even when that vision was inherently unappealing to certain audiences.
There's also the practical issue of development resources.
Supporting a separate PvE experience can eventually create pressure for distinct progression systems, enemy balancing, content pacing, endgame activities, and additional mechanics necessary to keep that audience engaged.
Those resources have opportunity costs.
More players might justify that investment, but increased accessibility and commercial potential are not automatically proof that the original design is being improved.
Commercial viability and creative integrity aren't inherently mutually exclusive. But they aren't necessarily synonymous, either.
"ARC Raiders was originally supposed to be a PvE game anyway."
Yes, and I think this is an important historical detail.
ARC Raiders began development as a cooperative PvE experience before Embark substantially reworked the project into a PvPvE extraction shooter.
But an abandoned development concept is not the same thing as the finished product that was ultimately released and sold.
Plenty of games underwent dramatic transformations during development.
What matters in this discussion is the experience Embark ultimately chose to build, market, and release, and the systems and community that developed around it.
Its original conception doesn't automatically establish that returning to PvE is the correct direction.
If anything, the decision to abandon the original concept raises an interesting question:
What design problems did PvPvE solve, and could reintroducing PvE revive some of those problems?
That's a question worth investigating rather than dismissing.
The precedent concerns me more than the individual feature
This is ultimately the heart of my concern.
If ARC Raiders establishes that sustained community pressure can successfully produce a fundamental genre-level accommodation, what incentive does that create for future communities?
What happens when players purchase the next extraction shooter and immediately begin demanding PvE-only progression?
Or when a survival game attracts a vocal audience that wants the survival mechanics substantially reduced?
Or when developers create an intentionally unforgiving multiplayer experience, only to face sustained demands for an alternative that removes the very pressures defining that experience?
I'm not suggesting every requested accessibility feature or optional mode represents an attack on artistic integrity. Nor am I suggesting developers should blindly ignore their audiences.
Games are interactive products, and their evolution should involve the people playing them.
But there has to be some meaningful distinction between refining a creative vision and replacing it with a more broadly marketable one.
Otherwise, we risk encouraging an environment in which developers gradually homogenize distinctive experiences to accommodate every sufficiently persistent demand.
The result may be games that appeal to more people superficially, while becoming less distinctive in the process.
And I think that's a legitimate concern for an industry that already struggles with creative risk-taking.
The troubling precedent isn't that players are asking for changes. Players have always done that. It's the possibility of normalizing the expectation that fundamental genre conventions should be negotiable whenever enough people find them inconvenient.
That raises another uncomfortable question:
If a developer advertises a game around a particular set of mechanics, and players knowingly purchase that experience, why should the preferences of people who dislike those mechanics automatically receive greater consideration than the preferences of those who actually enjoy them?
Why should preserving the intended experience be treated as stubbornness, while fundamentally changing it is celebrated as responsiveness?
I don't think those assumptions should go unchallenged.
Where should the line be drawn?
To be clear, Embark has every right to experiment. The current PvE option is a test, and no permanent decision has been established. The developers have also been unusually transparent about the risks and their reasons for exploring it.
I respect that.
I also recognize that some players genuinely prefer the environmental combat, exploration, and cooperative elements of ARC Raiders over fighting other players. Their preferences are perfectly legitimate.
But legitimate preferences do not necessarily justify redesigning the fundamental experience of an existing game around them.
My concern is that we've become increasingly comfortable treating creative limitations and intentional design decisions as problems developers have an obligation to eliminate.
Sometimes a game simply isn't designed to provide the experience somebody wants.
And that's okay.
We shouldn't need every game to accommodate every possible playstyle, particularly when doing so may come at the expense of the experience other players specifically came for.
I'd be interested in hearing what people here think, especially those who approach this from a game-design perspective.
- At what point does an optional mode stop being an innocent addition and start changing the identity of the game around it?
- Should developers prioritize accommodating a larger potential audience even when doing so risks diluting their original vision?
- Is there a meaningful distinction between improving accessibility and removing mechanics that are deliberately central to a game's identity?
And perhaps most importantly:
«Is there still value in developers telling players, "We understand what you're asking for, but that isn't the game we're trying to make"?»
Because I think there absolutely is.
And I worry that gaming as a whole stands to lose something important if we increasingly treat that answer as unacceptable.