Hearth and Hamlet Controls Guide

Comfortable controls matter in a cozy incremental citybuilder you might leave running while you plan the next quarry. This page covers practical mouse gathering, UI hiding, UI scaling, and Steam Deck notes for Hearth and Hamlet during the demo and the lead-up to the planned August 19, 2026 release on Windows and Linux. It does not claim the full game is already available.

Pair controls with resources (so you know what to gather), buildings (so you know what you are saving for), and system requirements (so your hardware matches the Steam specs).

Mouse and hold-to-gather

Hearth and Hamlet blends idle assignment with active gathering. Early on, your cursor is a temporary worker:

• Point at the resource you need most—usually food or wood.
• Use click / hold-to-gather interactions to bridge gaps while buildings unlock.
• Stop manually gathering a resource once assigned workers keep it trending up.
• Never let hold-gather distract you from placing the next tent or woodcutter.

Manual gathering is an S-tier emergency tool on the workers tier list, not a substitute for staffing. If you are still holding the mouse on trees an hour in, you probably understaffed wood or hit a storage cap—diagnose with resources.

Camera, zoom, and readability

Demo polish work specifically called out zoom and game-size adjustments for large resolutions such as 4K. If text or sprites feel tiny:

1. Open Options.
2. Look for zoom / game size / readability settings introduced in polish updates.
3. Combine them with UI scaling (below) instead of only lowering desktop resolution.
4. Recheck after a demo update—readability has been an active focus area.

A readable kingdom is easier to manage than a sharp but microscopic one.

UI scaling (Automatic or manual)

Full UI scaling support has been highlighted in public demo polish notes. You can set scaling to Automatic or adjust it manually in the Options menu. This is especially useful for:

• 1440p and 4K monitors where default UI can feel small
• Ultrawide layouts
• Steam Deck and other handheld-style displays
• Accessibility preferences for larger text targets

Recommended approach:

1. Start with Automatic.
2. If menus still feel small, raise manual scaling until resource meters are comfortable.
3. If the UI becomes oversized and clips, step down one notch.
4. Re-test after moving between monitor and Deck—ideal scaling rarely transfers 1:1.

Community feedback during the demo period pushed hard for interface scaling; treat the option as a first-class setting, not a cosmetic afterthought.

Shift+F11 — hide the UI

You can hide the UI with Shift+F11. Use it when:

• You want a clean screenshot of your hamlet
• You are enjoying idle growth and do not need meters for a minute
• You are recording a short clip of pixel-art lakes, swamps, or night lighting
• You need to judge whether a construction layout looks good without panel clutter

Press the same shortcut again to restore the interface when it is time to reassign workers or pass policies. Hiding the UI is not a pause—threats and production continue—so do not AFK through a raid with panels off unless you like surprises.

Audio comfort

Demo polish also emphasized more independent audio controls so music, effects, and overall mix can fit long cozy sessions. If you leave the game idling:

• Lower effects if repetitive gather clicks fatigue you
• Keep music at a level that signals mood without drowning podcasts
• Recheck audio after updates; mix changes often ship beside UI work

Comfort settings are part of controls even when they are not keybinds.

Stability-minded launch options

Public demo notes have mentioned additional launch options / command-line arguments for players hitting crashes during polish. If the demo fails to start or dies on specific hardware:

1. Verify game files on Steam.
2. Confirm you meet minimum specs.
3. Check the Steam community hub announcements for current launch-option guidance.
4. Avoid assuming every crash means permanent failure—demo stability work has been an explicit theme.

This wiki will not invent unofficial crash flags; prefer developer-posted options when you need them.

Steam Deck notes

Hearth and Hamlet lists SteamOS / Linux support beside Windows, and UI scaling notes explicitly call out Deck-class displays. Practical Deck tips:

• Set UI scaling before you fine-tune controls.
• Prefer shorter manual gather sessions; thumb endurance differs from mouse hold-gather.
• Keep the device plugged in for longer idle sessions if you are researching while docked.
• Use Shift+F11 sparingly on handheld—resource meters matter more on a small screen.
• Revisit system requirements if performance dips as the town grows.

Deck play is a great fit for a single-player cozy idler, but only after text is large enough to read in lamplight.

Suggested first-session control checklist

1. Boot the demo on Windows or Linux/SteamOS.
2. Set UI scaling (Automatic, then manual if needed).
3. Confirm audio levels for a long session.
4. Practice hold-to-gather on food, then wood.
5. Assign real workers as soon as buildings allow.
6. Try Shift+F11 once to learn the hide/show rhythm.
7. Open policies only after you can see happiness meters clearly.

Accessibility and session length

Incremental games reward glances over marathon strain. Scale the UI so a five-second check is enough. Hide the UI when you want scenery. Reassign workers with readable panels when a resource trend turns. These habits matter as much as any bind list.

Related pages

• Systems hub home: Systems
• Allocation help: Worker planner
• Polish themes: Demo patch notes
• Launch timing: Release date · Launch checklist

Learn the comfort settings now in the demo. On August 19, 2026, you will want the UI already sized for your monitor or Deck so the full single-player release—still upcoming—starts with clarity instead of squinting.