ReStory parts and tools database — demo-confirmed inventory

What counts as confirmed inventory

This database records a tool, part channel or component only when an official store page or developer post names it. It does not read tiny icons from a trailer or import a real-world repair kit into the game. ReStory is a stylised simulator: the developers aim for recognisable disassembly while deliberately simplifying some hardware.

Confirmed parts acquisition routes

The official store page directly confirms “surf the web for spare parts” and calls the browser a Y2K-era parts-hunting feature. It also confirms both in-person and online customer orders, but does not say every part arrives the same way. The current demo announcement specifically places the Airbrush and color palettes on the computer store.

One press demo observation, already covered in the profit guide, describes buying duplicate devices and stripping them for spare components. That is useful evidence that donor devices worked in the demo, but it is not proof they are always cheaper than individual parts in the launch economy.

Device components officially shown in detail

The Atari devlog gives the rare component-level example. For the in-game Atari 2600/2800-style hardware, the developer lists four screws, a motherboard, joystick, top and bottom casing, a red button and power cables. The post says the motherboard-to-power-cable connection is the one major difference from the real disassembly because the game simplifies that area.

This row is valuable because it establishes the standard for future component entries:

We do not apply the Atari component list to every console. Each device needs its own verified teardown because screw count and part order are exactly what change.

Airbrush and palettes

The June demo adds a clear post-repair customization layer. Players purchase the Airbrush and color palettes on the computer, then paint devices. The announcement says it works on all devices in that demo context. It does not publish palette names, prices, refund rules or whether a customer can reject a design.

Customization should therefore be tracked separately from fault repair. A device may be mechanically complete before painting, and screenshots of artwork are not evidence of a profit bonus. Any economic effect needs launch testing.

Tool progression without invented tiers

Official copy promises “multiple tools,” and the loop names operations that imply different tools, but there is no first-party launch table of Basic/Advanced/Pro tiers. The safe planning order is operational rather than numerical:

1. Identify the faulty device and required operation.
2. Confirm the needed tool or replacement part is available.
3. Disassemble in the shown order and keep components organised.
4. Clean or replace the fault, then reassemble.
5. Customize only if the order or your own plan calls for it.

Current release-build inventory boundary

Exact tool names beyond Airbrush, tool prices, upgrade effects, consumables, component compatibility, shipping time, stock refreshes and a complete parts catalog are still not published as a single official table. The v1.0.009r release patch does confirm fixes around inventory handling, the sonic bath and firmware updates, but it does not provide a complete parts catalog or numeric economy. Keep those fields unconfirmed rather than filling them with demo assumptions.