ARC Raiders Flashpoint Update Patch Notes Explained

Quick Answer: The ARC Raiders Flashpoint update, Hotfix 1.36.1, went live on all platforms on 2026-07-09 and mainly fixed a duplication exploit plus an Expedition UI bug that showed Skill Points instead of Mystery Rewards for fourth-time players.

TL;DR: What shipped in Hotfix 1.36.1?

Hotfix 1.36.1 shipped a narrow but important stability pass on 2026-07-09, targeting a duplication issue and an Expedition-screen UI error on all platforms. The update also came with a clear anti-exploit warning: accounts gaining significant advantage through abuse may face bans, so this is one of those “don’t be cute with it” patches. Source

The wording from Embark makes this one feel less like a feature drop and more like a cleanup sweep. If you were hoping for new guns, maps, or a shiny progression system twist, this is not that kind of patch. If you wanted the economy to stop getting kneecapped by duplication abuse, though, this is exactly the kind of hotfix the game needed. For broader context on the game itself, see our arc raiders update today.

A few practical examples make the scope clearer. If you were carrying extra crafting materials from a duplication path while running Dam Battlegrounds, that value loop is the sort of thing this hotfix is meant to shut down. If you were checking the Expedition flow after a rough run and saw the wrong reward type on the screen, the fix matters because that is exactly when players make irreversible decisions. If your squad has been trading around items inflated by exploit-driven supply, the patch helps restore a more normal baseline for stash and extraction planning.

Winners: who benefits from the flashpoint update?

The biggest winners are honest players, Expedition runners, and anyone tired of seeing exploit-driven nonsense warp the in-game economy. Hotfix 1.36.1 protects legitimate progression by removing a duplication path and correcting a UI bug that could have caused confusion during Expedition decision-making. Source

Players who play the game straight

This patch favors players who earn their loot the normal way, because duplication issues tend to distort prices, inventory flow, and upgrade pacing. In extraction games, even a small exploit can snowball into a big “why is everyone suddenly rich?” problem, so closing it helps the whole ecosystem breathe again.

A simple example: if you were doing a clean loop through a contested zone, extracting with a modest haul, and then reinvesting into safer loadouts, that progression path is now less likely to be undercut by someone printing value through a loophole. Another example: if your squad has been pacing upgrades around what you can realistically bring out of a run on your own, you are less exposed to market or stash inflation caused by abuse. In practical terms, the patch protects the slow, repeatable grind that most players actually experience.

Fourth Expedition players

Players on their fourth Expedition are also clear winners, because the UI now stops showing Skill Points where Mystery Rewards should appear. That sounds minor until you’re staring at a menu trying to make a high-stakes call and the interface is basically gaslighting you.

The concrete cases here matter. If you were about to commit materials after a full run and the screen was giving you the wrong reward readout, that could easily send you down the wrong decision path. If you were coordinating with a squadmate who thought the menu showed a progression reward instead of a mystery payout, that confusion could ripple into a bad reroute or a premature reset. This fix helps fourth-time players make decisions on the reward model the game actually intends.

The anti-exploit crowd

Anyone who wants a fair wipe cycle, fair trading, and fair progression gets a net gain from this update. Embark’s note about continued bans is also a signal that the studio is treating exploit abuse as a live-service integrity issue, not a “we’ll deal with it later” annoyance.

That matters in more than one situation. If you are the kind of player who checks patch notes before logging in because you want to know whether the economy will be stable enough for a normal run, this is a favorable change. If you queue with randoms and do not want your session warped by someone stacking illegitimate value, enforcement language is part of the health of the game. If you are building around fair progression in a wipe-driven environment, this hotfix is aligned with your interests.

Losers: what got nerfed or removed?

The main losers are duplication abusers, and by extension anyone benefiting from inflated item flow caused by exploit abuse. The patch does not list a classic balance nerf to weapons or gear; instead, it removes a problematic loophole and tightens enforcement around it. Source

Duplication exploit users

If you were using the duplication issue to gain significant advantage, this is the bad-news section. Embark explicitly says bans will continue for accounts that have been gaining significant advantage, so the update is not just a fix—it’s a warning shot.

Two examples make the loss clearer. If someone was stockpiling materials through a repeatable glitch and using those materials to skip normal progression gates, that route is now under direct pressure. If a group was moving duplicated items between stashes to create a fake supply cushion for repeated raid attempts, the patch is aimed at shutting that down. The practical effect is that abuse no longer has the same easy payoff, and the risk now sits visibly next to the reward.

Players relying on bugged UI reads

No, this doesn’t punish casual mistake-making, but it does remove one awkward crutch: bad information on the Expedition screen. If someone was making decisions based on the incorrect Skill Points display instead of Mystery Rewards, that misleading edge is now gone.

For players this mostly shows up in edge-case planning. If you were comparing two late-game options and using the broken display to justify one of them, that bad read is corrected. If your squad had learned to “work around” the wrong screen by mentally compensating for it, you now need to retrain that habit so you are not making decisions on old assumptions. The loss here is really the loss of ambiguity that some players had gotten used to.

Anyone hoping for content-heavy changes

If your wishlist was full of weapon tuning, new zones, or progression overhauls, this hotfix leaves that whole pile untouched. In other words, no big meta shake-up here—just housekeeping with consequences.

A couple of concrete examples: if you were waiting for a shotgun balance pass before rebuilding your close-range kit, this patch does not give you that pivot. If you wanted a new map route to open up your farming loop, you are still working with the same geography. If you were hoping the update would change how a full squad handles ARC pressure in high-risk interiors, it does not. The loss is not mechanical power, but expectation management.

What should you do differently starting today?

You should restart your game, stop leaning on any exploit-adjacent behavior, and check your Expedition flow more carefully now that the UI is corrected. That’s the practical takeaway from the arc raiders flashpoint update: less improvisation, more clean play. Source

A useful mindset shift is to treat the patch as a reset on assumptions. If you were tolerating weird menu behavior because it seemed harmless, that is no longer a reason to trust it. If your route planning depended on the game silently absorbing an exploit-shaped edge case, rebuild that route now instead of later. If your crew usually ignores hotfix notes, this is one of the updates worth reading before the next run.

Immediate player action items

• Restart the game so the hotfix actually downloads and applies.
• Avoid any duplication-related behavior, even if you think it is “just testing.”
• Re-check Expedition screen decisions on your fourth Expedition, since the displayed reward info has been corrected.
• Keep an eye on your account activity if you previously interacted with bugged systems; this patch comes with explicit enforcement language.
• If you plan your runs around economy stability, this is a good time to reassess routes and stash usage.

One practical example: if you normally log in, sort your stash, and jump straight into a run, do the stash review after confirming the patch has landed so you are not making decisions off stale assumptions. Another example: if your squad uses voice comms to coordinate who carries what, confirm that everyone is reading the same corrected Expedition information before committing. A third example: if you have been holding items because you expected some exploit-driven value swing, stop treating that as a reliable strategy.

Farm route and progression habits

This patch doesn’t change a farming route directly, but it does change the reliability of the game state around loot and rewards. That means your best move is to favor clean, repeatable extraction patterns over risky behavior that depends on shaky systems.

A good rule of thumb for the current meta:

• Play as if economy integrity matters, because it does.
• Double-check reward screens before committing to a run plan.
• Avoid stockpiling through anything that feels like an edge-case workaround.
• If you were delay-claiming or gaming Expedition rewards, stop and verify everything after the hotfix.

In practice, that means a few common habits should change. If you usually chain the same fast route through a loot pocket and rely on stale knowledge about what the reward screen will say, slow down and verify instead of autopiloting. If you like to run a light kit for speed and then convert loot into upgrades later, keep that loop, but drop any assumptions that duplicated economy will bail you out. If your progression plan depends on squeezing extra value out of every extraction, the safest answer is still consistency: reliable entries, reliable exits, and no system abuse.

Why this hotfix matters for the larger ARC Raiders experience

This hotfix matters because ARC Raiders is an extraction game, and extraction games live or die on trust. The game itself is built around high-stakes multiplayer survival in a hostile future Earth overrun by ARC, so when bugs start handing out free value, they hit harder than they would in a softer progression game. The Steam page frames the game as a multiplayer extraction adventure set in a lethal future Earth, and that kind of design really depends on fairness holding together. Source

That broader context is why even a small patch can be important. The current player base is large enough that live-service integrity matters, and third-party tracking shows the game at 38,670 current players with an all-time peak of 481,966, which is exactly the sort of scale where exploit fixes need to land fast. Source

Put differently, this is not only about one bug. In a game like this, a duplication issue can ripple into squad behavior, loot expectations, progression pacing, and the social trust that sits underneath every extraction. If one player in a group is using a loophole while another is playing clean, the game stops feeling like a shared system and starts feeling arbitrary. A hotfix like this pushes back toward a world where the outcome of a run is supposed to reflect the run itself.

There is also a longer-term signal in the enforcement language. When a studio says it will continue banning accounts that gain significant advantage, it is drawing a line around what counts as acceptable play. That is important because extraction games do not just need content cadence; they need rules that remain legible under pressure. The flashpoint update is less about novelty and more about preserving the conditions that make progression, loot, and risk feel meaningful.

Patch impact at a glance

Area	What changed	Why it matters
Duplication	Fixed on all platforms	Protects fairness and the in-game economy
Expedition UI	Corrected fourth-Expedition reward display	Prevents bad reward decisions
Enforcement	Continued bans for major exploit abuse	Signals stricter live-service policing

A few scenario-based readouts help here. If you are a solo player doing low-profile scavenging runs, the duplication fix helps keep your return on effort honest. If you are in a duo or trio that routes around Expedition milestones, the corrected UI prevents one partner from making the wrong call off a bad screen. If you are a player who mostly watches the metagame instead of chasing it, the biggest impact is that the patch tries to keep the broader environment from sliding into exploit-driven chaos.

Common Mistakes

Assuming a hotfix only matters if it adds content

Players often skip cleanup patches because they are looking for new weapons or zones, but exploit fixes can matter more to the day-to-day game state. This happens because content is visible and fixes are abstract. The concrete fix is to read hotfix notes for economy, UI, and enforcement changes before deciding whether the patch is worth your attention.

Continuing old routing habits after a UI correction

It is easy to keep following muscle memory after the Expedition screen is fixed, especially if you had already built a habit around the wrong display. Players fall into this because the old workflow felt efficient. The fix is to pause on your next Expedition, re-read the reward info, and rebuild the habit around the corrected UI instead of your memory of the bug.

Treating exploit testing as harmless curiosity

A lot of players tell themselves they are only checking whether something still works, but that still puts them near the edge of abuse. This happens because the line between curiosity and advantage feels fuzzy in live-service games. The fix is simple: do not test duplication-related behavior at all, and treat anything that looks like a workaround as off-limits.

Ignoring account-risk language in patch notes

Some players read “bans will continue” as background flavor rather than a direct warning. That mistake happens because enforcement statements are easy to skim past. The fix is to treat that language as operational, not decorative, and stop using any account patterns that depend on bug exploitation.

Planning progression around unstable or inflated value

Players sometimes keep hoarding or spending as if exploit-driven supply conditions will last forever. That mindset persists because it can feel profitable in the moment. The fix is to re-anchor your plan to normal extraction value: spend around what you can reliably earn, not around what a broken system temporarily handed out.

Relying on squad consensus instead of a fresh patch check

If one player in the group assumes the patch landed and another assumes it did not, the squad can make conflicting calls. This happens because teams often trust one person to keep up with patch notes. The fix is to confirm the hotfix state before the run and have one person re-check the key change, especially on the first session after maintenance.

Pro Tips

Tip 1. Re-baseline your stash after the patch

When you log in after the hotfix, compare your current stash shape against what you normally expect at the same point in the week. This matters most if you were running repeated extraction loops or holding reward items for later conversion. The trigger is any time your inventory looks unusually inflated or oddly thin relative to your normal cadence.

Tip 2. Use the corrected Expedition screen as a decision gate

The best use of the UI fix is not passive awareness but active verification. When you hit the fourth Expedition flow, stop long enough to read the reward display before committing materials or locking in a route. The setup is simple: any time your run is about to pivot on Expedition rewards, make the screen a hard checkpoint instead of a glance.

Tip 3. Audit routes that depend on rapid inventory churn

Fast loot rotation can hide bad assumptions about item flow. If your usual setup involves quick stash swaps, back-to-back extractions, or a “grab everything and sort later” loop, use the hotfix as a reason to clean that up. The trigger is any route where a single run’s value depends on repeated transfer behavior rather than one clean extraction.

Tip 4. Rehearse clean squad handoffs

If you play in a fixed group, assign one person to call out patch-sensitive decisions until everyone has re-read the notes. This helps when the team is deciding whether to extract early, keep pushing, or bank materials. The setup is any group session where reward information or stash state could change the plan mid-run.

Tip 5. Favor low-ambiguity runs for a few sessions

After an exploit fix, the best way to rebuild confidence is to reduce variables. Run familiar zones, predictable loadouts, and ordinary extraction paths for a short stretch so you can see how the post-hotfix game feels in practice. The trigger is the first few sessions after the patch, especially if you had previously encountered the duplication issue or the incorrect Expedition display.

Tip 6. Separate “good value” from “broken value”

If something feels unusually profitable, ask whether it is profitable because you are playing well or because a system is misbehaving. That distinction matters after a patch like this. Use it whenever you are tempted to hold, duplicate, or reroute around a suspiciously easy gain. The correct response is to preserve value you earned and drop anything that depends on a loophole.

Related Guides

• related guide for a broader ARC Raiders live patch tracker that collects update notes in one place.
• related guide for a beginner walkthrough covering early extraction routes, stash habits, and safe progression.
• related guide for a weapon and loadout guide focused on practical builds for solo and squad play.
• related guide for an economy guide explaining item value, inventory discipline, and upgrade priorities.
• related guide for an Expedition planning article that breaks down reward decisions and progression checkpoints.
• related guide for a troubleshooting guide covering launch issues, patch verification, and common client-side problems.
• related guide for a PvE threat guide on surviving ARC encounters, positioning, and escape timing.
• related guide for a squad coordination guide on callouts, split roles, and extraction discipline.

Sources

• https://steamstore-a.akamaihd.net/news/externalpost/steam_community_announcements/1836506165583167
• https://store.steampowered.com/app/1808500/
• https://api.steambase.io/games/1808500