Patch 1.23.23.0 Delayed: New Release Time

Arc Raiders’ usual Tuesday update cadence hit an unexpected snag this week. Embark’s community messaging confirms that patch 1.23.23.0 has been moved to tomorrow at the usual release time: 10:00 a.m. UK.

Delays like this typically point to last-minute build issues, certification timing, or a fix that didn’t pass internal checks. The studio hasn’t shared the specific reason, but the key takeaway for raiders is simple: plan your runs and crafting around tomorrow’s deployment window rather than today’s.

What’s Confirmed: The Vanguard Set Is Included

The one concrete piece of content confirmed for the patch is the Vanguard set. After being mentioned on April 1, some players assumed it might be a joke or a tease. With the delay announcement, it’s now clear the set is real and scheduled to arrive with tomorrow’s update.

From what’s been shown so far, the Vanguard look leans into a heavier, more imposing silhouette with a distinctive mask/visor profile. If you’ve been waiting for a more “armored” aesthetic compared to lighter scavenger styles, this is shaping up to be one of the more eye-catching rotations.

Will it be a full rotation or a single featured set?

While the messaging highlights Vanguard specifically, skin resets and rotations are usually bundled into these update windows. Expect the broader cosmetic lineup to refresh alongside Vanguard unless the delay forces a narrower rollout.

Patch Notes Are Not Out Yet (And Why That Matters)

One of the more unusual parts of this update cycle is that patch notes were not shared ahead of time. According to the studio response, details are expected with the update tomorrow.

That means players can’t pre-plan around balance tweaks, bug fixes, or economy changes today. If you’re optimizing your time, treat tonight as a “maintenance eve” and avoid making decisions that rely on unknown patch behavior—especially anything involving weapon handling quirks, consumable timing, or inventory management.

Community Bug Watch: Shoulder-Swap and Long-Standing Issues

A recurring community concern is the persistence of long-standing bugs—particularly issues like swapping shoulders behaving incorrectly (or inconsistently) along with other quality-of-life problems that have been present since launch.

Embark has indicated a fix is coming, but did not confirm whether it’s part of tomorrow’s patch. If you’re affected by shoulder/aim inconsistencies, the practical approach is to keep your sensitivity and positioning habits conservative until the fix is confirmed live.

• Choose consistent engagement angles so you aren’t forced into rapid shoulder swaps mid-fight.
• Hold wider cover margins to reduce “micro-peek” situations where shoulder behavior matters most.
• Test after patch in low-risk encounters before committing to high-value runs.

Possible Leak or Visual Bug: Pharaoh 5 Upgrade Appearing

Players have reported a strange upgrade screen moment showing an option to upgrade Pharaoh 4 into Pharaoh 5. As presented, it appears to be a glitch or a UI/state mismatch—because it surfaces where it logically shouldn’t.

Still, it’s notable for two reasons:

• If it’s purely a bug, it may indicate an incomplete or hidden upgrade tier that’s being surfaced accidentally by the client.
• If it’s future content, it could hint at an eventual expansion of weapon bonus tiers or progression depth.

No official confirmation has been shared publicly, so treat it as an interesting anomaly rather than a guaranteed roadmap reveal. If you see it yourself, document the conditions (what you clicked, what you had equipped, and whether it persisted after relogging), because reproducible steps are what typically turn “weird sightings” into actionable fixes.

Inventory Pressure: Why Players Want Stackable Components

Inventory and stash constraints are becoming a bigger friction point as new crafting materials and components enter the game. Two items called out by the community are the assessor matrix and vaporizer regulators, which many feel should be stackable to reduce stash bloat.

This kind of pressure tends to compound over time: every new weapon, crafting ingredient, and event drop competes for the same limited storage footprint. When components don’t stack (or stack too low), players end up spending more time sorting than raiding.

Practical stash management until changes happen

• Consolidate by purpose: keep one “crafting now” tab and one “crafting later” tab so you can purge with less hesitation.
• Set a hard cap per component: decide a maximum you’ll keep (for example, enough for your next 1–2 crafts) and recycle/sell the rest.
• Prioritize high-turnover items: if a component isn’t used in your current build path, it shouldn’t dominate your storage.

Reload Glitch: The Most Disruptive Combat Issue Right Now

Multiple reports continue to highlight a reload-related firing glitch—most commonly described as weapons continuing to fire or firing unexpectedly when the trigger is pulled during reload timing. It’s disruptive for obvious reasons: it can waste ammo, break stealth, and even cause accidental friendly fire incidents during chaotic events.

Until a patch explicitly confirms the fix, the most reliable mitigation is behavioral: do not pull the trigger while reloading. Because the issue is timing-sensitive, even small habits—like “pre-firing” as the reload finishes—can increase the chance of triggering the bug.

Why this bug is so costly

• Event pressure: in Harvester-style moments, stray shots can pull additional threats or ruin coordination.
• Ammo economy: unexpected bursts burn resources you intended to save for the next engagement.
• Trust and teamplay: accidental hits create confusion even when everyone knows it’s a glitch.

If tomorrow’s patch includes “a number of fixes,” this is one of the issues many players will check first.

Healing Item Delay Reports: What to Look For

Another community report worth tracking is a possible delay when using healing items (such as stims), where the input seems to require multiple presses before activating. Not everyone is experiencing it, which can suggest one of the following:

• Intermittent input registration tied to specific states (sprinting, swapping weapons, animation locks).
• Latency/desync edge cases where the client shows selection but the server rejects the use.
• Contextual conflicts such as attempting to heal during another action that silently overrides it.

How to self-diagnose quickly

• Recreate in a safe area: try healing after sprinting, after climbing, after swapping weapons, and right after reloading.
• Watch for consistent triggers: if it only happens during one transition, you’ve found a state bug.
• Adjust timing: a short pause before using the stim may reduce failures if the issue is animation locking.

If you’re affected, it’s worth treating heals as something you “buffer” earlier than usual—don’t wait until the last sliver of HP if your item use is unreliable.

What to Expect Tomorrow

With the patch moved to tomorrow at 10:00 a.m. UK time, the most realistic expectations are:

• Vanguard set goes live as a featured cosmetic addition.
• Patch notes arrive with deployment, not ahead of time.
• At least a handful of fixes ship, though which ones are included remains unknown.

Once the update is live, prioritize quick verification tests: reload behavior, healing item responsiveness, and any previously inconsistent shoulder/aim interactions. Those three checks will tell most players, within minutes, whether the patch meaningfully improves moment-to-moment gameplay.

Why was the Arc Raiders patch delayed this week?

The studio confirmed the delay but didn’t share a specific cause. Typically, it’s due to last-minute build issues or fixes needing more validation.

Is the Vanguard set actually coming, or was it a tease?

It’s confirmed for tomorrow’s patch window. Earlier timing made some players skeptical, but the latest announcement clarifies it’s part of the update.

Are patch notes available before the update?

No. The current plan is to publish patch notes alongside the update when it goes live.

How do I avoid the reload firing glitch?

The best workaround is to avoid pulling the trigger during reload sequences. The bug appears to be tied to reload timing and input overlap.

It appears to be a glitch or unintended UI exposure. There’s no official confirmation that a new upgrade tier is actually releasing.