RAD_O3 prospector-head delivery · Week 250–251 current-player evidence boundary
ICARUS RAD_O3 Prospector Heads Not Delivering
Quick Answer
If ICARUS RAD_O3 will not accept the prospectors’ heads required by the current objective, confirm that both the client and host run Week 250 build 3.0.28.157342 or later. RocketWerkz documented a RAD_O3 issue where the prospectors’ heads could not be delivered as intended and records the fix in Week 250. On the corrected build, verify the exact RAD_O3 tracker step, confirm that the named quest items are present through the normal inventory and objective interfaces, then attempt the visible delivery interaction once and watch for the tracker to advance. The release note does not publish how many heads are required, where they are acquired, which person, device, container, or location receives them, or what prompt should appear. It also supplies no relog, drop-and-pick-up, mission restart, console, or save-edit recovery. Do not convert the narrow fix into an invented walkthrough. Treat the mission code, item-delivery failure, and Week 250 boundary as verified; use the live objective for every missing operational detail.
- Reading time
- 8 minutes
- Difficulty
- Quest identity, item and delivery-state diagnosis
- Checked
- 2026-10-06
On this page
Guide details
Before you begin
Use the Week 250 fix for RAD_O3 prospector heads that could not be delivered, while keeping counts, destination, acquisition, and reset steps Unknown.
Week 250 RAD_O3 prospector-head delivery fix; no invented count, acquisition, recipient, destination, prompt, reset, or old-prospect guarantee.
- Status
- Official ICARUS release evidence plus bounded exact-query review
- Edition
- Week 250–251 current-player evidence boundary
- Platform
- PC · Steam
- Checked
- 2026-10-06
- Check note
- Only the cited Week 250 release facts are verified. Search volume, keyword difficulty, external SEO score, unsupported recovery methods, numeric values, and later changes remain Unknown.
Before you set out
Prerequisites#
- Use Week 250 build 3.0.28.157342 or later on both the player client and session host.
- Confirm the active task is RAD_O3 and record the tracker text that asks for prospectors’ heads.
- Preserve the item names and counts shown by the live game without assuming a requirement that the source never states.
- Do not abandon the mission, discard quest items, edit saves, or promise a reset; the official line documents no such recovery.
What Week 250 says about RAD_O3 head delivery#
The reliable answer is deliberately narrow. The Week 250 changelog says RAD_O3 had an issue where the prospectors’ heads could not be delivered as intended, and the update fixes it. That verifies a quest-delivery defect and a release boundary. It does not explain whether the failure was caused by item recognition, objective state, a receiver, an interaction prompt, a location trigger, or another internal condition. It does not identify the prospectors, publish an item count, tell players where to collect the heads, or name the intended recipient. Those details must come from the current live objective or separate evidence. This distinction protects the mission state. If the heads are in an inventory but the tracker does not accept them, confirm RAD_O3, match client and host builds, and preserve the objective wording. Attempt only the interaction currently shown by the game. Do not repeatedly drop quest items, transfer them between players, move them through containers, or leave the mission area to provoke a refresh unless a current authoritative instruction supports that action. The patch confirms corrected delivery behavior from Week 250, but it does not state whether an item or objective created under an older build is revalidated. Record prospect age and multiplayer ownership if visible, but do not turn either into an asserted cause. A precise remaining-failure report is more reliable than a guessed route through an undocumented quest.
Route 02
Check ICARUS RAD_O3 prospector heads that will not deliver#
Follow the current objective and Week 250 boundary while avoiding invented counts, destinations, or item-reset methods.
Confirm RAD_O3#
Read the mission code and title. This official fix is not evidence about every quest that uses a body part, trophy, sample, or delivery objective.
Capture the objective text#
Record the exact delivery instruction before interacting. The release note does not publish the step wording or intended destination.
Check the client build#
Verify Week 250 build 3.0.28.157342 or later. An older client is outside the documented fix boundary.
Check the host build#
Confirm that the host or dedicated server runs the corrected build too. Shared mission state cannot be judged from the joining client alone.
Read the live quest-item labels#
Use the current inventory or objective interface to identify the items. Do not replace the game’s wording with a guessed item name or required count.
Keep the items in their current valid state#
Avoid dropping, destroying, splitting, transferring, or storing quest items simply to force recognition. The official fix provides no such sequence.
Use the visible delivery interaction once#
Follow the prompt, location, person, or device shown by the current objective. This guide does not invent a destination missing from the source.
Watch for tracker advancement#
Observe whether the item state changes and the objective advances before taking another action. Save the before-and-after wording.
Record the prospect boundary#
Note whether the prospect began before Week 250. The release does not guarantee migration or replay of a previously failed delivery.
Preserve a remaining failure#
Keep builds, host type, objective, item labels and counts, destination shown, interaction result, prospect age, and participating player roles as observations.
Pocket list 03
Verified RAD_O3 delivery boundaries#
- Affected task — RAD_O3.
- Affected items — prospectors’ heads, using the publisher’s wording.
- Documented failure — the heads could not be delivered as intended.
- Fix boundary — Week 250 build 3.0.28.157342.
- Unknown — required count, acquisition route, item ownership, and exact labels.
- Unknown — recipient, container, location, prompt, and objective sequence.
- Unknown — relog, transfer, drop, restart, console, save-edit, or older-prospect recovery.
- Search volume, keyword difficulty, and external SEO score remain Unknown.
Fault ledger
If RAD_O3 still rejects the heads#
- The host is older than Week 250
- Update and restart the host before testing. Delivery state may be session-controlled, so the current client alone is not enough.
- The objective is not RAD_O3
- Use evidence for the actual mission. This patch line cannot validate another quest’s items or delivery target.
- The item name or count is uncertain
- Read the live objective and inventory. The official note confirms the item type only in general and supplies no quantity.
- The prospect predates Week 250
- Record that fact and preserve the state. Automatic repair or replay of an older failed delivery is not promised.
- A workaround requires dropping or editing items
- Treat it as unsupported here. The cited release gives no manual item-reset, console, or save-edit procedure.
Field questions
RAD_O3 prospector-head questions#
- What did Week 250 fix in RAD_O3?
- It fixed an issue where the prospectors’ heads could not be delivered as intended.
- How many heads are required?
- The saved official changelog does not provide a count. Use the current objective and keep the number Unknown here.
- Where do I deliver them?
- The cited source does not name a recipient, device, container, or location.
- Should I drop and pick up the items again?
- That recovery is not documented by Week 250 and could risk the mission state.
- Will an old stuck mission repair itself?
- The release does not guarantee migration or replay for a prospect already stuck before the patch.