Shroud and Exposed ceiling-light placement · Week 250–251 current-player evidence boundary
ICARUS Shroud and Exposed Ceiling Lights Placement Fix
Quick Answer
ICARUS Shroud Exposed lights ceiling placement. If Shroud lights or Exposed lights are difficult to place on a ceiling, match the client and host to Week 250 build 3.0.28.157342 or later. RocketWerkz adjusted collision for both light families so ceiling deployment is easier. Confirm the exact light and that the targeted surface is a ceiling, record the placement preview and obstruction message, then try one normal alignment without demolishing nearby structures. The source does not publish snap distance, allowed angles, recipes, power requirements or a universal fix for every red placement preview. Other structural collision, ownership and support rules remain separate.
- Reading time
- 7 minutes
- Difficulty
- Variant, surface and placement-collision diagnosis
- Checked
- 2026-10-09
On this page
Guide details
Before you begin
Use the Week 250 boundary when Shroud or Exposed lights reject otherwise sensible ceiling placement because of collision.
Week 250 Shroud/Exposed ceiling-placement collision fix; no invented snap, angle, recipe, power, brightness, ownership or clipping claims.
- Status
- Official Week 250 evidence plus bounded exact-query review
- Edition
- Week 250–251 current-player evidence boundary
- Platform
- PC · Steam
- Checked
- 2026-10-09
- Check note
- Only the cited Week 250 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 250 build 3.0.28.157342 or later.
- Confirm the exact affected subject: Shroud lights and Exposed lights being deployed on ceiling surfaces.
- Record the exact light name, selected variant, ceiling piece, placement preview, collision point, nearby objects and any obstruction text before the test so the documented symptom stays separate from another system.
- Keep snap distance, allowed angles, collision dimensions, recipes, unlocks, power requirements, brightness and old-object refresh Unknown unless another current reliable source verifies them.
Why Shroud and Exposed lights resisted ceiling placement#
The official Week 250 line identifies collision setup as the specific problem for deploying Shroud and Exposed lights on ceilings. The correction adjusts that collision to make the two light families easier to place overhead. This supports a narrow diagnosis when an otherwise suitable ceiling position is rejected or awkward, but it does not disable all placement rules. A preview can remain invalid because the surface is not a ceiling, another object occupies the volume, the player lacks build permission, the item variant differs, the structure is unsupported, or a later rule applies. Record the item label, surface piece, preview color and message before changing the room. Try one deliberate alignment on the corrected build; do not demolish a base or exploit clipping to force acceptance.
How to preserve evidence for Shroud and Exposed ceiling-light placement#
Keep the original state observable until the comparison is complete. Write down the client build, host build, exact object or interface name, the exact light name, selected variant, ceiling piece, placement preview, collision point, nearby objects and any obstruction text, and the one normal action performed. A screenshot or short clip can preserve the presentation, but the visible in-game label and build are more reliable than a guessed internal cause. Do not combine an update, object replacement, reconnect, language change 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 object, animal or inventory state existed before the update and whether another player on the same host sees the same result. Preserve that evidence for a support report without describing an undocumented workaround as official.
Route 03
Check ICARUS Shroud Exposed lights ceiling placement#
Use this order to test the documented Week 250 boundary without inventing a destructive reset or unsupported mechanic.
Identify the exact subject#
Use the current in-game label and visible state to confirm Shroud lights and Exposed lights being deployed on ceiling surfaces. A similar tame, consumable, light or placement surface is outside this exact evidence.
Check the client build#
Confirm Week 250 build 3.0.28.157342 or later. An older client is below the documented correction and cannot demonstrate the fixed behavior.
Check the host build#
Match the host or dedicated server to the corrected build. A current joining client alone does not prove that the authoritative shared state uses the fixed path.
Record the pre-action state#
Capture the exact light name, selected variant, ceiling piece, placement preview, collision point, nearby objects and any obstruction text. Preserve visible labels, counts and prompts rather than relying on memory after the state changes.
Use one normal interaction#
Perform the ordinary action once: aim the supported placement preview at one clear ceiling surface and adjust normal position or rotation once without clipping through another object. Do not reload repeatedly, destroy an object, discard resources or edit files merely to force a different result.
Compare the corrected behavior#
Week 250 collision should make Shroud and Exposed lights easier to deploy on ceilings while ordinary obstruction and building rules still apply.
Separate adjacent symptoms#
A different failure may look related. Keep recipes, unlocks, power draw, wiring, brightness, support, ownership, general building collision and non-ceiling placement as separate issues unless current evidence connects them.
Note the pre-patch boundary#
Record whether the relevant animal, item stack, world or placement state existed before the update. The changelog does not guarantee that every stored state reconstructs immediately.
Preserve a remaining failure#
Keep client and host builds, host type, light variant, ceiling piece, preview color, obstruction text, rotation, nearby objects, permission state and whether the structure predates the update, and the exact outcome before making broader changes. That record is more useful than an unsupported reset sequence.
Pocket list 04
Verified Shroud and Exposed ceiling-light placement boundaries#
- Affected subject — Shroud lights and Exposed lights being deployed on ceiling surfaces.
- Documented symptom — collision setup made Shroud and Exposed lights harder to deploy on ceilings.
- Documented correction — Week 250 adjusts collision for Shroud lights and Exposed lights so they can be placed more easily on ceilings.
- Fix boundary — Week 250 build 3.0.28.157342-rel-DangerousHorizons.
- Unknown — snap distance, allowed angles, collision dimensions, recipes, unlocks, power requirements, brightness and old-object 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 ceiling-light preview is still blocked#
- The host is older than Week 250
- Update and restart the host before judging the correction. The authoritative shared state may remain on the older build even when the joining client is current.
- The subject does not match the changelog
- Stop applying this diagnosis and record the actual object, creature, item, interface or surface. Week 250 names Shroud lights and Exposed lights being deployed on ceiling surfaces.
- Only an adjacent mechanic fails
- Keep recipes, unlocks, power draw, wiring, brightness, support, ownership, general building collision and non-ceiling placement separate. The cited official line does not verify those systems or promise that they changed.
- The state predates Week 250
- Preserve that version boundary. A code correction is not proof that every older placed object, tame state or inventory stack migrates automatically.
- A workaround requires destructive changes
- Do not present deletion, demolition, console commands, database manipulation or save editing as official. Capture the failure and use normal support channels.
Field questions
Shroud and Exposed ceiling-light placement questions#
- What exactly did Week 250 fix?
- Week 250 adjusts collision for Shroud lights and Exposed lights so they can be placed more easily on ceilings.
- Which build is the verified boundary?
- Week 250 build 3.0.28.157342-rel-DangerousHorizons.
- Does this prove every related mechanic changed?
- No. recipes, unlocks, power draw, wiring, brightness, support, ownership, general building collision and non-ceiling placement remain separate unless a current reliable source explicitly connects them.
- Will updating repair every state created earlier?
- The changelog records the corrected 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, avoid destructive guesses and report the exact remaining symptom.