Ambrosia Sky Hidden Items Cleanup Checklist
Use a hidden-items checklist for ceiling scans, side rooms, cleanup percentages, and return routes in Ambrosia Sky.
Hidden Evidence Read
Source pair: https://ambrosiasky.featureupvote.com/suggestions/676840/collectible-totals-are-incorrect and https://steamcommunity.com/app/3580160/guides/.
Hidden items are easiest to miss when the player treats cleanup and collection as separate chores. In Ambrosia Sky, a cleaned wall can reveal a passage, a tether angle can expose a ledge, and fruiting bodies can draw attention away from a smaller collectible marker. Use this checklist after the hazard is controlled: sweep ceiling lines, inspect side rooms, and re-enter any space where the main objective changed the layout or lighting after the first cleanup.
The public collectible totals report makes the counter worth checking, but the player still needs physical evidence before declaring a route bugged. Mark hidden items only after you can identify the object, the access method, and the room condition that made it visible. If the route used hidden passages, record whether they opened through spraying, movement, or story progress. That habit makes the cleanup checklist useful for completion players while avoiding unsupported claims about exact item totals or reward values.
Run the hidden-items pass in layers. The first layer is safety, where hostile growth and blocked movement are removed. The second layer is visibility, where Dalia looks behind cleaned walls, upward angles, and side rooms. The third layer is confirmation, where the player checks whether the collectible counter or personal notes changed. Keeping those layers separate helps when a hidden passage reveals only a resource, or when a collectible-looking object is actually part of the room's story dressing.
Final checkpoint: hidden items should be marked found only after the object, access route, and changed room state all match the player's own notes.
Check hidden items first.
Then compare collectibles.
Use fruiting bodies as the mechanic or scene cue.
The page angle is to scan hidden items after cleanup opens sightlines.
| Evidence item | Practical use | Player risk |
|---|---|---|
| hidden items | Establishes the main route or status anchor | guessing from memory |
| collectibles | Adds a second check before leaving | skipping the real blocker |
| fruiting bodies | Connects the page to a named mechanic or scene | treating all rooms alike |
| hidden passages | Shows what to inspect after cleanup | spending resources too early |
Hidden Route Decision
Route decision: split ceiling, side-room, and passage checks into separate passes.
Stop after any visible room-state change.
Test movement, sprayer logic, story interaction, then collection.
Keep unsupported coordinates or rewards out of the route.
| Route step | Do this first | Confirm before moving on |
|---|---|---|
| Safety | remove the nearest active hazard | Dalia can move and read the scene |
| Objective | inspect the named blocker | the mission text or room state changed |
| Resource | harvest only after danger is controlled | hidden passages remains available if needed |
| Return | note one reason to revisit | tether is not silently forgotten |
Hidden Failure Check
Failure check: avoid turning resource collection into a first-route spoiler.
Mission pages compare objective text with the latest room change.
Cleanup pages inspect remaining growth before assuming a bug.
Movement pages look upward and behind the main path.
Story and update pages avoid unsupported interpretation.
Hidden FAQ
What first? Verify hidden items and collectibles.
Does this replace video? No, it is a source-backed decision note.
Why cautious? fruiting bodies, hidden passages, and tether need source support.