ARC Raiders PvE Mode Datamined: Loot, Matchmaking & What We Know

What did the ARC Raiders PvE datamine find?

The current discussion comes from a community datamine thread shared on September 12. The poster describes references to a matchmaking option and a custom PvE loot configuration, while acknowledging that the implementation is unclear.

Three strings feature in the circulating reports:

enable_pve_only_matchmaking=false
GameplayOption.Social.PvEOnly
RoundConfiguration.Loot.PvE

Noclip's September 12 report attributes the discovery to dataminer Silarious and describes references across feature flags, matchmaking, UI, and loot settings. It also repeats the caution that there isn't enough information to say exactly how a mode would work.

Several related labels are a reason to investigate. They do not show whether the code behind them is complete, active, or intended for public release. Features can be tested internally, changed, abandoned, or left dormant for months. We have not independently inspected the game build behind these reports.

What does the false value mean?

Taken literally, false means the reported flag is disabled in that configuration. That is narrower than proving that PvE matchmaking is disabled everywhere. A client file does not, by itself, establish which settings a live service uses or whether another configuration overrides them.

It also tells us nothing about a release date. The claim that PvE is definitely coming on October 8 goes beyond what these strings establish.

The remaining questions are substantial. Would other human Raiders inhabit those matches? Would player damage be disabled? Could PvE be a rotating map condition or a separate activity? The labels alone don't answer any of those questions.

How does existing matchmaking fit into this?

ARC Raiders already adjusts the kinds of players you're likely to meet based on how you play. In its May Notes on the Matchmaking System, Embark describes a continuous range of playstyles. Cooperative Raiders are more likely to meet similarly cooperative players, while people who seek fights are more likely to encounter others doing the same.

The studio explicitly says that this does not create guaranteed PvE-only servers. Even a peaceful lobby retains the possibility that somebody will shoot you. Our aggression-based matchmaking guide explains the distinction in more detail.

Update 1.36.0 made another relevant change: Solo, Duo, and Trio behavior is tracked separately. Embark's example is a player who quests peacefully alone and seeks PvP with friends in Trio. Playing one way in one squad size no longer changes the playstyle profile for another.

Update 1.39.0 then began testing the removal of defensive PvP from the playstyle estimate entirely. During that test, starting a fight affected the estimate; defending your squad did not.

These changes help explain why switching squad size can produce a different experience. They do not establish that a protected PvE queue is already built or ready to ship.

Friendly lobbies show the appeal, with limits

Cooperation is already part of the game. Embark's matchmaking explanation describes strangers helping each other, spontaneous musical groups, negotiations, and sudden betrayals. Those interactions can make a round feel closer to cooperative PvE without changing its underlying rules.

A player who spends most raids helping strangers may reasonably want that experience more consistently. Someone else may enjoy a friendly encounter precisely because either player could have chosen to fight. A protected mode changes the meaning of that choice.

Personal accounts of peaceful rounds are useful examples of what players enjoy. They aren't controlled tests of matchmaking, and one player's experience cannot guarantee what another player will encounter in a different region, squad, or session.

Why could separate PvE loot settings matter?

RoundConfiguration.Loot.PvE may be the most consequential label in the report. Its name suggests that PvE could have its own loot configuration, although the report doesn't establish how that configuration is used.

ARC Raiders' raid loop includes equipment loss. You spend ammunition and consumables, search for valuable items, fight ARC, and try to extract. Another Raider can kill you and take what you're carrying. Removing that threat could increase successful extractions and reduce the rate at which players lose their gear, unless other risks rise enough to compensate.

That creates a balance question: how much should a protected raid reward, and where should those rewards be usable?

The datamine poster speculates that a separate loot pool could mean lower rewards. The actual values are missing. A label containing Loot.PvE cannot tell us whether item rarity, container contents, blueprints, or boss drops would change at all.

There are several possible uses for separate settings. They could reduce general valuables, increase ARC crafting materials, change the rewards from particular encounters, or give an activity a different distribution of items. Those are design possibilities, not discoveries in the files.

How could a PvE mode balance risk and rewards?

Players in the datamine discussion propose different rewards and separate progression. Harder machine encounters provide another option. Each approach solves a different part of the problem, and they could be combined.

Reduced PvE loot and better PvPvE rewards

One approach would make protected raids a dependable place for questing, exploration, learning bosses, and gathering materials, while reserving stronger rewards for matches with unrestricted PvP.

A self-described friendly player in the September 12 discussion argues for a more dangerous standard queue with better loot if players gain a protected option. The tradeoff is easy to explain: choosing the greater risk gives access to the greater reward.

Finding the right gap would be harder. Cut rewards too severely and PvE players could feel that their preferred mode offers an incomplete progression path. Make the difference too small and protected farming might become the most efficient way to prepare for PvPvE, even for players who would rather spend their time fighting.

Separate stashes and progression

A separate economy would keep equipment earned in PvE within PvE. A player could not spend hours farming protected raids and then bring the resulting stockpile into the standard queue.

That addresses transfers between modes. It doesn't automatically give either mode a healthy economy or a satisfying endgame. PvE could still accumulate more equipment than its encounters consume.

It also introduces costs for people who enjoy both styles. They might have to unlock blueprints, build a stash, and work through progression twice. Every crafting cost, Trader offer, and future progression change would need to make sense in both environments, whether the studio balances them together or separately.

Harder ARC encounters

PvE could retain valuable rewards by giving players more dangerous machines to overcome. More enemies, combinations of major ARC, and objectives that force squads to move would create different pressures from simply increasing enemy health.

In a discussion of the Chinese client's map conditions, players imagined maps crowded with Rocketeers, Matriarchs, and other threats. Those suggestions are enthusiasm, not a practical balance specification, but they point toward a kind of challenge some PvE players want.

Demanding encounters would give upgraded weapons a job. Players would spend ammunition, healing items, grenades, and expensive equipment trying to survive. A good drop would matter because there was something difficult enough to use it against.

Difficulty would still need to suit the activity. A mode intended for relaxed exploration has different requirements from a coordinated boss operation. Treating all PvE players as one audience risks disappointing both groups.

What happens when your stash is full?

The progression problem extends beyond how much loot a raid gives. Once players have the weapons and materials they want, another successful extraction may add little to their next session.

There are plenty of reasons to keep playing without needing another upgraded gun. Exploring the Rust Belt, helping strangers, fighting bosses, completing projects, or preparing equipment for friends can be satisfying in their own right. A player who enjoys collecting may also want to keep collecting.

For players motivated by equipment progression, though, a growing stash needs worthwhile uses. If incoming gear consistently exceeds the cost of raids, clearing inventory can become more pressing than finding the next reward.

Harder operations, expensive optional projects, and rewards tied to challenging objectives could help. Their value would depend on whether players enjoy the activities enough to spend their equipment on them. Raising costs alone would give them another bill to pay.

How does Frozen Trail relate to the PvE discussion?

Embark's Frozen Trail announcement gives October 8, 2026 as the release date and describes it as the largest update since launch. Confirmed plans include a frozen map with greater verticality and underground threats, new ARC, and a high-level ARC Operation emphasizing cooperation and difficult decisions.

The studio also describes longer-term progression through Outposts, Skill Tree adjustments, and changes to Raider Decks. Our Frozen Trail development update covers the earlier announcement and the shift to larger updates.

A demanding operation could give well-equipped players a reason to spend their resources. That makes it relevant to the economy question, whether or not a dedicated PvE mode appears.

The Operation has not been identified as the mode suggested by the datamine. Cooperative objectives can exist within PvPvE, as they already do elsewhere in the game. Linking these two developments is an interpretation of how they might fit together.

Is PvE coming on October 8?

There is no confirmed PvE release date in the sources reviewed as of September 18. October 8 is the announced date for Frozen Trail. Its official feature announcement does not list a dedicated PvE-only matchmaking option.

The datamine appeared less than a month before the update, which helps explain the speculation. Timing cannot establish that a feature will ship. A direct announcement would be needed to turn that proposed connection into a release claim.

How could cooperative boss rewards work?

Large cooperative encounters introduce another problem. Suppose ten Raiders help destroy a major ARC and one valuable item drops. The fight may have rewarded teamwork, but the loot now rewards whoever reaches it first.

Individual completion rewards could reduce that conflict. Other possibilities include personal reward rolls, contracts, boss-specific currencies, or rewards based on meaningful participation. A system like that would need to recognize useful support as well as damage, or it could punish players who keep the group alive.

This is a design proposal, not a reported Frozen Trail feature. It matters because increasing the scale of cooperative battles also increases the need to decide who earns what. A shared physical drop works differently from a reward that every participant receives, and each adds resources to the economy at a different rate.

What is the Chinese client's Security Protocol?

A community translation posted in June describes a Chinese-client condition called Security Protocol. According to that translation, restored communications enable protection against damage from other Raiders, while players who disconnect remain a threat.

That describes a protected starting state with a route to hostility. It would change the first question at an encounter: a player would need to leave that protection to become a threat. Betrayal could remain possible even though friendly interaction is the default.

This is a community translation of a separately customized client. It is not an official global announcement, and it does not establish that the same rules will arrive worldwide.

The global labels PvEOnly and pve_only_matchmaking sound more absolute than that arrangement. Interpreted literally, they could refer to matches with no PvP at all. We still don't know whether those names describe a finished mode, a test, a map condition, or something else.

What has Embark said about demand for PvE?

In a March interview with Pocket Tactics, design director Virgil Watkins said the strength of players' engagement with PvE had surprised the studio and was influencing its plans. He described a "strong appetite" for that content.

Watkins also defended the intentional coexistence of cooperation and competition. Supporting players who prefer PvE does not, by itself, amount to a promise to remove the possibility of player conflict.

That distinction is why a protected option would be a substantial change. It would let players opt out of a source of uncertainty the studio has repeatedly treated as central to the game.

What could happen to the standard queue?

Some objections to PvE focus on who would remain in PvPvE. If players who never want to fight choose a protected queue, the remaining population could become more aggressive. The scale of that effect would depend on participation, region, squad size, and how matchmaking responds.

For players who value unpredictable encounters, friendliness matters because another Raider could have chosen violence. A protected lobby offers a different social experience. Both can appeal to players, but a new queue would need to give people enough reason to return to each one.

The strongest part of the loot argument is that rewards offer one way to shape those choices. Separate settings could support different activities and risks, if that is what the reported label is eventually used for. We do not yet have the rules that would show how Embark intends to do it.

ARC Raiders PvE mode FAQ

Has Embark announced a dedicated PvE mode?

The sources reviewed for this article do not contain an official announcement. The September report concerns alleged references in game files, and their intended use remains unconfirmed.

What is enable_pve_only_matchmaking=false?

It is a reported configuration flag whose name refers to PvE-only matchmaking. Its value suggests a disabled default in that file. It doesn't establish live server settings, a working public option, or a launch plan.

Can friendly matchmaking guarantee that nobody shoots me?

No. Embark's official matchmaking explanation says similar playstyles are more likely to meet, but the system doesn't guarantee protection from other Raiders.

Will PvE loot be reduced?

That is unknown. The reported RoundConfiguration.Loot.PvE label suggests separate settings, but the reviewed material provides no reward values that establish a reduction.

Would PvE and PvPvE share progression?

That is unknown. Shared progression and separate inventories are possible designs. Neither has been confirmed for a global PvE mode.

Is October 8 a confirmed PvE release date?

No. October 8, 2026 is Frozen Trail's announced launch date. Connecting a dedicated PvE queue to that date remains speculation.

Is Security Protocol the same as the datamined mode?

There is no evidence establishing that connection. Community translations describe protection that players can leave, while the reported global labels refer to PvE-only matchmaking.

What to watch for next

The useful next evidence would be an official explanation of the rules: who can enter, whether player damage is possible, what rewards can leave the activity, and whether progression is shared. A loot table or a named configuration needs that context before it tells us much about the experience.

A protected queue could make cooperative exploration easier to choose. Keeping equipment progression satisfying would also require challenges and rewards that give those players a reason to head back Topside with the gear they've earned.