Track observed ReStory device sale prices without confusing one save's offer with a fixed value; includes Nony PMP economics and a reusable profit ledger.
Observed price database
An observed price is a dated data point, not a universal guarantee. Marketplace condition, progression, job context, or a later build can change the useful comparison.
| Device | License | Observed sale | Confidence | Action |
|---|---|---|---|---|
| Nony PMP | ¥40,000 | ¥23,400 | Current guide observation | Verify the offer in your save before selling |
| Atari Lynx | Check current unlock | Record from current save | No stable public value | Do not publish an estimate as fact |
| Atari 2600 | Check current unlock | Record from current save | Variable | Compare job payout with donor cost |
| Atari CX40 | Check current unlock | Record from current save | Variable | Keep useful donor pieces in inventory |
| Eggotchi | Check job/listing | Story value may exceed resale | Route-sensitive | Protect data and story objectives first |
Profit formula
Use net result = sale or job reward − device purchase − replacement parts − transaction-specific costs. Track a license separately as a one-time category unlock, then calculate how many paid jobs are needed to recover it. Charging the full ¥40,000 Nony PMP license to every repair makes every later job look falsely unprofitable.
Repair, donor, or resale decision
Repair when the needed part is cheap and the reward leaves margin. Buy a donor when several confirmed-good components are needed or its remaining pieces have future value. Resell only after story and active-job requirements are clear. Wait when the listing hides the exact condition or the cash reserve would prevent required story work.
A save-by-save price ledger
For each transaction record date, build, device condition, purchase, parts, reward or offer, and donor leftovers. Screenshots of the listing and completed offer turn a number into reproducible evidence. A single row can be useful; a median from several comparable rows is much stronger than a confident-looking guess.
Why some rows stay blank
Blank is better than fabricated. Public pages often describe a repair without showing the final sell screen, and values from preview builds may not survive release. This database will add exact figures when the screen, build, and device condition can be tied together. Until then, use the in-game offer in your own save.
Sale checklist
Protect progression before optimizing cash.
- Update the game and note the build
- Save before buying or selling
- Capture device condition and listing
- Separate license cost from per-device cost
- Subtract replacement parts
- Keep route-sensitive devices until their story objective is complete
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.