KAGARIBI · published
I wasn't a good daughter, so I couldn't say the words. To embrace the memories of those choices I couldn't make, I challenged myself to develop this game.
Mandatory auto-saves now trigger at the beginning and transition of every chapter (from Prologue to Chapter 4). This ensures that even in the event of an unexpected freeze or interruption, you can resume immediately from the start of the most recent chapter.
We have thoroughly reinforced the resetting of internal flags (such as isTransitioning) at the start of the scene. This resolves the issue where the screen would remain black and unresponsive.
We have eliminated the duplication of DOM elements (UI components) that occurred when switching between characters like "Kagari" and "Homura." This prevents memory leaks and input conflicts.
Save data now displays identification badges: "🔥 Kagari" or "🔥 Ember."
You can now identify which character's route is saved at a single glance.
The "A Path of Fate Has Closed" notification, which appears upon failing certain choices, has been corrected to display properly according to your language settings.
As a 56-year-old indie developer, I have been building the world of "KAGARIBI" one step at a time. While I may at times be clumsy in my technical execution and cause you inconvenience, I am committed to facing every error with sincerity to deliver the ultimate narrative experience.