Current player briefing
Star Citizen Loop Health — What’s Playable Right Now?
The short answer: cargo hauling and mining remain possible in Alpha 4.9.x LIVE, but the current evidence supports a Degraded call for both—not a clean bill of health. Salvage remains Unknown: BustedLoops does not yet have enough fresh published evidence to recommend it or warn players away.
Applicable LIVE: Alpha 4.9.x LIVE · Assessment updated: · Underlying Workarounds researched 15–20 August 2026
The quick read
Cargo & hauling
Degraded
A supported manual-transfer path exists, but ship choice and transfer method matter.
Mining
Degraded
Known fitting, refining, and sale failures require bounded workarounds.
Salvage
Unknown
Not enough fresh published evidence for a responsible verdict.
Interdiction
Unknown
Two narrow equipment workarounds do not establish the health of the full loop.
Cargo & hauling
Degraded
Cargo earns Degraded because current evidence shows a workable Hull C manual-transfer path alongside several meaningful failure points. Current reports support moving Hull C cargo manually through working external freight elevators when the cargo exists and both endpoints have usable elevators. This bypasses automated transfer; it does not repair Cargo Services. Stop cycling failed requests, and do not risk damaging the lower spindle.
Mission hauling is less dependable. When contract cargo is absent from the pickup elevator, close the game and launcher, synchronize the PC clock, then make one bounded retry. Results are mixed, so stop if the pickup remains empty. Repeated abandon–reaccept–relog cycles are not dependable, while station-to-station routes and commodity hauling remain unverified fallbacks.
Ship to avoid for valuable cargo: Ironclad
If the session depends on retaining valuable cargo, avoid the Ironclad for now. Its cargo body can become inaccessible after quantum travel, and its body or cargo state can also be missing after retrieval. Neither case has a reliable recovery. Before claiming, returning to the original shard is a cautious final check; Alt-F4 is not dependable recovery.
If you use a Hull-A, fully retract its cargo spindles before storage. This is preventive guidance, not evidence that every other Hull-A state is reliable. Once the ship returns partially extended and unresponsive, the corpus has no supported recovery.
Mining
Degraded
Mining is Degraded because fitting, refinery intake, and selling all have current failure points, even though each still has a bounded action worth trying. It does not establish universal reliability across mining ships, locations, or terminals.
Avoid basing a mining session on the Golem when module fitting is essential. Its mining modules can be missing or refuse attachment, and repeated normal fitting attempts are not useful. A pre-prepared spare Pitman head is worth one cautious test, not treatment as a dependable fix. Switching to another mining ship avoids the affected fitting path, but the corpus does not identify a universally safe substitute.
For the stored-ship work-order failure, move the ore pods to local inventory before starting the refinery order. This is current official guidance, without an independently established success rate. For hand-mined gems, sell a small test from personal inventory with your character selected, confirm payment, then move the rest. This limits exposure; it does not guarantee the terminal will accept the full haul. If the low-risk tests fail, retain the gems.
Salvage
Unknown
BustedLoops does not currently have enough fresh, published Salvage evidence to call the loop Playable, Degraded, or Broken. That means no responsible recommendation either way—not that scraping, fracturing, cargo handling, contracts, or sale are healthy or unhealthy.
Interdiction
Unknown
The corpus offers actions to try for two specific equipment states, but not enough evidence to grade piracy or interdiction as a whole. If an equipped quantum snare or dampener disappears from its console after travel, make another quantum jump and check again. If a docked Drake Command Module radar stops functioning, undock and redock the module. These are narrow component-state workarounds, not evidence that targets, missions, payouts, or interdiction ships are broadly reliable.
Cross-loop traps worth planning around
- Do not make an unverified rental the keystone of your session. A completed rental can remain missing from ASOP, and the current router/DNS fallback has mixed outcomes. Re-renting, server hopping, character repair, or buying another vehicle are not supported fixes.
- If your Aurora Mk I is already affected, treat it as unavailable. If it cannot be retrieved after Alpha 4.9, try one alternate-location or stock-layout claim only if its warning is acceptable; do not keep cycling the same terminal.
- Give Landing Services time to wake up. When repair, refuel, and restock do not appear after landing, wait several minutes and reopen mobiGlas. This is official guidance, not an independently confirmed repair. It only covers missing app options, not a failed service transaction.
- Recognize the limiter-specific thrust failure. If the velocity limiter prevents sustained forward thrust, release and press forward thrust again. That does not cover damage, power loss, or other flight-control failures.
What Unknown means here
This briefing grades only the loops the current published Workaround corpus can say something useful about. It makes no current loop-health claim for bounty hunting, general combat, delivery, racing, medical play, exploration, or other activities. Alpha 4.9.x LIVE defines the evidence scope; it does not guarantee identical behavior across every server, location, mission, ship, or hotfix.
Use the linked Workaround pages for the incident boundaries, evidence, and exact actions behind each call.