Diagnose invisible assembly outlines, unclickable screws, and final-story delivery-box conflicts without risking the original save.
Protect the current save
- 1 Protect the current save
- 2 Leave the challenge after the first failure
- 3 Open another competition item
- 4 Return and test the lower-left screw before covering it
Identify which soft lock you have
If parts appear to drop into a plain box, the assembly outline may have failed to render. If the XI-box looks normal but the lower-left motherboard screw, hard drive, or disc drive will not highlight, use the XI-box branch. If the problem started while an assembly challenge box remained in the green delivery box during the final story beat, preserve that fact in the report.
| Symptom | Reported trigger | Safest next step |
|---|---|---|
| Cardboard box / invisible outline | Assembly challenge object not rendering | Leave the challenge and protect the save |
| XI-box screw or drive cannot be selected | Often reported after a failed attempt | Try one clean re-entry only |
| Old challenge box after the finale | Box present during the final story beat | Buy a fresh challenge box if possible; keep the old save |
One controlled retry
Community workarounds conflict. Some players recovered by leaving the item on the table, opening another competition item, then returning; others report that this did nothing. Make one protected test: exit the challenge, interact with a different item, re-enter, and check the lower-left screw before installing the covering parts. Stop if the hit target is still missing rather than burning more entries.
Keep removed parts visible and grouped by layer. Use the recorded order as a reference; if your Notebook shows something different, follow the game.
What not to treat as a fix
Randomly rotating every remaining part, repeatedly failing the timer, or overwriting the only good save does not repair a missing interaction target. A fresh competition box helped one final-story case, but left the broken purple box in the shop; treat that as a workaround with a cost, not a universal repair.
Developer-acknowledged report package
A developer replied that the final-story assembly-box issue would be investigated. Send the build, device, competition type, whether this was the first attempt, the last selectable part, the delivery-box state at the finale, screenshots or a short clip, and the protected save files. Link the exact thread so the report joins the existing cluster.
Research links
These are the primary pages used to check the facts and current release context in this guide.
Official information, observable release behavior, and community reports are deliberately separated. A community report is not presented as a universal fix until it can be reproduced or supported by current patch notes.