← Changelog
Daily2026-06-15

A dark-fantasy ARPG sample + upload-a-model-and-use-it

This day a dark-fantasy action-RPG sample with an animated hero appeared, threading the skeletal animation, cameras, combat and lighting built up over recent days into real gameplay for the first time; uploading a model now lets you see and use it in play immediately, an end-to-end path; you can also roll the conversation and project back to any past message; and the engine prepared to ingest professional model formats and landed a cross-device "record-and-replay" debug setup.

Assembling the parts into a game that actually moves

Over the past two weeks, the platform accumulated, piece by piece, the parts needed to make a game: moving rigged characters, shadow-casting lights, walkable scenes, importable models. This day, those parts were assembled into the same real game for the first time — a dark-fantasy action-RPG sample with a moving witch hero, switchable cameras, naturally-blended combat and nighttime atmosphere. It's a meaningful milestone: it proves those scattered capabilities aren't just individually demonstrable but can genuinely combine to support a flesh-and-blood game. The day's other lines all orbited "making creation smoother": turning model upload into an immediately-usable end-to-end flow, letting you roll back to any step of the conversation at any time, and paving the way for the engine to ingest professional modeling formats. In one line: moving from "the parts are ready" to "they assemble into a whole machine," and continuing to polish the assembly to be smoother.

A new dark-fantasy ARPG sample: Hellforge

This day a complete dark-fantasy action-RPG sample game was added. Its witch hero is a rigged character model with five animations — idle, move, attack and more — which is the first time the recently-completed skeletal animation was used on a real playable character; the witch is no longer a standing-still model but a living character who walks and fights. It offers two cameras switchable with a single key: an over-shoulder follow camera behind the character, and a slightly top-down 2.5D view like classic ARPGs; combat actions are driven by a state machine so the transitions between "idle → move → attack" blend naturally rather than stiffly. The scene carries night-vision atmosphere — dim moonlight plus a few camp torches — evoking the dark-fantasy mood. The sample's value is that it's the first time the platform threaded the separately-polished capabilities of skeletal animation, the camera system, combat logic and atmosphere lighting all into one game with complete gameplay. It's both a directly playable finished product and a ready starting point anyone wanting to make a similar action-RPG can stand right on.

A more independent editor + upload a model and use it now

The thing most directly benefiting creators this day was making "bring in a model → use it in the game right away" one end-to-end path. The play side gained complete model import, covering all of a model's internal sub-contents — mesh (shape), material (texture quality), texture (surface pattern), animation (motion), skeleton (the drivable bones) and more, missing none. This means you upload a model and can immediately see and use it in play, and rigged characters preview correctly in the edit view too; no more fretting over "it imported but doesn't display fully, or the animation/skeleton was lost." To read rigged models correctly, the underlying mesh validation was made to "understand" skeleton data — skinned vertices carry bone-weight information beyond ordinary vertices and are laid out differently, and validation must distinguish the two, or a skinned model would be flagged as malformed on import. Meanwhile, the editor absorbed the core of the front-end shell's framework and removed its old self-built docking layer, so it can now mount more fully independently and isn't bound to the main chat interface — leaving room to later embed the editor elsewhere or package it on its own.

Roll back to any past message + per-file diffs

This day the backend added a reassuring capability: message-level rollback points. In trial-and-error with the AI, you often hit "the earlier rounds were right, but the recent rounds drifted worse and worse" — from this day, every step of changes gets snapshotted, and you can "soft-revert" to the state at any earlier message, rolling back the last few unsatisfactory rounds in one click and starting over. The key is that it's "soft" and reversible: a rollback doesn't hard-delete what came after, and you can always return to a later state again, effectively fitting the whole creative process with a timeline you can drag back and forth. The interface clearly surfaces each rollback point, the dimmed parts that were rolled back, and the current edit state, and shows a per-file breakdown of exactly which files each step changed and by how many lines. The significance is that it turns "collaborating with the AI" from something requiring caution lest you break things into something you can boldly try — because however you try, you can always come back. The sturdier the safety net, the bolder people dare to explore.

Engine: paving the way for professional model formats + record-and-replay debugging

The engine designed and prepared to ingest the model formats that professional modeling tools output directly this day. Professional 3D modeling software usually exports a format that fully carries animation, skeleton and even physics parameters, while the platform currently mainly supports another web-common format — many professional assets must undergo a format conversion before use, and conversion inevitably loses detail. This day's design is for the engine to read professional formats directly, skipping the intermediate-conversion hassle so assets flowing from professional tools enter the game in their original fidelity. Another heavyweight was landing a "record → replay and compare" debugging infrastructure: it can record the rendering process and replay it pixel-by-pixel across different devices for comparison, purpose-built to catch the very-hard-to-reproduce regressions where "the same code draws differently on this machine." It also wired in ambient occlusion (naturally darkening corners and crevices that light can't reach, for stronger depth), and fixed a critical bug — previously, turning on anti-aliasing silently disabled custom material shaders; such "silent breakage" is the most dangerous because you have no idea where it went wrong, and this day closed it.

What this day means

The most memorable thing this day is the turning point the dark-fantasy ARPG sample marks: the platform is no longer just isolated capability points like "can make a moving character," "can import models," "can cast lighting and shadows," but assembled them, for the first time, into a complete game with a hero, cameras, combat and atmosphere. The value of capability points is ultimately redeemed by whether they can play together as a complete tune — and this day gave a resounding yes. The other things around it all pushed toward "letting more people assemble their own games more smoothly": instantly-usable model upload lowered the bar to using assets; rollback to any message lowered the psychological burden of trial and error; paving the way for professional formats broadened the sources of assets that can come in; and record-and-replay made visual problems easier to catch and fix. From accumulating parts to assembling a whole machine, to polishing each step of the assembly to be smooth — this day took a solid step toward the goal of "letting anyone assemble a real game."

← All daily updates