Previously, the newly-inagurated team opted to use AliceOS — a framework for building rich experiences with Ren’Py. Sadly, due to a commitment for “less is more”, we’re trashing off AliceOS in favor of custom-implemented UI.
It was a nice touch for our Doki Doki Literature Club project — however as time went on, it became evident the same framework we rely on does not fit our creative parameters, and technically it was too redundant with errors.
AliceOS during Demo 1
When our project was in early stages, and we’re still deeply partnered with the author, Marquis Kurt, they opted in to code the mod with this framework. It was created specifically for Doki Doki : The Angel Returns but was open-sourced to be used by other people.
When it saw release with it on Demo 1, we were satisfied with the completeness, albeit missing some visually new UI.
But that’s about it.
“At first I didn’t care if we moved forward with it, but as time grew, it became creatively being too limited and didn’t really live to expectations.”
When the development progressed however, it became evident AliceOS was not keeping up with our needs for creative detail and attention for passive simplicity.
At first I didn’t care if we moved forward with it, but as time grew, it became creatively being too limited and didn’t really live to expectations.
Design-wise, I wanted a summer-like UI, with the blend of skeumorphism, moe, and minimalism. It was not possible with Marquis’s AliceOS. If we tried to style it, it would break immersion on one part of the framework. And I was irritated the extra design work for the Red Screen of Death.
I just wanted something simple to style in a design standpoint, however, AliceOS proved too limiting, so I pushed the team to remove it.
Other Reasons for AliceOS Deprecation
It was not just its limitations that pushed us to the edge with it, there was also creative conflict and miscommunication between the team.
“People started doing things beyond my knowledge, and that pushed me to the edge.”
When I left the Visual Novel team management for a while to focus on the Core work for the platform, people started doing things beyond my knowledge, and that pushed me to the edge.
The creative team, or so we call the Concepts team, was having conflicts and confusion — especially when sticking to a certain “pink box” shared story pipeline. I wasn’t consulted to that, so an emergency meeting was called to rectify this.
As the overall lead, there were this points I considered something was off on the development when I was idle:
- The Pink Box was actually a major story change — because it shares characteristics from two mods, DDEA and of course, The Angel Returns. None of this was raised to me to let me know what should be done next.
- A chapter of the story, which was undergoing a overhaul after feedback, was having too many limitaions — and that was caused by “Pink Box”. Since one of the characters has to stick to that behavior, it became evident the writers were having too locked-down insight for the character development of that character.
- Since we didn’t have any meetings, there were miscommunications regarding the roadmap, causing more inconsistencies.
Since the damage was done, there was a decision to throw the Pink Box out of the window because of its limited nature, and as veto’d by the creative. However, because it was too heated, two of the writers left, including the writer in question.
The other writer blamed himself for the departure of the other writer, and left as requested. He went back again after some time, apologizing for what happened.
“Over the course of the argument, It was evident I need to supervise them more closely and to set up a proper flow for major changes.”
After the emergency meeting, a major reorganization has to be done. This involved the following:
- AliceOS will be removed due to its limitations and redundancy.
- There is now a co-lead to assist me during major decisions.
- Every week, status reports will have to be done to make sure everyone does their jobs.
- If there’s a major change needs to be dealt, it has to be directly decided by me and the rest of the team.
It was clear over the course of the argument, it was evident I need to supervise them more closely and to set up a proper flow for changes — this paved a way for a more structured type of creative work, without sacrificing productivity and quality.
Overall, the deprecation of AliceOS not just frees us from limitations, but the argument surrounding the decision made some major changes for the team.
If you want to download Doki Doki: Endless Adventures, Go to our Releases page on GitHub. Happy Modding!