Rarely does a debut title from a new studio land with such thunderous impact as Sandfall Interactive’s Clair Obscur: Expedition 33. It is a game that feels both nostalgic and fiercely modern, blending the deliberate pacing of classic JRPGs with a visual fidelity that pushes current-gen hardware to its absolute limits. Set in a world inspired by Belle Époque France, it tells a haunting story of a Paintress who wipes away ages with a stroke of her brush.

Blueprints and Whispers

From a technical standpoint, this is a showcase for Unreal Engine 5. The implementation of Nanite and Lumen is among the best I’ve seen, allowing for environments that are densely packed with ornate architectural details without sacrificing performance. What is particularly impressive is that the team achieved this level of complexity almost entirely using Unreal’s visual scripting Blueprints, with very little C++ code—a significant feat for a project of this scale and visual fidelity.

The “Paintress” aesthetic is more than just a lore point; it informs the entire rendering pipeline, with certain effects and transitions looking like brushstrokes coming to life. However, while the levels are visually breathtaking, their layout can be deceptively labyrinthine. I often found myself inadvertently looping back to the start, lost in the sheer density of the ornate French-inspired architecture.

One stylistic choice that deserves special mention is the voice acting. Eschewing the typical high-octane shouting of action games, the cast often speaks in low, almost whispering tones—even in moments of despair or intense action. It gives the game a unique, somber atmosphere that feels distinctly deliberate and “stylish.”

The Combat Conundrum

The most significant design decision is the “Active Turn-Based” combat. Unlike traditional JRPGs where you might select a command and watch it play out, Expedition 33 requires constant player engagement. Every enemy attack can be dodged or parried in real-time, and your own attacks benefit from timed button presses.

A crucial piece of advice for any newcomer: test if you truly enjoy this combat loop early on. Because the game is a massive RPG, you will be engaging in these mechanics hundreds, if not thousands, of times throughout the journey. If the rhythm of parrying and dodging doesn’t click for you, the sheer frequency of combat might eventually feel like a hurdle rather than a highlight. For me, it added a layer of tension but I was exausted by the end.

Narrative and Character Depth

The story is a melancholic trek through a dying world, and for the most part, the writing is superb. It tackles heavy themes of grief, death, and the core of human existence with genuine maturity. The chemistry between the members of the expedition feels earned, and their individual motivations are slowly unpeeled like an onion.

However, by the third act, the narrative starts to lose its subtle touch. Themes that were previously explored through atmosphere and subtext begin to be discussed quite plainly and repetitively, making the existential weight feel a bit more forced than it was in the game’s earlier hours.

Rinse and Repeat

While the “active” nature of the combat is its soul, it can also lead to fatigue. Some late-game bosses have massive health pools, and maintaining perfect parry timing for 20+ minutes can be mentally draining. A bit more variety in encounter pacing—perhaps some “puzzles” within the combat system that don’t rely solely on reflexes—would have been a welcome addition.

Clair Obscur: Expedition 33 is a triumph of art and ambition. It proves that the turn-based genre still has plenty of room for innovation. Despite some third-act heavy-handedness and occasionally confusing level design, it is an essential experience for anyone who appreciates bold art direction and deep, challenging systems.

Other day iI woke to some unsettling news in the .NET ecosystem. Rumors are swirling—and some blog posts are starting to corroborate—that NUKE, the build system I’ve come to rely on for almost all my C# projects, is being effectively abandoned.

The word on the street is that the primary developer, Matthias Koch, has reached a breaking point. After years of pouring heart and soul into the project, the lack of financial incentive and the sheer weight of maintaining such a critical piece of infrastructure has taken its toll. What’s even more concerning is the talk that any future development might happen in a fork that could be closed-source or move to a paid model.

This hits home. Hard. I just wrote about how much I love Nuke, and now the foundation feels like it’s shifting under my feet.

The Search for a Substitute

When a tool you depend on enters “maintenance mode” or changes its licensing terms, the first instinct is to look for a lifeboat.

Interestingly, Cake 6.0 was recently released, and it seems the team there has been paying attention. They’ve introduced the Cake.Sdk, which feels very much like an answer to NUKE’s “code-first” philosophy. It moves away from the old .cake scripts and toward standard .cs files with a project-based approach. It’s got that IDE integration and strongly-typed feel that made me switch to NUKE in the first place.

Is it enough to make me jump ship? Not yet. For the time being, I’m sticking with NUKE. The existing code is MIT licensed, and even if the official repo is archived, the current version still works. But the long-term viability is definitely a question mark.

The Cost of “Free”

This situation shines a harsh spotlight on the open-source ecosystem. We—developers and businesses alike—have become incredibly comfortable building empires on the back of free labor. We depend on these “tiny” projects maintained by one or two people, and we often forget that there’s a human on the other side of that GitHub handle.

If we care about these tools, we have to support them. Whether it’s through GitHub Sponsors, Open Collective, or enterprise licenses, “free” always has a cost. If the maintainers can’t pay their bills or find a reason to keep going beyond “community spirit,” the project eventually collapses.

I’m at a crossroads here. Are you already testing the waters with Cake 6 or maybe something else like Modular Pipelines? For now, I’ll keep my Nuke scripts running, but I’ll be keeping a very close eye on the horizon.

The USA’s Academy of Motion Picture Arts and Sciences is about to host the annual Oscar Awards. These are the movies that I watched and can comment on.

1. The Secret Agent (8★★★★★★★★): Longer than needed, yet with a thrilling ending.
2. Weapons (7★★★★★★★): Uneven by design.
3. Sinners (7★★★★★★★): Ryan Coogler + Michael B. Jordan movie that blends blues, horror, and history.
4. One Battle After Another (7★★★★★★★): may be one of this year’s Oscar favorites, but despite the acclaim it left me oddly unmoved, with strong craft overshadowed by a story that never fully resonated.
5. The Devil Is Busy (7★★★★★★★): The routine of a abortion clinic.
6. Frankenstein (6★★★★★★): Reverent to the source but rarely surprising. Good performances carry a production that plays it too safe.

Documentaries

1. The Devil Is Busy (7★★★★★★★): A short documentary about a abortion clinic.

Animations

1. The Girl Who Cried Pearls (8★★★★★★★★): This short film is a mastery in stop motion animation; very touching.
2. KPop Demon Hunters (8★★★★★★★★): Gleefully maximalist. Combines idol culture and demon-slaying with more wit and heart than it has any right to.
3. The Girl Who Cried Pearls (8★★★★★★★★): Beautiful short animation.

Sequels often face the “sophomore slump,” but this sequel manages to dodge that trap by doubling down on everything that made its predecessor a cult classic. Kingdom Come: Deliverance II delivers on the original’s promises with newfound polish and ambition, making it easily my best experience of the year so far, as expected.

Kuttenberg Is the New Novigrad

From a technical standpoint, the leap in environmental density is staggering. The standout achievement is the city of Kuttenberg. Rendering a dense, medieval urban environment in CryEngine is a massive challenge. Unlike the small villages of the first game, this is a sprawling city with multi-story buildings, crowded marketplaces, and intricate alleyways. The developers had to significantly optimize their draw-call management and level-of-detail (LOD) systems to keep the frame rate stable while maintaining the gritty, lived-in aesthetic. The lighting system, particularly the way it handles interior shadows and cobblestone reflections, is a significant step up from the first title.

From Blacksmith to Ninja

As a developer, I’m always interested in the balance of progression systems. In this experience, the curve is somewhat front-loaded. By the time I moved to the second map and reached Kuttenberg, I was already a “super ninja.” This was largely because I took the first map very seriously, completing most of the side quests and engaging in every skirmish I could find. This provided enough opportunities to evolve Henry’s stats to a point where the quests in the second half of the game became a bit of a breeze.

While it feels rewarding to see Henry’s growth, from a design perspective, it highlights the difficulty of scaling content for a player who explores every corner. The combat, while refined and less “janky” than the original, can’t quite keep up with a fully leveled Henry, resulting in a power fantasy that contrasts sharply with the desperate survival of the early hours.

The Recurring Narrative Pacing Issue

On one hand, the amnesia setup is a clever narrative shortcut that sidesteps the “power creep” problem entirely. By stripping Henry back to a blank slate—forgetting combat techniques, alchemy recipes, and even basic survival skills—the developers justify the early-game fragility without having to invent a contrived injury or gear loss. It’s a diegetic reset button that feels surprisingly organic within the story’s opening chaos. That said, the trope wears thin quickly. The game hand-waves Henry forgetting everything—including how to hold a sword properly—while conveniently allowing him to remember key characters and plot-relevant details. It’s a functional solution to a difficult design problem, but one that lacks the elegance of the first game’s slower, more believable progression from village nobody to seasoned fighter. In trying to have it both ways, the amnesia framing occasionally feels less like storytelling and more like a designer’s duct tape.

Unfortunately, some of the old ghosts still haunt the machine. Just like the first entry, the sequel struggles with its final chapters. The story, which builds so much momentum in its middle act, feels rushed and confusing as it reaches its climax. From a narrative design standpoint, it’s a bit disappointing to see the same pacing issues repeat themselves. A more focused third act could have easily pushed this into a perfect 10/10 territory. It seems the team prioritized the systemic complexity and world-building over a tightly woven conclusion.

Despite the narrative stumbles at the finish line, the moment-to-moment gameplay is unparalleled. The world is denser, the quests are more varied, and the sense of being part of 15th-century history is stronger than ever.

A New Standard for Immersion

This title offers a level of immersive simulation that is hard to beat. It respects the player’s intelligence and rewards patience, even when its complex systems push back. If you loved the original, this is an essential experience. If you were put off by the previous entry’s rough edges, the added polish here might finally be enough to win you over. It’s a bold, ambitious, and deeply rewarding sequel that proves Warhorse Studios are masters of their craft, even if they still haven’t quite nailed the landing.

For many, the dream of receiving a letter from a magical school is a cornerstone of childhood. I should preface this by saying that I am not a fan of the books or the universe—quite the opposite, in fact. Despite my lack of personal connection to the source material, I can objectively say that this experience is a masterclass in world-building and high-budget adaptation. It finally gives this franchise the high-budget, open-world treatment it has long deserved.

Technical Execution

From a developer’s perspective, the implementation within Unreal Engine 4 is fascinating. The scale of the castle is staggering, and the way the developers handled the interior/exterior transitions is a significant technical feat. To maintain the sense of a seamless, sprawling structure, the team had to employ clever level-streaming techniques. You can wander from the highest astronomy tower down to the lake without a loading screen, which is no small task given the sheer density of unique assets and high-resolution textures packed into every hallway.

The lighting work is particularly noteworthy. The way the light spills through the stained-glass windows or reflects off the suits of armor in the corridors creates a palpable sense of history. Every corner of the castle feels like it has a story to tell, filled with magical curiosities and moving portraits that bring the environment to life in a way that feels “alive” rather than just decorated.

Design Decisions and Exploration

Exploration is where the project truly shines. Flying on a broomstick over the Scottish Highlands is an absolute joy, providing a sense of scale and freedom that is mechanically very well executed. The control scheme for the broom feels intuitive, and the transition between ground and air is smooth—a trade-off in design that prioritized player freedom over strict physical realism.

The combat system is another surprise. Instead of a simple “shooter” mechanic, it encourages you to chain spells together in creative combos. From a design standpoint, the cooldown management and spell-switching systems keep the encounters dynamic. It’s surprisingly robust, rewarding players for experimenting with different magical interactions.

Room for Improvement: The Open World Trade-off

While the castle is a masterpiece of environmental design, the world beyond its walls exposes some common open-world trade-offs. The “hamlets” scattered throughout the map lack the unique personality and asset density of the main hub. From a production standpoint, it’s understandable—building a world of this scale requires a balance between hand-crafted detail and procedural filler—but the contrast is noticeable.

Additionally, the main narrative about Ancient Magic is serviceable, but it doesn’t always feel as personal or urgent as it should. Some of the side activities, like the repetitive Merlin Trials, feel like classic “busy work” intended to extend the playtime rather than enrich the world.

Despite my personal indifference toward the lore, the final product is a triumph. It’s a polished, beautiful, and genuinely well-executed experience that sets a new bar for how to adapt a beloved fictional world into a video game. It proves that even if you don’t care for the universe, good design and technical prowess can still make for a compelling experience.