The engine learns shadows + a new narrative workbench

Two lines advancing: image quality steps up, the tool family grows

This day split clearly into two lines. One is the engine's image quality: the previous days lit up lighting, and this day added shadows and ambient light, moving images from "lit" to "having volume and atmosphere." The other is the expansion of the tool family: atop the "split-surface plugin" architecture established the day before, new workbenches moved in one after another — narrative, character, a UI workshop, each with its own role. One line pushes toward "looks good," the other toward "convenient to make," and together the platform grows both more beautiful and more complete. This rhythm of "low-level image quality + upper-level tools" advancing in parallel is exactly why it can be both an engine and a productivity platform.

The engine learns to cast: directional-light shadows

Engine rendering crossed a key threshold this day — directional-light shadows. Objects now cast shadows under a directional light (like sunlight) and receive shadows from others. A shadow looks like just a dark patch on the ground, but it's a major source of an image's "depth": human eyes largely use shadows to judge height, distance and contact between objects — without a shadow, a character floats above the ground like a sticker; with one, it truly "stands" there. Getting directional-light shadows right is a key step from "objects are lit" to "objects exist in a space," and a foundational capability no game aiming for realistic scenes can avoid.

Image-based sky light + per-object textures

Beyond directional-light shadows, this day added two more capabilities that make images more real. One is "image-based sky light": using an environment image as a light source so objects are softly lit by their surroundings — shadowed areas no longer go dead black, and metal and smooth surfaces reflect the look of their environment, making the whole scene's light suddenly far more natural and refined, a key part of approaching realistic rendering. The other is fixing "per-object material texture binding": different objects in the same scene can now each carry their own texture, with no more crosstalk where "changing one object's texture affects another." With directional shadows + ambient sky light + per-object textures together, the engine is much closer to rendering a complete scene that simply "looks right."

A new narrative workbench

The tool family welcomed a new member this day: a narrative workbench. Riding the split-surface plugin architecture established the day before, it lives in the workbench as an embedded tool window filling the main area to organize a game's story and text. It solves a real fragmentation — making a game isn't just writing gameplay code but also scripting plot, writing dialogue, designing branches; these often had to be done in another tool and then somehow brought back. Now "building gameplay" and "writing the story" advance inside one platform, with no switching and copying between separate tools. It also confirms the value of that split-surface architecture: it lets the platform plug in workbench after workbench of different functions, like building blocks, steadily.

Character workbench: keeps your assets, takes your uploads

The character workbench took a big step this day from "fun to try" toward "actually usable on a project." The key is asset persistence: generated portraits and assets are now saved, still there when you close the workbench and come back, with no regenerating each time — a qualitative difference for someone refining a character repeatedly. The two sides of a split view stay in sync, so editing one updates the other rather than them disagreeing. You can also upload your own existing assets to use alongside, not relying on generation for everything; and generation can route to different external services on demand, picking the right one for the image. Together these turn the workbench from an interesting demo into a tool that can genuinely carry everyday creation.

A new UI workshop + cross-platform and interface polish

This day also added a UI workshop workbench, continuing to expand the tool matrix; the interface aligned details like the tool switcher bar and collapsed-state width to the design spec for a tidier look. The low level cleaned up a batch of things too: removing a few build-time plugins no longer needed, consolidating some examples' namespaces, and fixing a cross-platform path-handling bug on Windows — so developers on more systems can run smoothly. Individually these look minor, but they matter as much as the big features above: big features decide what the platform can do, while these polishes decide whether it's actually pleasant on your machine, in your day. Doing both solidly is what lets the product hold up.

What this day means

This day pushed both "good-looking" and "usable" forward. The engine learning to cast shadows and adding ambient sky light means it genuinely has the ability to render a real scene with volume and atmosphere; the narrative, character and UI workbenches moving in one after another mean "the various jobs of making a game" can start to be done in place within one platform. A game is more than code — it has visuals, plot, characters, an interface — and this day happened to place pieces across exactly these dimensions at once, bringing the platform closer to "one person can make a complete game right here." Growing low-level image quality and upper-level tools together is the steadiest way down this product road.