Star Citizen Alpha 4.8.1 dropped on June 5, 2026 as a live hotfix, and it brings two changes that will affect almost every player currently in the game. The first rewrites how you send aUEC to other players. The second takes a swing at the long list of bugs plaguing the Ironclad and Ironclad Assault. Neither story is clean cut.

Star Citizen Alpha 4.8.1: Complete Hotfix Reference

The launch of Alpha 4.8.1 on June 5, 2026, delivers critical gameplay guardrails designed to crack down on aUEC exploiters while stabilizing complex multi-grid ships like the Drake Ironclad. While there is no Long-Term Persistence database wipe with this hotfix, your client and RSI launcher must be updated before you can access the game.

Star Citizen Alpha 4.8.1 Mobile Feature Matrix

System/ShipUpdate StatusNew Mechanical ParametersCore Tactical & Sandbox Impact

aUEC Wallet

(Economy Refactor)

Rebuilt Implements the Player Trade Notification Refactor with Economy Authorization Service. Mutual Consent: Both players must be online. The recipient has a finite window to accept/decline the transaction via screen alert. Transaction CapsHard-Capped Single transfers max out at ~999,999 aUEC (including fees). Daily combined outbound cap sits at 20M aUEC. Exploit Mitigation: Limits transaction rates to break duplication loops and RMT currency farming businesses. Hangar InsuranceNew Protection Destroys caused by environmental hangar floor clipping glitches (getting “purpled”) trigger a free insurance claim. Glitch Insurance: Bypasses standard reclaim financial penalties. Note: Self-destructing your vehicle voids the free claim. Friend List UIAdjusted Right-clicking a contact in your join options now forces a static “0 out of 1” population readout. Anti-Server Hopping: Hides actual shard metrics to curb aggressive server-hopping. Shard limits must be checked via the in-game overlay.

If you have been sending money to org mates, splitting mission payouts with a crew, or funding a new player’s first ship purchase, the system you were used to is gone. The new one has hard caps, requires the other person to be online, and gives them the option to reject your transfer entirely. And if you own an Ironclad and were hoping 4.8.1 finally made it reliable for multi-jump runs, testing shows that some fixes landed, but the wormhole problem is still there.

Here is what changed, what got tested, and what you actually need to know before logging in.

No Reset, But You Still Need to Update Your Launcher

4.8.1 does not trigger a Long-Term Persistence reset, so you keep your home location and your current aUEC balance. You do need to update your launcher before the game will load. Once you are in, the changes hit immediately.

The Player Trade System Got a Full Rebuild

The old mobiGlas wallet let you send aUEC to any player, at any amount, across any shard, whether they were online or not. There were no limits on frequency and no confirmation step on the receiving end. That system is what allowed players to move billions of aUEC between accounts in previous patches without any friction.

4.8.1 replaces it with something CIG is calling the Player Trade Notification Refactor with Economy Authorization Service.

How Sending Money Works Now

  • You initiate a transfer through your mobiGlas wallet

  • The receiving player gets a notification alert on their screen asking them to accept or decline

  • You see a pending status while you wait

  • If they do not respond in time, the transaction cancels and nothing moves

  • The receiving player must be online for any transfer to go through, even cross-shard

  • The system now enforces per-transaction caps and rate limits

What the Actual Cap Is

Live testing confirms the cap sits at roughly 999,999 aUEC as the maximum total cost per transaction, including any transaction fee. Attempting to send exactly 1,000,000 aUEC returns a “Transaction not permitted at this time” error because the fee pushes the total above the seven-digit ceiling. Sending 995,023 aUEC (the amount where total cost stays under 1,000,000 after fees) goes through fine.

The daily total cap is reported by multiple players as 20 million aUEC per day across all outbound transfers combined, though CIG has not published an official number in the patch notes at time of writing. Per-transaction frequency testing showed 20+ consecutive transfers going through without a rate limit block, so the frequency cap is not aggressively low.

Cross-shard transfers still work, but again, the receiver must be online and must actively accept.

Why CIG Did This

This is a direct response to aUEC economy exploitation. Prior to the Alpha 4.8 wipe, players were distributing hundreds of billions of aUEC between accounts using duplication bugs and bulk transfers, with no consent mechanism and no limits. The new system closes the most accessible routes for that by requiring mutual consent, capping single transfer values, and limiting daily outbound totals.

For normal players splitting mission payouts or helping a friend get started, the system still works fine. You just both need to be in the game at the same time.

Hangar Collision Insurance: What It Does and Does Not Cover

4.8.1 adds a free insurance claim for ships destroyed by collisions inside a hangar. The intent is to protect players from the specific bug where a ship clips through or gets stuck in the hangar floor, often called being “purpled,” which previously burned through your ship’s insurance timer and cost you money.

Testing shows that self-destructing your ship inside your hangar does not qualify for the free claim. The ship reclaims normally and deducts the standard cost. The free claim appears to only trigger in specific hangar collision scenarios, likely those caused by environmental glitches rather than voluntary actions.

Since the “purpled ship” bug happens randomly and cannot be reliably triggered on demand, full confirmation of the free claim working in that specific scenario is still pending from the community.

Ironclad and Ironclad Assault: Three Fixes, One Big Problem Remaining

The Ironclad has been one of the most discussed ships since its Alpha 4.8 release. It is a large modular cargo hauler that uses a detachable Command Module for flight control, and that architecture has created a cascade of bugs since day one. 4.8.1 addresses three of them officially.

What the Patch Notes Say Is Fixed

Route resetting between SCM and Nav modes. Previously, switching flight modes on any ship with a Command Module (Ironclad, Ironclad Assault, Caterpillar) would wipe your active route and force you to re-plot. That is fixed.

Mid-flight stops and Command Module self-undocking. Ships would randomly stop during flight or quantum travel, and in some cases the Command Module would undock itself without any player input. This was one of the most reported Ironclad issues. The patch claims a fix for both.

Quantum travel marker behavior. Markers did not display correctly when a route was set on an Ironclad or Caterpillar that spawned with the Command Module already attached. Fixed.

What Is Still Broken After 4.8.1

Wormhole jump after the first one. Testing shows the Ironclad can make one wormhole jump successfully, including Stanton to Pyro. The second wormhole jump does not work. After jumping once, quantum markers disappear and the jump gate either does not activate or pushes the ship away. Detaching the Command Module, activating the gate manually, and reattaching does not reliably work due to gate timing. No confirmed workaround for multi-jump runs exists yet.

Camera locked to Command Module. The third-person camera centers on the Command Module rather than the full ship after spawning. Undocking and re-docking the Command Module fixes it for that session.

Quantum marker disappearance mid-flight. If markers vanish during a run, the current workaround is to detach the Command Module and reattach it. This restores markers in most cases.

Ship power initialization bug. The Ironclad sometimes spawns in a state where it cannot be flown until you power the ship fully off, then back on, then manually toggle the engines.

Pressure and temperature anomalies. Certain interior areas of the ship show dangerously high pressure or low temperature readings. These appear to be localized to specific zones rather than the full interior, and the issue is not fully resolved.

Notification stack bug. The “Dock with Refueler” and similar notification prompts stack on screen and do not dismiss. The current fix is to go to Options, set Show Hints to Yes, then set it back to No, and exit.

Server Population Display Change

After the latest server maintenance, right-clicking a friend in the join list now shows “0 out of 1” regardless of actual server population. This appears to be intentional. CIG seems to have hidden the population count from the friend list view to reduce the practice of adding players purely for server-hopping to find a high-population shard. To check actual server population after joining, open the Display Info overlay.