Genshin’s Miliastra editor update makes iteration part of the play

An update to the workshop changes the workbench

HoYoverse published “Version 7.2 - Editor and Miliastra Sandbox Update and Fix Notes” on November 4, 2026. The notice describes changes to the in-game editor and sandbox used to create Miliastra Wonderland stages, including a custom Take Photo control, refinements to UI control groups, and added or adjusted editor functions. The notice is a technical change log; it does not say that any particular stage has become better or that the tools will suit every creator. [1][2]

That distinction matters. A creator tool is not only a box of objects and effects. It is also the set of ways a person can inspect what they have made, find a failure, and try a different solution. An editor update can change the practical shape of a project even when its central premise stays the same. The player who designs a chase, puzzle room, or social space has to work through the same loop: imagine, build, test, adjust.

Treat a stage as a sequence of questions

Before opening the editor, write down what the player should understand at each point. For a short collection challenge, that might be: Where is the objective? What can stop me? How will I know I am making progress? A stage that cannot answer these through its layout may need more than decorative additions.

Then build the smallest version that can test the premise. If the concept is “find three switches while avoiding a moving hazard,” first make the route legible and the switches reachable. Add visual style after the core route works. This order makes an early test useful: a missed switch indicates a visibility or route problem, whereas a missed switch hidden behind a wall of effects tells you less about which part failed.

Use new control and capture options as part of that loop. A custom photo control can help a creator inspect or preserve a view from within a stage, while UI controls affect how players perceive the available actions. Those functions do not replace playtesting. They make observation and presentation part of the design process.

Make one change at a time

A practical revision pass can be divided into three checks. First, test comprehension: can a new player identify the goal without a spoken explanation? Second, test flow: does the space provide a clear next action after each success? Third, test feedback: does the stage visibly or audibly acknowledge an important action? Change one major feature between attempts so that the result stays interpretable.

For instance, if testers miss the second switch, resist adding arrows, lights, sound, and a new camera angle all at once. Move the switch or adjust the route, then test again. If the problem remains, add a cue. This is not a claim that every stage should be minimal; it is a way to learn which element is doing the work.

A tool update is an invitation, not a verdict

Version notes document available functions, not a design recipe. They do not establish whether a feature improves a stage in every context, and a creator should check the in-game editor after updating because controls and options may vary by platform or version. The strongest takeaway is procedural: use the editor to make the premise testable, gather observations, and revise with intent.

When browsing community stages, the same lens is helpful. Ask what the creator wants you to notice, what action the layout encourages, and how the stage signals success. Those questions let you appreciate both the finished experience and the decisions that shaped it. In a mode built around making and sharing, the act of iteration is part of the game’s design language.