Cobalt Games / REKA

Woodland encounters

REKA quests. Company for the woods.

Keep a creature’s role, a neighbour’s request and a story choice distinct. Follow the active lesson without turning every encounter into a collection target.

A luminous deer stands among trees in an autumn forest.
A luminous deer stands among trees in an autumn forest.Official Steam image
Inside this field note +
Recognise three different kinds of companyInvite a cat to follow deliberatelyKeep conversation separate from companionshipTrack the promise you actually madeOptional opening-story landmarksRecord a choice without spoiling the next onePocket checklistQuestions
Field notes · 2 November 2026Current source: 1.0.25.afc5b3Sources & scope ↓

Recognise three different kinds of company

Crows are gathering tools, a cat can be a travelling familiar, and a wild animal can belong to a particular request. Their presence in the same forest does not make their interactions interchangeable. Begin with what the current scene or dialogue actually offers, then decide whether you want to pursue that relationship now.

Our recommendation is to write one short purpose beside an encounter. “Bring the requested food,” “try the familiar interaction” and “return after the next lesson” are more useful notes than simply listing the animal’s name. They also leave room to enjoy a creature without treating it as an unfinished task.

Invite a cat to follow deliberately

The developer’s October update describes pet cats acting as familiars: pick them up and set them outside to begin following. They can occasionally point out interesting things while accompanying you. This is specific guidance about cats, not proof that every forest creature follows through the same action or produces discoveries on a guaranteed timer.

Try the interaction on a quiet outing where you can notice what the companion is doing. If the goal is simply to enjoy its company, the journey need not become a search for an optimal reward. Keep the house arrangement comfortable for the creatures you choose to bring home.

Keep conversation separate from companionship

The tools reference describes the Tonic of Connection as a temporary animal-conversation tool. Speaking to an animal and keeping a familiar are therefore different systems. If a conversation-related interaction is unavailable, inspect the current tool and its state instead of assuming that carrying the animal or feeding an arbitrary ingredient is the missing step.

Read an encounter’s request carefully. A source can document berries for one deer-related favour without establishing a universal food for every animal. We would preserve an ingredient for the request that names it, and record a new interaction after observing its actual prompt.

TRY THIS NEXT · AN EDITORIAL PRACTICE

Company for one quiet outing

01

Notice

Identify whether the encounter is a tool, companion or request.

02

Try

Use the documented interaction for that particular creature.

03

Remember

Write what happened and whether a return conversation remains.

Track the promise you actually made

A village errand can begin with a conversation and finish after an action elsewhere. Keep the final return in your notes as well as the outward objective. Helping somebody, seeing the result and collecting a response are related moments, but finding an object alone is not proof that the dialogue has been resolved.

Use the game’s sidequest record and current markers for the active task. Our journal is a place for your intentions and observations, not a replacement map or an automatic quest checker. When several requests compete, choose the next one by the supplies and tools currently available rather than a copied completion percentage.

Reveal early story context +

Optional opening-story landmarks

Early quest names follow. Starting Out introduces Kopnik and the recipe-book handoff. Trial of the Chicken leads to raising the walking hut. Trial of the Forest Spirit introduces Leshy’s agreement around taking and returning to the woodland. These are orientation points for the opening, not a complete sequence of the finished story.

For the forest agreement, keep its replanting expectation in view rather than treating new gathering permission as unlimited extraction. Hotfix 2 also addresses Leshy becoming stuck while approaching the blessing. Compare an old troubleshooting report with the current developer notes before repeating a workaround that may no longer be needed.

Record a choice without spoiling the next one

Write what your character chose and why it suited your playthrough. You do not need a full reward list or an ending explanation to make that note useful. When a request presents competing wishes, allow the conversation to establish the situation before consulting a route that already resolves it for you.

Our source review does not claim every possible consequence in 1.0. The guide keeps later outcomes out of view and lets you open the early named milestones only when wanted. You can use the same habit in the browser journal: keep ordinary preparation visible, and reveal named story checkpoints separately.

FOLD INTO YOUR POCKET

Before the next outing.

  • Identify whether this is a tool, companion or quest interaction.
  • Try the documented cat-familiar action deliberately.
  • Keep a temporary conversation tool separate from adoption.
  • Record the return conversation as well as the outward errand.
  • Reveal early quest names only if useful.
Carry the plan into your field journal →

A FEW SMALL ANSWERS

Questions by the hearth.

Can every animal become a following familiar?+

The reviewed developer update gives the following interaction specifically for pet cats. It does not establish the same rule for every animal.

Do companions guarantee a discovery?+

The developer describes occasional interesting finds, not a fixed reward timer. Treat companionship and guaranteed resource income as different claims.

Will opening the milestone section reveal the ending?+

It contains early quest names and unlock context only. Later plot outcomes and final rewards are deliberately omitted.

Where these notes began.

Named mechanics follow the reviewed sources. Our exercises, planning diagrams and working order are editorial guidance. Current developer notes take priority over stale release labels; no completed Cobalt playthrough is claimed.

Publisher source ↗

Official developer gallery; capture build unspecified. Arrow keys move between images.