Five articles on this site already cover ARC Raiders: the 1.45.0 patch itself, the deadline checklist before Frozen Trail, the expansion preview, the weapon-mod ladder, and the machine threat hierarchy. Each describes one patch or one system. None charts the thing that shapes a player’s month — how often Embark ships, what those ships contain, and how far a single patch moves a number.
This guide does that instead. It lines up a selection of the dated patch posts Embark published between 24 February and 27 October 2026 — roughly one per month plus each major update — measures the gaps between them, reads the concurrent-player curve either side of Frozen Trail, and pulls out only the weapon and item changes those posts actually state. Then it converts the pattern into a raid plan that does not need rewriting every three weeks.
What this covers: fourteen dated patch posts, the interval between them, the population curve across 2026, and the specific weapon and item values the patches moved. Why it matters: Embark has now stated its cadence in writing, and the post-Frozen Trail patches have each touched one or two numbers rather than rewriting the meta — so the right response is a loadout built on roles, not on the stat line of the week. Who should care: returning players deciding when to re-learn the game, and anyone whose current kit was assembled around a value that a patch has since moved.
The rhythm, measured
Every dated post below is a page Embark published. Two things have to be said before the table is read. First, this is a selection, not the archive: the official news feed carries far more dated posts than the fourteen here, and the table keeps roughly one a month plus each major update, so the intervals measure the rows below rather than Embark’s release history. Second, the labels are not a content guarantee.
| Date | Post | Days since previous row | What the post carried |
|---|---|---|---|
| 24 Feb 2026 | 1.17.0 “Shrouded Sky” | — | Hurricane map condition, two new ARC types, five-weapon balancing pass |
| 5 May 2026 | 1.27.0 | 70 | Fixes after Riven Tides; the balance follow-up is promised, not shipped |
| 19 May 2026 | 1.29.0 | 14 | Bettina fire rate, weapon durability re-tune, weapon-mod values |
| 16 Jun 2026 | 1.33.0 | 28 | Nomadic Envoys arrival, Forgotten Relics event, Converging Paths project |
| 7 Jul 2026 | 1.36.0 | 21 | New Expedition and Trials season, matchmaking tweaks, a THE FINALS crossover outfit |
| 28 Jul 2026 | 1.39.0 | 21 | Test that removes defensive PvP from matchmaking weighting |
| 18 Aug 2026 | 1.42.0 | 21 | Regional map condition schedules, Phantom Targets event |
| 8 Sep 2026 | 1.45.0 | 21 | Expedition 5, Cred sunset scheduled, engine move to Unreal 5.7 |
| 22 Sep 2026 | 1.47.0 | 14 | Riposta variants, a Fair Play update, fixes |
| 29 Sep 2026 | 1.48.0 | 7 | Two colour variants for the Misthorn Set; no update the following Tuesday |
| 8 Oct 2026 | 2.0 “Frozen Trail” | 9 | Expansion: new map, new enemies, two new weapons, skill tree revamp |
| 13 Oct 2026 | 2.1.0 | 5 | PvE toggle beta opens; Carrion Set; long fix list |
| 20 Oct 2026 | 2.2.0 | 7 | PvE beta closes; Hydra damage raised; Frigatefrigate. A player-built warship used to protect naval trade routes from pirates. and Emperor fixes |
| 27 Oct 2026 | 2.3.0 | 7 | Noxious Set, Souls Offering project, Heavy Shield and Flame Spray buffs |
Four consecutive gaps between June and September are exactly 21 days, and every dated post in the table except the Frozen Trail expansion landed on a Tuesday, from 24 February to 27 October. Hotfixes are the exception that proves the rule: 1.46.1 went out on a Wednesday, 2.0.2 and 2.1.1 on Fridays, because a hotfix is not a scheduled post.
Then September and October compress the whole thing. The last week of September shipped a store update on the 29th, the expansion on a Thursday — Embark’s own 1.48.0 post says “no update next Tuesday as we make way for Frozen Trail, arriving Thursday, October 8th” — and then three Tuesday posts in a row on 13, 20 and 27 October. Frozen Trail was followed by two Friday hotfixes and a weekly rhythm while the new map bedded in.
Embark ended that burst in the 2.3.0 notes: “Since Frozen Trail has released, we have been including fixes in our weekly updates. After today we will go back to the regular schedule of fixes every three weeks and store updates on a weekly basis.”
So the operating rhythm from 27 October is two separate clocks. A shop-and-cosmetics pass weekly, a fixes-and-balance pass every third week. The four 21-day gaps from June to September are the same clock running before the expansion interrupted it.
What the compression did to the population
The numbers below are a selection of months from steamcharts.com; each month from February to September 2026 averaged lower than the one before it.
| Month | Average concurrent | Peak concurrent |
|---|---|---|
| November 2025 | 264,429 | 459,483 |
| January 2026 | 241,196 | 465,097 |
| March 2026 | 112,312 | 250,148 |
| May 2026 | 61,053 | 120,450 |
| June 2026 | 35,914 | 68,130 |
| July 2026 | 28,661 | 50,024 |
| August 2026 | 23,216 | 41,319 |
| September 2026 | 21,256 | 39,900 |
| Last 30 days (read for this piece) | 67,882 | 185,443 |
The all-time peak of 465,097 sits in January 2026, and the monthly average declines every month after that, bottoming at 21,256 in September — the last full month before the expansion. Then the last 30 days, which is the Frozen Trail launch window, average 67,882 with a peak of 185,443. steamcharts puts the period-over-period gain at +219.35%.
What that does not prove is causation. A free-play window ran 8–12 October, and a launch always pulls lapsed players; one storefront is also not the whole population, since the game ships on Steam, the Epic Games Store, PlayStation 5 and Xbox Series X|S. But the direction lines up with the only month in the second half of 2026 that carried a full expansion plus a free window. The honest reading: the expansion changed the slope, and the cadence decides how long the new slope holds.
Which weapons the patches actually moved
This is the part where the site’s other coverage matters. The February balancing pass is documented weapon by weapon, with the exact values, in our weapon-modding and loadout tier list — that article owns those numbers and this one will not repeat them. What matters here is its shape: 1.17.0 changed five weapons at once, with a stated intent to stop low-tier guns outperforming high-tier ones at a fraction of the cost.
Nothing since has looked like that. The table below collects the weapon and combat-item changes the dated notes spell out from May onwards:
| Patch | Date | Stated change | Reasoning given in the notes |
|---|---|---|---|
| 1.29.0 | 19 May | Bettina base fire rate 235 → 250; Extended Barrel bullet velocity 25% → 30% and damage falloff distance +15%; durability raised on the weapons that “break too quickly” | The previous patch’s durability changes “were felt too much on some weapons” |
| 2.0 | 8 Oct | Explosive damage formula reworked: weapons like the Hullcracker deal over 50% more against armour plates, around 30% less against fragile parts; Anvil moved Green → Blue rarity; Jupiter no longer propagates damage twice to ARC parts behind its target | Explosive damage should be consistent and better against heavy armour |
| 2.1.0 | 13 Oct | Semi-Auto Amplification for the Hairpin now correctly deals reduced headshot damage; stamina consumables blocked during the Sprinting on Fumes cooldown | Stopping items from bypassing the skill’s intended penalty |
| 2.2.0 | 20 Oct | Hydra base damage increased; ARC aim corrected against sliding players | Compensating for corrected Hydra targeting so “its overall threat level remains competitive” |
| 2.3.0 | 27 Oct | Heavy Shield base charge 80 → 90; Flame Spray damage 10/s → 13/s with durability drain cut 50%; Firefly Burner now ignites on impact and leaves a fire trail | 2.0’s Heavy Shield experiment “showed marked changes” but usage is still low; “another little bump” |
The pattern is small, explained, and reversible. Since Frozen Trail, each patch has moved one or two values, published the reasoning, and said it will keep watching. The Anvil change is the biggest structural edit in the set and it is not a damage number at all: the gun moved up a rarity tier, the Anvil Splitter stopped being a usable mod and became an upgrade path for the Amplified version, and the Tech Mod slot came off the weapon entirely.
Two practical conclusions follow. A loadout anchored to one item’s stat line is now the fragile kind, because a single Tuesday can move it. A loadout anchored to jobs — one answer for armour, one answer for weak points, one answer for getting out — keeps working when a number moves, because the number was never the point.
The raid plan that survives a mid-season shift
The 2.0 explosive rework is the clearest worked example of what a shift does. Your Hullcracker did not get better or worse in the abstract. It got better into plate and worse into fragile parts. The plan that breaks is “bring explosives for the weak point”. The plan that survives is “bring explosives for the plate, and something else for the yellow”. That distinction is the whole discipline of playing a live game on a patch clock.
Do not build on a slot that can be deleted. The Anvil losing its Tech Mod slot is the template. Any recommendation that depends on a specific attachment point existing on a specific weapon has an expiry date nobody announced.
Treat attachment values as patch-movable. The Extended Barrel’s velocity and falloff numbers changed in 1.29.0, in the middle of a durability re-tune that itself walked back the previous patch. If a build write-up quotes a mod’s percentage, check when it was written.
Matchmaking is part of the plan now. 1.39.0 began testing a change where only the fights you choose to start affect your playstyle estimate, and defending yourself does not count at all — including knocking out players who attacked you first. Third-partying a fight already in progress does count as starting it. Aggression stopped being free, and a squad that habitually jumps other people’s fights is now asking for different lobbies.
Map conditions are scheduled, not random. 1.42.0 moved map conditions from one global schedule to regionally offset schedules matched to local peak hours. If you plan a session around a specific condition, the schedule is a resource; Embark publishes it at arcraiders.com/map-conditions.
Loot routes are deliberately less predictable. Since 2.0, Pendola Pass runs a Dynamic Loot Zone system where an area’s value varies raid to raid while its loot type stays fixed. 2.3.0 pushed the same idea into the Emperor and the Frigate, moving higher-tier rewards deeper inside and lowering what sits near the entrance. A route that was optimal last month may still be a route, with worse contents.
The PvE toggle is a test result, not a mode. It ran 13–20 October with zero player-to-player damage, lowered overall loot value on PvE servers, and several major map conditions excluded from the option entirely — Night Raid, Locked Gate, Hidden Bunker, Frigate and Redirection. Embark’s own wrap-up post says the test was “polarizing” and that a decision will follow “in November”, with no date attached.
What is actually dated, and what is not
Two published dates matter for planning. Trials Season 6 runs from 8 October 2026 to 12 January 2027, with the Maestro Outfit as the season grand prize — that is the horizon a returning player can build against. And the PvE follow-up is promised for November 2026 with no day attached.
Everything after that is undated. Embark has not published a post-Frozen Trail roadmap with dates, and the 2.3.0 post does not name a date for the next fix bundle. The three-week clock, counted from 27 October, would put the next fixes pass around 17 November — that is arithmetic on a stated cadence, not an announcement, and it should be read as such.
One clarification on vocabulary, since the archive uses both words. A “store update” is the Tuesday shop pass; a “live update” is the fixes-and-balance pass. The two are not reliably different in size: 1.48.0 was literally two colour variants, while 2.2.0 carried a page of gameplay and stability fixes under the store-update label. “No update next Tuesday” in the 1.48.0 post therefore meant no scheduled post at all, not a quiet week for the game.
Where the earlier coverage now sits
The August preview on this site described the October update as a photo mode, a frozen map and an undisclosed high-level challenge, and said Embark had not publicly detailed countermeasures for cheating. Both halves of that have moved. Frozen Trail shipped with a new map in Pendola Pass, new map conditions, three new enemies, two new weapons, a revamped skill tree, the Outpost and Research Bench, 22 new quests and a new Reward Pass — see that preview for how far ahead of ship the details were signalled. On cheating, Embark had already folded a “Fair Play” update into the 1.42.0 and 1.47.0 notes, then published a direct statement on 30 September 2026 naming kernel-level protection from Denuvo, detections from Anybrain, in-house machine-learning models, and Elytra being tested at small scale in THE FINALS with the aim of testing it in ARC Raiders later. That is not a claim that cheating is solved; it is the end of “no public position”, which is what the older piece was reporting.
The pre-expansion checklist is now history: Cred expired on 8 October, and the new Souls Offering player project has replaced Ascending the Mountain. Our 1.45.0 countdown piece records how far ahead Embark telegraphs a currency sunset — announced 8 September for a cut-off a month later. That is the one part of the cadence that has stayed consistent: economy changes are signalled early, combat values are not.