Direct answer
Find your symptom, read its likely cause, apply the verified fix, and check the affected/build-fixed markers if relevant. Unknown causes stay UNKNOWN — never guessed.
Current problem records
| System | Symptom | Cause | Fix | Status |
|---|---|---|---|---|
| Plants | Plant not growing after planter reuse | Wrong soil composition | Dilute / add components to target | VERIFIED |
| Quest | Quest stuck with 4 epic salads | Bag/quest state report | Under investigation | OBSERVED |
| Quest | Can't find Atrium NPC | NPC location | Location guide in quests | OBSERVED |
| Drones | Drone station won't accept more stew | Station upgrade state | Under investigation | OBSERVED |
| Cooking | Stove still 1 portion after upgrade | Upgrade/portion state | Under investigation | OBSERVED |
| Greenhouse | Electricity billed before unlock | Billing timing | Logged; verify in build | OBSERVED |
| Controls | FOV / ultrawide request | Missing slider | Request tracked | COMMUNITY |
Search intent behind these pages
Google Autocomplete surfaces exact problem phrasings: 'tiny eden not enough sunlight', 'tiny eden drone not working', 'tiny eden plants suddenly dying'. Each earns a guide only after the Problem Page Gate passes.
✓
Evidence note
Problem records store cause, solution, affected build, fixed build, evidence and confidence. Recurrence from Steam/GSC adds weight to gate decisions.
OBSERVEDSteam discussions
Source: current Steam community reports for the 1.0 build, cross-checked against observed gameplay.
ℹ
Problem pages standalone only after the Problem Page Gate (see methodology). Otherwise they stay in this hub.