Gods Will Be Watching by Deconstructeam, published by Devolver Digital, is a severe point-and-click thriller about managing impossible situations with limited actions. This beginner guide is for players who want to understand the survival logic before pushing for perfect routes, achievements, or no-sacrifice clears.
Content warning: This mature guide discusses violent, coercive, and survival-themed scenarios in non-graphic gameplay terms.
Beginner does not mean the game is easy. It means the advice below focuses on repeatable habits: tracking information, balancing pressure, reading failure, and choosing difficulty settings that match your goal.
Essential Tips
1. Treat Every Chapter Like a Pressure Puzzle
Each scenario is built around too many demands and too few safe actions. Before clicking through a turn, name the meters that can actually fail you: time, morale, health, food, fire, distance, cyber security, antidote progress, or enemy pressure. If you cannot say what you are protecting, you will usually spend actions on whatever looks loudest.
2. Write Down What the Game Teaches You
Gods Will Be Watching expects repetition. Keep short notes for antidote guesses, route signals, character condition, and the last thing that went wrong. You do not need a full spreadsheet; a few lines beside the keyboard can turn a failed attempt into a better next run.
3. Balance Opposite Pressures
Many systems punish both extremes. Hostages can become dangerous if they are pushed too hard or left too comfortable. Survival chapters can collapse if you focus only on food and ignore morale, or only on morale and let the fire die. When a meter changes, ask what the opposite risk looks like.
4. Spend Actions Before the Emergency
Emergency turns are expensive because they remove choice. Keep wood before nightfall, make spears before predators become the only problem, rest or support exhausted characters before they break, and prepare tools before the chapter’s deadline squeezes you. A boring action taken early can save several desperate actions later.
5. Assign Jobs by Strength
Do not rotate everyone equally just to feel fair. Some characters are better suited to digging, science work, repair, hunting, or endurance. Use durable characters for heavy labor, preserve specialists for their unique jobs, and avoid spending a critical worker on a task someone else can handle.
6. Let Morale Be a Meter
Morale is not flavor. Food, speeches, rest, direct conversation, and who survives can all affect whether the group keeps functioning. If a chapter gives you several morale tools, mix them. A speech may buy time, but a hot meal or a direct check-in can solve a different kind of pressure.
7. Use Difficulty Modes for Your Goal
If you want the story and core ideas first, choose a lighter mode and learn the chapter structure. If you want achievements or the harshest intended challenge, Original-style play asks for cleaner planning and more tolerance for restarts. There is no value in forcing the hardest mode while you are still learning what each chapter is asking.
8. Scout Before Committing
When the game gives you a way to check the next risk, use it. In navigation-heavy situations, signal checks and scouting turn a confusing map into a solvable route. In other chapters, the equivalent may be checking character condition, reading robot statistics, watching security, or looking at how close enemies are.
9. Review the Cause of Failure
After a loss, do not restart immediately. Identify whether you failed because you ignored a meter, misunderstood a rule, ran out of time, overused a character, or gambled too late. The next attempt should change one or two decisions, not your entire plan.
10. Avoid Perfect-Run Thinking Early
The game tempts players to save everyone and avoid every ugly choice. That can be a satisfying long-term challenge, but it is a poor first objective. Learn how a chapter resolves, where its pressure spikes are, and which sacrifices are optional before planning a cleaner route.
11. Keep Chapter Goals Separate
The hostage chapter, cave chapter, survival chapter, and desert chapter do not test the same habits. Reusing one plan everywhere leads to bad reads. Start each chapter by asking what kills the run fastest, what advances the win condition, and what can safely wait.
12. Pause Before Moral Decisions
Hard choices often look like panic buttons. Before using one, check whether the same action also creates a new survival problem. Removing a mouth may help food, but it can damage morale or reduce your labor pool. Hurting a hostage may buy control, but it can push the room toward revolt.
Chapter Priorities
| Chapter Situation | First Priority | Beginner Habit |
|---|---|---|
| Hostage and hacking pressure | Keep control without overcorrecting | Watch both security progress and hostage mood |
| Captivity | Preserve enough health to reach rescue | Avoid taking damage just because one character can still stand |
| Cave antidote work | Track cure logic and escape progress | Use notes for test results and robot information |
| Wilderness survival | Keep fire, food, morale, and repair moving | Do not let one urgent meter consume every action |
| Desert navigation | Understand direction before marching | Scout and check signal before committing to movement |
| Original Mode attempts | Learn from every failed run | Restart with one planned correction |
Difficulty and Failure
Gods Will Be Watching is hardest when you treat failure as random punishment. Some outcomes can feel harsh, but many failed chapters reveal a rule: a meter was ignored, a character was overworked, a warning sign was missed, or a deadline was allowed to close too far.
For a first clear, use a mode that lets you understand chapter logic without exhausting yourself. For a harder clear, keep your notes from the easier run and tighten the plan. If the game offers less randomness or a story-focused setting, it can be a useful learning path rather than a concession.
The best mindset is controlled experimentation. Change a food plan, a work assignment, a scouting rhythm, or a morale response, then see what improves. Randomly changing everything after each loss makes the next failure harder to understand.
Common Mistakes to Avoid
-
Starting without a written plan - Track antidote clues, route signals, and failed choices so repeat attempts improve.
-
Spending every action on the loudest crisis - Keep quieter meters alive before they become instant failures.
-
Pushing hostages or allies past their breaking point - Pressure can solve one problem while creating a worse one.
-
Ignoring morale until someone leaves or collapses - Treat morale support as maintenance, not cleanup.
-
Using specialists for generic labor too often - Preserve key workers for science, repair, or other unique jobs.
-
Waiting too long to prepare survival tools - Wood, spears, medicine, and rest matter most before the emergency turn.
-
Moving through navigation chapters blindly - Scout and compare direction clues before spending movement.
-
Restarting without reviewing the loss - Name the failed system before beginning the next attempt.
-
Forcing hardest settings on a first clear - Learn the chapter rules first, then return for strict challenge goals.
-
Chasing a perfect route too early - Finish the scenario once before optimizing every sacrifice or survival outcome.
Summary
| Category | Top Tip |
|---|---|
| Planning | Identify each chapter’s failure meters before spending actions |
| Notes | Record clues, guesses, route feedback, and causes of death |
| Morale | Support the group before panic removes your options |
| Supplies | Prepare wood, food, tools, repair, and medicine early |
| Difficulty | Use easier modes to learn and harder modes to prove mastery |
| Navigation | Scout and check direction clues before moving |
| Restarts | Change one or two decisions after each failure |
Did this answer your question?
Your feedback helps keep the useful answers visible.Sources
8 checked for this guideEvery factual claim in this guide was checked against at least two independent sources before publication. These are the references used for Gods Will Be Watching.
Next answers
Community notes0
No community notes yet.
Sign in to contribute