A source-checked XI-box dossier with parts, screw counts, reassembly order, costs, competition data, and current bug reports.
Keep your place while you work
Progress is stored only in this browser and is never uploaded.
XI-box at a glance
Current records list 14 distinct pieces, 19 screws, an XI-box license, hacking support, and a ¥90,000 sale value. Ten of the fourteen pieces can carry dirt. The rebuild-parts total also equals ¥90,000, so buying every component leaves no margin before the job reward.
Parts, screws, and rebuild order
The table follows a community-recorded release-build reassembly sequence. The two Front Panels are separated by position and price because the game lists them as distinct pieces.
| Order | Part | Screws | Recorded cost |
|---|---|---|---|
| 1 | Back Panel | 0 | ¥10,930 |
| 2 | Motherboard | 6 | ¥12,860 |
| 3 | Right Ports | 2 | ¥4,500 |
| 4 | Left Ports | 2 | ¥4,500 |
| 5 | Fan | 0 | ¥2,250 |
| 6 | Power Unit | 2 | ¥10,290 |
| 7 | Motherboard Cable | 0 | ¥1,930 |
| 8 | DVD | 1 | ¥9,000 |
| 9 | DVD Cable | 0 | ¥2,890 |
| 10 | Front Panel — side | 0 | ¥5,140 |
| 11 | Hard Drive | 2 | ¥9,640 |
| 12 | Hard Drive Cable | 0 | ¥2,890 |
| 13 | Ribbon Cable | 0 | ¥2,250 |
| 14 | Front Panel — top | 4 | ¥10,930 |
Keep removed parts visible and grouped by layer. The article’s order is the source of truth for the named device; the screenshot illustrates the bench workflow.
Open original page →How to use the order safely
Use the table from the inside out only after documenting your own teardown. Photograph each layer, keep screw groups with the part they secure, and compare the live Notebook before installing the next cover. If the current build disagrees, follow the game and report the mismatch rather than forcing an older sequence.
Parts cost and sale-value boundary
The recorded component values sum to ¥90,000, matching the listed device sale value. That is a rebuild-cost comparison, not guaranteed profit: customer rewards, dirty but reusable parts, donor stock, and the 1.0.013r marketplace rebalance can change the practical outcome.
Tourist order and competition
A current database records a stage-five Tourist order with one broken and three dirty parts and a ¥27,000 reward. It also lists assembly entry at ¥1,400, prize ¥6,200 and net ¥4,800, with a 2:53 record. Treat event figures as build-sensitive and confirm them at the counter.
Marketplace decisions start with the listing: compare condition, price, seller information, license access, and the parts or resale purpose before buying.
Open original page →Reported missing-part and duplication issue
A focused Steam technical report describes an XI-box order duplicating the device and losing screws or parts after advancing the day. A developer acknowledged it as a new issue and requested save/log evidence. This is a player report, not proof that every XI-box is broken. Preserve a save before hand-in and avoid advancing the day with an incomplete XI-box if the symptom has already appeared.
Verification checklist
Before returning the device, confirm the fourteen named pieces, all nineteen recorded screws, cable seating, both Front Panels, and the remaining task counter. If anything is missing, stop before hand-in and compare the current Notebook, inventory, workbench and parts store.
- Before returning the device, confirm the fourteen named pieces, all nineteen recorded screws, cable seating, both Front Panels, and the remaining task counter
- If anything is missing, stop before hand-in and compare the current Notebook, inventory, workbench and parts store.
XI-box FAQ
Which license is needed? Current records list XI-box. Is 19 the case-screw count? It is the total recorded across the fourteen-part rebuild, not just the outer shell. Is the order official? No; it is cross-checked community data from release-window records, so the current in-game Notebook wins if it differs.
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.