The short decision rule
Keep any working part that matches an active job, a device family you repair regularly, or a donor set whose remaining pieces are clearly labeled. Shred a component only after the game marks or testing confirms it as broken and no current repair, route, or comparison needs it. Being common, ugly, or unused today is not proof that it is worthless.
Decision table
Audit the part in this order before using the shredder.
| Part state | Decision | Reason |
|---|---|---|
| Working and required by an accepted job | Keep and reserve | It already has a higher-value use |
| Working, matching a frequent device | Keep in labeled stock | It can prevent a later purchase |
| Working but version is unknown | Quarantine and identify | Appearance alone does not prove compatibility |
| Confirmed broken with no test value | Shred when convenient | It cannot complete a repair |
| Story device or branch checkpoint | Do not shred | Preserve the route and comparison save |
| Inventory is crowded | Organize before destroying | Clutter is an information problem first |
Label donors before dismantling
Record the model, technical version, seller description, needed component, and customer job before opening a donor. Store working leftovers under the same model. This prevents a compatible piece from becoming anonymous clutter and makes it easier to see when several partial donors can cover a later repair.
Do not confuse broken and unprofitable
A part can work while the overall donor purchase loses money; it can also be broken but still useful for confirming shape, layer order, or a bug reproduction. Decide the repair value first and the economic lesson second. Shredding a working piece does not undo an overpriced purchase, while keeping every confirmed failure forever does not recover the cost either.
Shredder timing and achievements
The public Steam list includes buying the shredder as an achievement. That unlock does not require feeding it every leftover part. Purchase it when confirmed junk is accumulating and the shop retains its repair reserve. Keep an unmodified checkpoint before testing story or rare-device stock so completion cleanup cannot damage a route.
Five-second audit
Before shredding, answer each question.
- Is the part explicitly confirmed broken?
- Is its exact model or version recorded?
- Is it reserved by an accepted order?
- Could it complete a frequent device family?
- Is it tied to a story or test checkpoint?
- Does a protected save exist before the action?