Dev Notes — Nov 2, 2026

This Week

• Start working on the final boss's second form — basic attack animations

• Keep polishing Chapter 3's flow and mechanics

• Keep making prop models

A quick word on why we can't do regular small updates:

Some changes ripple backward. Say I fix a zombie pathfinding bug that happens under certain conditions. That fix might break something else — possibly in earlier chapters. If I had to fully retest everything after every single change, I'd never get any new content done.

Could players help test? Sure — but that takes time too. Collecting feedback, fixing issues, pushing patches, rinse and repeat. And there's always a chance that something we spent days fixing could become wasted later as new requirements come in.

On top of that, the project currently contains Chapter 3 assets. Shipping a build means leaking new content — which would ruin the experience when the full chapter drops. Stripping out new stuff for every test build? Too error-prone, too time-consuming.

So here's the reality: we need to finish the new content first, then focus entirely on testing. That's the fastest path forward. Hope that makes sense.

And why do finished things keep getting reworked?

Take automatic doors — they're everywhere in the scene.

1. Basic function: open when player approaches, close when player leaves. Done.

2. Then zombies got blocked outside, killing the combat flow. So we let zombies open doors too.

3. Then we wanted doors to trigger events — quest updates, cutscenes, spawning enemies. More changes.

4. Then zombies triggering events caused bugs. More fixes.

5. Then we needed locked doors that unlock via quests, computers, or buttons.

6. Then we wanted one-time-use doors to create choke points and puzzles.

7. Then save/load broke door states.

8. Then opening/closing doors messed up zombie pathfinding. Debug, fix, repeat.

9. …

Okay, I'm losing it.

But only for a minute. Because these problems have to be solved.

🥲