Dropship Quest Salvage and Close localization · Week 250–251 current-player evidence boundary

ICARUS Dropship Quest Salvage Close Localization Fix

Quick Answer

ICARUS Dropship Quest Salvage Close localization. If Salvage or Close on the Dropship Quest UI is not localized, match the client and host to Week 251 build 3.0.29.157838 or later and confirm the current game language. RocketWerkz records a fix specifically for those two labels. Open the exact Dropship Quest interface once and compare the labels with the selected language. The update does not list affected languages, change the salvage result, alter quest rewards, or provide a manual localization-file repair. Keep a wrong label separate from a button that is disabled or a quest that cannot progress.

Reading time
7 minutes
Difficulty
Language, screen and build-state diagnosis
Checked
2026-10-08
On this page

Guide details

Before you begin

Use the Week 251 boundary when the Dropship Quest UI shows Salvage or Close text in the wrong language or as an untranslated token.

Week 251 Dropship Quest Salvage/Close localization fix; no invented language list, reward, quest-state, cache, file-edit or reset claims.

Status
Official Week 251 evidence plus bounded exact-query review
Edition
Week 250–251 current-player evidence boundary
Platform
PC · Steam
Checked
2026-10-08
Check note
Only the cited Week 251 facts are verified. Volume, KD, external SEO score, undocumented reset procedures, numeric mechanics and later changes remain Unknown.

Before you set out

Prerequisites#

  • Confirm that both the player client and the session host run ICARUS Week 251 build 3.0.29.157838 or later.
  • Confirm the exact affected object or interface: the Salvage and Close labels on the Dropship Quest interface.
  • Record the visible state before interacting so a display defect is not confused with a separate gameplay failure.
  • Keep affected language list, fallback order, string identifiers, salvage results, quest rewards, button logic and cache refresh Unknown unless another current reliable source verifies them.

Why Salvage and Close could remain untranslated#

The Week 251 fixed list names a missing localization problem on the Dropship Quest UI. The affected strings are Salvage and Close. Localization determines which translated text the interface displays; it does not by itself determine whether a button is enabled, what salvage returns, or whether the quest state is valid. A label can remain wrong because the client is older, the selected language lacks the corrected string, cached interface state predates the update, or the player is viewing another screen. Record the selected language and exact visible text before opening the same interface once on the corrected build. Do not edit localization files, abandon the quest or salvage items merely to test wording.

How to preserve evidence for Dropship Quest Salvage and Close localization#

Keep the original state observable until the comparison is complete. Write down the exact client build, host build, object or interface label, selected variant, visible text or geometry, and the single normal action performed. A screenshot can preserve presentation, but the in-game label and build are more reliable than a guessed internal cause. Do not combine a version update, object replacement, language change, reconnect and file edit in one test because the result would not identify which condition mattered. If the corrected build still shows the symptom, record whether the state existed before the update and whether another player on the same host sees the same thing. This evidence is suitable for a support report without claiming an undocumented workaround.

Route 03

Check ICARUS Dropship Quest Salvage Close localization#

Use this order to test the documented Week 251 boundary without inventing a destructive reset or unsupported mechanic.

  1. Identify the exact subject#

    Use the current in-game label and visible model or interface to confirm the Salvage and Close labels on the Dropship Quest interface. A similar object or screen is outside this exact evidence.

  2. Check the client build#

    Confirm Week 251 build 3.0.29.157838 or later. An older client is below the documented correction.

  3. Check the host build#

    Match the host or dedicated server to the corrected build. A current joining client alone does not prove shared state uses the fixed path.

  4. Record the pre-action state#

    Capture the selected language, exact visible Salvage and Close text, quest screen identity and whether each button is enabled. Preserve labels and visible geometry rather than relying on memory.

  5. Use one normal interaction#

    Perform the ordinary action once: open the exact Dropship Quest interface once and observe the two labels without committing a salvage action. Do not reload, dismantle, replace, or edit files merely to force a different result.

  6. Compare the corrected behavior#

    On the corrected build, Salvage and Close should use the available localization for the selected language rather than remaining an untranslated fallback.

  7. Separate adjacent symptoms#

    A different failure may look related. Keep button enablement, salvage rewards, quest progression, inventory transfer and dropship travel as separate issues unless current evidence connects them.

  8. Note the pre-patch boundary#

    Record whether the object, world, or interface state existed before the update. The changelog does not guarantee that every stored or placed state reconstructs immediately.

  9. Preserve a remaining failure#

    Keep client and host builds, host type, selected language, exact strings, quest UI identity, button state, client build and host build, and the exact outcome before broader changes.

Pocket list 04

Verified Dropship Quest Salvage and Close localization boundaries#

  • Affected subject — the Salvage and Close labels on the Dropship Quest interface.
  • Documented symptom — Salvage and Close were not localized on the Dropship Quest UI.
  • Documented correction — Week 251 fixes missing localization for the Salvage and Close text on the Dropship Quest UI..
  • Fix boundary — Week 251 build 3.0.29.157838-rel-DangerousHorizons.
  • Unknown — affected language list, fallback order, string identifiers, salvage results, quest rewards, button logic and cache refresh.
  • Unknown — manual reset, console command, save edit, or guaranteed migration of an older state.
  • Search volume, keyword difficulty, and external SEO score remain Unknown.

Fault ledger

If the Dropship Quest labels are still untranslated still appears#

The host is older than Week 251
Update and restart the host before judging the correction. The authoritative shared path may remain on the older build.
The subject does not match the changelog
Stop applying this diagnosis and record the actual object, tier, material, screen or button. Week 251 names the Salvage and Close labels on the Dropship Quest interface.
Only an adjacent mechanic fails
Keep button enablement, salvage rewards, quest progression, inventory transfer and dropship travel separate. The cited line does not verify those systems.
The state predates Week 251
Preserve that boundary. A code correction is not proof that every old placed object or stored interface state migrates automatically.
A workaround requires destructive changes
Do not present dismantling, deletion, console commands or save editing as official. Capture evidence and use normal support channels.

Field questions

Dropship Quest Salvage and Close localization questions#

What exactly did Week 251 fix?
Week 251 fixes missing localization for the Salvage and Close text on the Dropship Quest UI.
Which build is the verified boundary?
Week 251 build 3.0.29.157838-rel-DangerousHorizons.
Does this prove every related mechanic changed?
No. button enablement, salvage rewards, quest progression, inventory transfer and dropship travel remain separate unless a source explicitly connects them.
Will updating repair every object or state created earlier?
The changelog records the fixed behavior but does not guarantee migration or reconstruction of every pre-patch state.
Should I edit files or use console commands?
No official procedure of that kind is supplied by the cited release. Preserve the state and avoid destructive guesses.

Back to the game

Browse all ICARUS guides

Sources

What this guide was checked against