PRACTICAL FIELD NOTES

Family Time Game beginner guide: make your first session useful

Start Episode 2 with its tutorial, try one building or animal interaction, and learn the documented save/load controls.

Last checked

For a first session, use free Episode 2 and open its tutorial menu. Start with one task from the guidebook, such as making planks or using a building command, before managing several tasks at once.

The steps below are preparation advice based on official Episode 2 notes. We have not playtested them. Use the in-game tutorial for exact controls and recipes.

1. Establish which build you have

Start by separating free Episode 2 from the newly announced Episode 3 and the future Steam edition. The developer's October announcement provides the episode routes; Steam still targets Q1 2027. Match a guide to the episode and build you actually downloaded.

Record the episode, build label, download date and instructions before starting. Episode 2 includes a tutorial menu and an in-game guidebook; use those for its controls before borrowing advice from older footage. Keep the original filename when comparing DX11 and DX12 downloads.

Use our official access checklist to find the right channel and the platform guide to compare the published requirements. A machine meeting a listed minimum is a starting point for checking compatibility, not a promise about performance in every colony.

2. Choose a small first goal

Steam describes building homes and beds, growing food and hunting with the family. For the first session, choose one building task from the Episode 2 guidebook.

For a first exercise, use the guidebook to try plank-making. Watch for the resulting planks and note which action produced them. This is a suggested learning task, not a required opening sequence.

When trying a building command, check three things separately: the target selected, the response to the command, and the finished structure. If construction stops, record the last completed step and any message on screen.

3. Separate the need from the bottleneck

If a task stalls, check the selected target, the materials named by the guidebook and the character response. Change one thing at a time so you can identify what resolved the problem.

Questions to investigate, rather than confirmed failure conditions for every build.
What you observeWhat to check next
A need remains unmetWas the resource actually produced, and does the build show how it reaches the character?
An order appears to do nothingDid selection or command feedback appear? Do the instructions name a prerequisite?
One task finishes, but pressure returnsWas that a one-off result, or can you repeat it at the current scale?
Activity becomes hard to followCan you observe one target or task without issuing more overlapping orders?

For a failed attempt, note the selected object, the command used and the visible result. Repeat the same steps once before changing the setup. This gives you a specific sequence to compare with the tutorial or report to the developer.

4. Learn what a command changes

Delegation becomes useful when you understand the feedback it gives you. Start with a single task and track three moments: the order is issued, a character responds, and an outcome appears. If one moment is missing, you have a narrower question to investigate.

The reviewed notes do not explain command queues, cancellation or priority rules. Use the tutorial for available controls and avoid issuing several overlapping orders while learning one task.

Once one command works, repeat it with a second target and compare the result. Keep the task small until you can follow each character response. For the other announced systems, see our colony systems guide.

5. End with a record you can reuse

A short note is more useful than a verdict such as “the AI is bad” or “everything worked.” Use this structure after your session:

  • Context: build label, operating system, and whether this was a new session or an existing save.
  • Goal: the single result you tried to produce.
  • Steps: the actions you actually performed, in order.
  • Observation: what changed, what did not, and whether it happened again.
  • Next question: one detail to check in the build notes or during your next session.

Episode 2's release notes document F5/F6 saving and loading. Check your build's instructions before using them, and do not assume autosave or progress transfer into Episode 3. Read the save and update checklist before replacing a working version.

Before ending the session, note your episode and build number, one task you completed, and any exact error message. Keep that note with the download so it is available after the next update.