1666: Amsterdam

Right now, the current chapter asks for a medium commitment rather than a season-long obsession. Most people looking for the full shape of the current release will reach that point in about 10 to 15 hours, with a little extra time if they search every corner and read everything. That makes it manageable across a couple of weeks, not months. The good news is that the structure helps. Investigations, safehouses, and night confrontations create natural places to stop, and full pause means real-life interruptions are usually fine. The less good news is that the autosave system adds friction. You cannot freely lock in progress whenever you want, so ending a session carelessly can cost you recent work. Returning after a week away also takes a few minutes, because you may need to remember which suspect you were chasing and what clues still matter. This is a solo game with no social obligations, no team schedule, and no ladder to maintain. It fits a normal week reasonably well, as long as you respect the autosave rhythm.

Most sessions ask for steady, active attention, but not absolute tunnel vision. You’re usually tracking several light threads at once: where a suspect was last seen, which rooms you already searched, whether using magic in public is worth the risk, and when to switch from Noa to Aaron for a cleaner route. That layered thinking is the real workload. The combat itself is simpler than the mystery side, but it still wants real-time dodges, camera control, and potion use, so the game never becomes something you can half-watch while folding laundry. In return, that attention pays off in strong detective momentum. A clue found in daylight can make a whole district click, and a clever cat-led shortcut can make you feel sharper than the systems really are. The rough onboarding raises the first few hours, because you’re learning around the game’s awkward edges as much as through its actual design. Once it settles, the experience feels more like careful tracking than raw button pressure.

This is medium difficulty, but the learning process is bumpier than the enemy design alone would suggest. The main hurdle is getting comfortable with its rhythm: investigate during the day, manage suspicion, understand what Aaron can do, and recognize when you have enough preparation to survive the night. None of that is wildly deep on paper. What slows you down is that the game explains itself unevenly and asks you to absorb a few unusual controls and camera habits before things start feeling natural. The good news is that it does not demand perfect execution every second, and it is nowhere near a punishing action game built around flawless reactions. The bad news is that mistakes can waste time because saves are not fully in your hands, and deaths can reset momentum in annoying ways. The game asks for patience up front and delivers a satisfying sense of “I finally get how this works” once its day-night loop clicks.

The mood is dark, uneasy, and occasionally sharp, but it is not nonstop panic. Long stretches are about walking smoky streets, reading notes, and quietly narrowing down a suspect. The pressure rises when suspicion starts climbing, when night falls, or when an Esbat fight begins and the game asks you to dodge cleanly while managing space and supplies. That creates a nice horror-adjacent push and pull: calm setup by day, anxious payoff by night. The catch is that some stress comes from the build’s roughness rather than from clean dramatic design. A messy camera, weak lock-on, or uneven save timing can make failure feel more irritating than thrilling. If you like spooky historical mood with bursts of action, that trade can still work well. If you want smooth, confident combat or pure cozy exploration, this may feel harsher than its mystery framing suggests. It is tense in pockets, grim in tone, and only occasionally heart-racing.