patch_notes · 2026-07-24

ARC Raiders Patch Notes Explained: Hotfix 1.36.1

ARC Raiders update Hotfix 1.36.1 fixes duplication abuse and an Expedition UI bug. Here is what changed, who benefits, and what to do next.

I’m expanding the article in place and preserving the required heading order exactly. I’m checking where the existing sections are thin, then I’ll add the missing support sections and concrete examples without introducing any unverified patch facts.# ARC Raiders Patch Notes Explained: Hotfix 1.36.1

Quick Answer: ARC Raiders update Hotfix 1.36.1, pushed on 2026-07-09, targets a duplication exploit and fixes the Expedition screen UI bug that showed Skill Points instead of Mystery Rewards on fourth Expedition runs.

TL;DR

Hotfix 1.36.1 is a narrow but high-impact arc raiders update focused on exploit suppression and UI correction, with the patch landing on 2026-07-09 and explicitly requiring a restart to download Source.

The important part is not new content, balance tuning, or weapon reworks. This is a live-service maintenance pass aimed at protecting the economy and preventing misinformation in one of the progression screens. Embark also signaled that exploit abuse can still trigger bans if a player has gained significant advantage, so the enforcement side matters as much as the technical fix Source.

For context, ARC Raiders is still sitting in a strong public position: Metacritic lists an 86/100 critic score across 65 professional reviews Source, and SteamDB-style tracking shows 38,670 current players with an all-time peak of 481,966 Source. This hotfix is about preserving that live-service stability, not changing the core meta.

In practical terms, that means two things for most players. First, if you were dealing with the Expedition screen on a fourth run, your reward readout should now be trustworthy again. Second, if you were benefiting from any duplication behavior, the window is shut and the enforcement risk is now part of the equation. In extraction games, that kind of maintenance can matter more than a flashy content drop because it changes how safe the economy feels from one session to the next.

What Shipped

Hotfix 1.36.1 shipped two confirmed changes and one operational warning.

• A duplication issue was mitigated across all platforms Source.
• The Expedition screen UI bug was fixed for players on their fourth Expedition, where Skill Points were incorrectly displayed instead of Mystery Rewards Source.
• Players were instructed to restart the game to download the hotfix Source.

That is the full confirmed scope from the patch context. There is no evidence here of weapon buffs, perk adjustments, traversal changes, or map edits. Treat it as a systems fix rather than a gameplay balance update.

A few concrete in-game examples help show why that matters:

• If you were banking materials for a future weapon upgrade route, any duplication-driven stockpile is now part of a post-fix economy, not a reliable planning baseline.
• If your squad was comparing fourth Expedition rewards and someone saw Skill Points where Mystery Rewards should have been, the old readout may have pushed the team toward the wrong session goal.
• If you log in after the update and the game still behaves as before, the most likely cause is that the restart step was skipped and the hotfix did not fully apply.

The patch notes are short, but the consequences are not trivial. In a game built around extraction timing, item value, and route discipline, even a two-line fix can influence how players choose to spend a session.

Winners

The biggest winners are players who care about fair progression, clean economy state, and reliable UI reads.

Progression-focused players

Players pursuing fourth Expedition progression are now less likely to misread the reward track. The UI fix matters because Expedition systems are only as usable as their information layer, and a reward mismatch can easily send someone down the wrong optimization path.

A few concrete cases show the impact:

• A player planning their next upgrade around Mystery Rewards can now verify the screen before committing to an extraction run.
• A squad that splits tasks, with one member farming supplies and another mapping the Expedition path, can use the corrected screen to avoid duplicate effort.
• A returning player who only checks progression once per session can trust the display again without second-guessing every reward slot.

This kind of fix is small on paper and large in practice because progression systems are psychological as much as mechanical. If the screen lies, players lose confidence in the route. Once confidence goes, they start overchecking, delaying decisions, or farming the wrong resources.

Legit players in the current meta

Players who are not exploiting the duplication issue benefit indirectly because the hotfix reduces the incentive for inflationary behavior. In extraction shooters, even a temporary duplication bug can distort the practical value of loot, upgrade timing, and risk assessment. Fixing it preserves the integrity of the grind.

That matters in cases like these:

• A solo player deciding whether to cash out early or push deeper into a raid can now evaluate loot value without wondering whether the market is being distorted by duplicated stock.
• A midgame build that depends on hard-earned materials keeps its relevance longer when illicit shortcuts are removed.
• A player who prefers careful scavenging over aggressive farming is less likely to feel punished by someone else’s exploit-driven advantage.

The broader effect is simple: when the economy is cleaner, legitimate play feels more consistent. You can still lose a fight, miss a cache, or extract too late, but you are less likely to be competing against a fake supply curve.

Integrity-minded squads

Coordinated teams that play cleanly should see a healthier matchmaking environment after enforcement messaging. The studio’s statement that significant exploit advantage can still lead to bans is not a balance note, but it is a live-service signal: abuse is being treated as a rules issue, not just a bug report.

A useful way to think about the impact is:

There are also practical squad-level examples:

• A trio that divides roles into scout, carrier, and escort can now route around clean reward expectations instead of planning around an inflated stash.
• A team that uses the Expedition screen as a session checkpoint can trust the progression markers when deciding whether to extract or continue pushing.
• A clan or regular group that values account safety has a clearer signal that exploit behavior is being watched, which changes how risk is priced inside the group.

For organized play, this is the kind of patch that reinforces discipline. It does not make the game easier, but it makes the rules easier to read.

Losers

The obvious losers are players who relied on the duplication issue.

The patch does not state how the exploit worked, so there is no factual basis to describe the method or magnitude. What is clear is that the studio has already tied exploit use to enforcement, so anyone who used the bug to gain a significant advantage is now exposed to account action Source.

There is also a small but real inconvenience cost for everyone:

• You need to restart the game to receive the hotfix Source.
• The patch does not add compensating content, so this is pure maintenance rather than a value-add drop.
• Players who were using the flawed Expedition UI as a decision aid will need to re-check their route assumptions after relogging.

If you were farming around a duplicated-resource loop, that line has effectively closed. If you were not, nothing in the notes suggests your loadouts, weapons, or class decisions were nerfed.

Concrete examples make the loser side clearer:

• A player who stacked resources beyond what normal play would allow may now find that their planning assumptions no longer match a clean progression curve.
• A squad that built its session around exploit-assisted stash growth will need to rebuild expectations around actual raid success instead.
• A player who was using the Expedition UI bug to decide between pushing one more mission or stopping for the night may have been making decisions from bad information.

This is not the kind of loser group created by a combat nerf, where everyone in a weapon class feels it equally. It is narrower than that and more about behavior than loadout choice.

What To Do Today

The right response is to adjust your routine, not your builds.

• Restart the game before your next session so the hotfix actually applies.
• Re-check your Expedition screen after login if you are on the fourth run, because the reward readout issue is the kind of bug that can quietly waste a session.
• Stop any farm route or stash-management loop that depended on item duplication, because that behavior is now directly in the studio’s enforcement crosshairs.
• Treat any reward or progression planning based on pre-hotfix UI as stale until you verify it in-game.
• Keep an eye on related guide coverage for expedition routing and economy efficiency once the post-hotfix meta settles.

For players who optimize around progression cadence, this is less about respeccing a character and more about rerouting attention. Your best play is to restore clean baseline information, then continue with normal extraction discipline.

There are a few sensible session-level adjustments as well:

• If you were about to commit a long run, log in early enough to verify the hotfix applied before you queue with a squad.
• If your team uses a shared loot or crafting plan, have one member confirm the Expedition screen so nobody is building around the old bug.
• If you track resources manually, update your mental baseline after the restart and assume any inflated totals are suspect until you reconcile them.

In short, today is for housekeeping. The game state changed in a narrow but meaningful way, and the safest move is to reset your assumptions before you start chasing goals again.

Why This Matters In The Current Meta

This hotfix matters because ARC Raiders is already operating at live-service scale. The game has 293,879 Steam recommendations and 404,995 total Steam reviews according to the tracked snapshot Source, which means even a narrow exploit fix has broad downstream impact.

The title also has enough completion depth to make progression clarity important. HowLongToBeat currently places the main story at 38.43 hours, 73.74 hours with extras, and 157.95 hours for completion Source. In a game with that much time investment, a UI bug in progression rewards is not cosmetic. It can alter how players route their sessions.

That is why Hotfix 1.36.1 should be read as a trust-preserving patch. It does not reshape combat, but it protects the systems that support long-term play.

There are a few more reasons the current meta makes this kind of patch important:

• Live-service economies react fast to duplication, so a short-lived exploit can echo through normal play for longer than people expect.
• Progression UI errors matter more late in a game’s life cycle, when players are optimizing tightly and every reward tier has a known purpose.
• A patch that combines a fix with enforcement messaging can change behavior even before players feel the technical result.

In practical terms, that means the patch is doing more than patching a bug. It is setting expectations. Players now know that the studio is willing to clean up both information flow and exploit abuse rather than letting either linger.

That has value in a current meta built around repeat sessions, stash decisions, and progression planning. If the system says Mystery Rewards, the game needs to mean Mystery Rewards. If the economy says items are scarce, the game needs to protect that scarcity. Hotfix 1.36.1 is mostly about keeping those promises intact.

Common Mistakes

Players tend to make the same few mistakes after a narrow hotfix like this.

1. Skipping the restart
   Why players fall in: They assume a small patch will apply silently in the background.
   Concrete fix: Fully restart the game before queueing so the hotfix actually loads.

2. Trusting pre-hotfix Expedition reads
   Why players fall in: They saw the reward screen once and assumed it was stable.
   Concrete fix: Re-open the Expedition screen after logging in and confirm the fourth-run reward text before planning the session.

3. Keeping a duplication-based stash plan alive
   Why players fall in: A farm loop that worked yesterday feels safe until it breaks.
   Concrete fix: Stop treating inflated inventories as your baseline and rebuild plans around legitimate drops only.

4. Using the patch as a reason to rush into a long session
   Why players fall in: They want to “test” the update immediately and skip verification.
   Concrete fix: Spend a minute checking that the restart applied and that UI text matches expectations before committing supplies.

5. Assuming all progress systems changed
   Why players fall in: Players often read any hotfix as a stealth balance patch.
   Concrete fix: Stick to the confirmed notes and avoid overcorrecting your build, loadout, or raid route without evidence.

6. Ignoring squad communication
   Why players fall in: One person updates, the others stay on the old assumption set.
   Concrete fix: Have one teammate confirm the patch and the Expedition screen before the squad commits to a shared route.

7. Treating exploit use as harmless if it was “small”
   Why players fall in: People downplay low-level abuse when they think only major offenders get punished.
   Concrete fix: Assume the enforcement warning applies broadly enough that any exploit-driven advantage is a bad trade.

These mistakes are easy to make because the patch is small and the temptation is to move on quickly. The risk is that you keep planning from stale information.

Pro Tips

Tip 1. Verify the restart before you spend a run

When the patch lands, do a quick reboot and check the game’s updated behavior before entering a longer raid chain. This is especially useful if you are about to commit rare materials or a valuable squad loadout.

Trigger: You just installed the hotfix and are considering a serious session.
Setup: Launch once, confirm the game is current, then inspect the Expedition screen before queueing.

Tip 2. Use the corrected Expedition screen as a routing checkpoint

The UI fix is most useful when you make it part of your planning loop. Look at the screen before you decide whether to push for another mission, extract early, or hold resources for the next run.

Trigger: You are on a fourth Expedition or near a progression milestone.
Setup: Check the reward display, then align your objective list with the confirmed readout rather than memory.

Tip 3. Rebuild your economy assumptions after any duplication fix

Once a duplication issue is mitigated, any stash value you were mentally assigning to inflated items needs recalibration. A clean economy makes old shortcuts look more profitable than they really are.

Trigger: You were tracking rare materials, crafting inputs, or stash growth before the hotfix.
Setup: Recount what you actually earned through normal play and discard any exploit-shaped assumptions.

Tip 4. Keep squad roles tied to verified information

In coordinated play, one person should confirm patch behavior while others focus on route prep. That keeps the group from making a shared mistake based on a bugged screen or a stale assumption.

Trigger: Your team is planning a multi-run evening.
Setup: Have one player confirm the hotfix applied and another confirm the Expedition display before loadout lock.

Tip 5. Watch for behavior changes in other players, not just your own menu

An exploit mitigation can change how other players move through the economy even if your own routine is clean. Loot values, supply pressure, and risk tolerance can all shift subtly after a fix.

Trigger: You notice that session pace or trade expectations feel different after the patch.
Setup: Run a few normal raids before making hard judgments about the meta, then adjust only after the post-hotfix pattern is clear.

Tip 6. Treat ban-risk messaging as part of the patch, not a footnote

The enforcement warning changes the way you should read the update. Even if the technical side is quiet, the studio is telling you what behavior it will not tolerate.

Trigger: You are tempted to test whether the old exploit still works.
Setup: Don’t treat that as curiosity; treat it as avoidable account risk and play clean.

Tip 7. Use short sessions to confirm stability before long ones

If you usually play in extended blocks, start with a short verification session after any maintenance update. That reduces the chance of wasting time on a bad assumption or a missed restart.

Trigger: You are about to spend a long evening on progression.
Setup: Do one short log-in, confirm the update behavior, then commit to the full session.

Related Guides

• related guide explaining ARC Raiders progression systems and how to read reward screens after a hotfix.
• related guide covering expedition routing, including when to push deeper and when to extract.
• related guide on loot economy basics for players trying to avoid bad stash assumptions.
• related guide comparing solo and squad strategies in the current ARC Raiders meta.
• related guide focused on account safety, exploit warnings, and behavior that can trigger enforcement.
• related guide for returning players who need a clean post-patch reset on the game’s systems.
• related guide describing common UI mistakes in ARC Raiders and how to verify what the game is actually telling you.
• related guide on efficiency tips for players who care more about progression integrity than speedrunning.

Sources

• Steam Community announcement: Hotfix 1.36.1
• Metacritic: ARC Raiders
• Steambase API snapshot
• HowLongToBeat: ARC Raiders