Emma can command the Blight’s plant-like growth for traversal. Official and hands-on material shows vines shaping routes, including bridge-like crossings, wall or elevation access, and positions that support falling attacks. This makes navigation part of encounter planning rather than a separate movement minigame.
The final Steam build must establish the interaction input, permitted surfaces, progression gates, fall rules, and route reset behavior. Use visible prompts and landmarks instead of assuming all vegetation is interactive.
Identify a traversal anchor
Before activating anything, locate the stable origin: a ledge, wall, broken bridge, large root, or path junction. Record the direction Emma faces and the visible destination. A plant effect can change the scene dramatically, so a before-and-after pair helps another player recognize the correct spot.
Use the game’s final term for the action if a tutorial names it. “Vine route” is descriptive, but a canonical mechanic name should take priority. Record whether the prompt appears automatically, requires target selection, or depends on story progress.
Read bridges and climbs differently
A horizontal vine bridge solves a gap and may expose Emma while crossing. A vertical route changes elevation and can reveal side space or combat angles. Record width, one-way behavior, nearby enemies, and where the route deposits the player. Do not treat a climb as a fast-travel system.
If the plant persists, test whether it remains after reload or return. If it retracts, note the trigger. Persistence is useful map information and can also show whether an earlier route is now permanently open.
Turn elevation into a deliberate opener
Game Informer’s preview observed vine-assisted falling assassination. To document that in the public build, distinguish the navigation action from the combat result. Record the ledge, target state, prompt, landing, detection status, health or Down effect, and whether other enemies react.
A falling ordinary attack and a named assassination are not interchangeable. The game feedback decides. If the target survives, Emma needs an open-combat plan: orient the camera, defend, and use Koo if FP or an Art can stabilize the group.
Check side routes before committing forward
Plant growth can point toward optional huts, sheds, equipment, or alternate approaches observed in preview coverage. At a branch, identify the return route before dropping. Mark one-way descents, locked gates, and story transitions separately.
Do not describe a reward until it is captured in the release location. A pre-release item can move. The traversal entry should stand on its own as a route; the gear or collectible page can own the reward details.
Diagnose a missing vine prompt
Confirm the exact landmark and approach angle. Check whether combat is active, whether the story has introduced the ability, and whether another path must be completed. Inspect the final control menu rather than copying a console glyph. Reload only after recording the current state.
If another player sees the prompt, compare story progress, visible version, platform, and whether the route was already activated. Do not immediately label the absence a bug. It may be a progression condition, completed interaction, or wrong surface.
Record movement safety
Test whether Emma can leave the route, take fall damage, be hit during movement, or cancel the action only in a safe repeatable area. Capture accessibility or camera options that affect traversal presentation. Avoid encouraging out-of-bounds movement or unsupported skips in a beginner route.
For performance analysis, distinguish input failure from frame pacing. A hitch during a plant animation should be recorded with hardware and settings; it does not prove the prompt itself failed. The native Steam scope is Windows, while Deck/Proton behavior remained unverified before launch.
Create a route card
A useful traversal card includes region, landmark, route type, activation condition, destination, return path, combat opportunity, nearby reward link, version, and spoiler level. Add a short instruction that can be followed without the image. Test the route from the stated start.
Group cards by region rather than by generic action. That preserves context and prevents repeated descriptions of the same plant animation from becoming dozens of thin pages.
Traversal evidence
Emma’s command over plant-like Blight growth is described in the official Developer_Direct article and Steam Store material. Bridges, wall-like routes, and falling approaches remain attributed to Game Informer’s hands-on preview. Final controls, gates, and route placements await public-build verification.