inZOI: The August update slips to early September — and if you've customized regions, you'll need to redo part of it

Bad news for inZOI players who were waiting for the August update: it won't arrive in August. Kjun, the game's director, announced it in his weekly letter of August 14: "the August update has been slightly delayed, and we now plan to release it in early September."

The delay comes with a warning that deserves preparation right now: if you have customized regions or spaces, you will likely need to re-save part of them after the update.

What the update will contain, and what it won't

Kjun is straightforward about its scope: "For this update, rather than adding new content, we focused on making the fundamental aspects of daily life and behavior in inZOI more natural. This won't be a particularly major update, but a lot of development work has gone into strengthening the foundations of our life simulation systems for the future."

In other words: no new content to check off, no new city, no new job. A plumbing update. It's a useful clarification for recalibrating expectations, especially since it comes after a series of more visible content updates.

The problem the studio is trying to fix: Zois that don't do what they came to do

Kjun describes the flaw with a concrete example, and it will resonate with anyone who has closely observed their Zois:

"Previously, when a Zoi visited somewhere like a burger restaurant, they would stay there for a certain amount of time. But instead of ordering and eating during that time, they might talk to other Zois, look at nearby objects, or perform other actions unrelated to the reason for their visit."

This is at the heart of a life simulator's credibility problem: a character who goes to a restaurant and doesn't eat there breaks the illusion more surely than any graphical glitch.

The two systems coming

The studio is responding with two distinct mechanisms, presented as complementary.

1. A hierarchy of actions by location. A system "that allows us to define the actions a Zoi should prioritize when entering a particular place." Behavior is therefore no longer decided solely by nearby objects, but by the nature of the place itself.

2. An interaction permissions system. It "allows us to specify who can use each object." This is the missing piece needed to distinguish an employee from a customer.

Put together, the expected result is this, as described by Kjun: "in a burger restaurant, we can make a Zoi order at a kiosk, wait at a customer seat, receive and eat their food, and then naturally head home once their visit is over. Employees will no longer sit in seats meant for customers."

This last detail is revealing: staff sitting in customer seats wasn't an isolated bug, it was the absence of an entire system.

The warning to remember if you've customized locations

Here is the passage that requires action on your part:

« However, if you have previously customized regions or spaces yourself, you may need to re-save some of this newly added information. The amount of data itself isn't significant, but if you've customized many different areas, it could mean a bit of extra work. »

The logic is mechanical: if the game starts requiring, for each location, a list of priority actions and a list of permissions per object, then locations created before these lists existed don't have them. They will need to be filled in.

The studio nonetheless announces a safety net: « we are also preparing a way to properly apply the new system via a reset ». A reset would therefore apply the default values all at once — presumably at the cost of your manual settings.

What you can do right now, without waiting: take stock of your customized locations. How many regions have you tweaked? Which ones do you really want to keep as they are? This assessment will be simpler to make with a clear head today than upon discovering the migration message in two weeks.

A consultation, not an announcement: the studio can backtrack

The most unusual point in the letter is its wording. Kjun does not present these systems as final:

« I wanted to share this with you before applying the system to the development version, so that we could hear your opinion first. […] If you are against this change, we are ready to stop and reconsider it. »

This isn't an isolated courtesy formula: the studio already launched a player survey on August 7 about career and school updates. It consults before implementing, not after. Practical consequence: the content of the September update is not set in stone, and feedback posted before its rollout on the official Discord and forum genuinely carries weight.

Where to see the demonstration

One point that trips up many readers: the video showing the two systems in action is not in the Steam announcement. Kjun points this out at the end of the letter — « for the video, please check it out on Discord or the forum » — with a link to the first comment on the announcement.

Another procedural detail: these weekly letters are published in English only. The final French wording for the two new systems therefore doesn't exist yet; it will arrive with the update itself. The phrasing used here is a reading translation, not official naming.

What this changes for your ongoing save

Nothing, for now. The live version remains 0.9.6, deployed on July 30, and no intermediate patch has been announced since the known issues published on August 3.

In the medium term, however, two things to keep in mind. First, don't undertake any heavy customization project before early September: what you set up by hand risks having to be redone. Second, if your Zois' autonomy matters to you, go read the letter and respond — this is explicitly what the studio is asking for, and it says it will take it into account.