Ready to Release. Forced to Rebuild.
Dear supporters,
We have some difficult news to share with you today.
About a week ago, a new team member joined us as we prepared for the Steam release. We were setting up Syncthing to synchronize project files across our team's computers when a misconfiguration led to disaster: a sync command triggered a deletion process on our main project folder.
We noticed within 2-3 seconds and stopped it immediately. It wasn't fast enough. Nearly 2000 render files, all scene layouts, and animation assets for the final portion of Chapter 6 and the entirety of Chapter 7 were wiped out. Worse still, our backup system was connected to the same sync network—so the deletion cascaded across every device we had.
The game was 100% complete. We were just waiting on the final angle renders for a handful of animations. We were that close to the finish line when everything slipped through our fingers.
We tried everything to recover it.
We spent the past week throwing everything we had at this problem. Around $300 on professional data recovery software subscriptions. Dozens of different programs. Consultations with data recovery specialists. The answer was always the same: the TRIM system on M.2 NVMe SSDs wipes deleted data instantly and permanently.
Here's the part that really hurt: we "found" most of the files. But everything we recovered was just metadata. Thousands of files sitting there, looking intact, refusing to open. Corrupted headers. System errors. Unreadable content. Empty shells of what used to be months of work.
These are all the files we managed to recover. None of them work.
We lost the script files too, but by sheer luck, one of our testers had a copy and we were able to get it back. The menu design we'd been working on wasn't so lucky—we salvaged a few pieces, but most of it is gone. We're putting the menu on hold for now and channeling everything into content production.
Why this hits so hard.
We're asking for a moment of empathy here.
Dallas has been pouring himself into this project for months. He pushed through a period of illness, and the moment he recovered, he was right back at it. Sleepless nights. Relentless deadlines. Everything lined up to deliver this update on time. And then... one wrong click. A few seconds. An irreversible outcome.
Months of work vanished in seconds. After a week of desperate attempts to undo it, we had to accept that it's gone.
Where do we go from here?
Our morale took a serious hit, but our resolve hasn't wavered. This month, we're rebuilding Chapter 7 from the ground up—new renders, new animations, all of it. It's a massive workload, but we're committed to keeping the delay as short as possible.
We need you to believe us.
We still have the previews of the content we lost. This work existed. We weren't stringing you along—we've been working on this for months.
We know some of you won't believe us. And honestly? That's fair. When you see "files got deleted, update delayed" online every other day, why would you trust us?
But here's the thing: We could have stayed silent. We could have drip-fed you previews for months to buy time. We could have made vague promises like so many other developers do. We didn't. Because that's not how RWA Studios operates.
Our only promise is this: We will rebuild Chapter 7 from scratch, as fast as humanly possible, and prove ourselves through the work.
One last thing.
If you need to pause or cancel your subscription, we completely understand. No hard feelings, no guilt. You supported us when you could, and that already means the world.
For those who choose to stay—thank you. Not just for the financial support, but for believing in us when we're at our lowest. We won't forget it.
Either way, when Chapter 7 rises from the ashes, you'll be the first to see it.
— RWA Studios
Comments (19)
I feel like it could possibly happen, and I feel sorry about it, really hoped to play it, but to ensure it wont happen again I would say try uploading updates more frequently, not twice a year and then force a lot of content, the more content you put the riskier to recover, hopefully it can give you guys some new ideas and you guys learnt a lot from it
No 😭
All because of your carelessness and over confidence. Should have been released it earlier. You tried to make us dump. Now starting from scratch? Do wtf you like idiots 🤢🤢
lets gooooooooooooooooooooooooooooooo
Keep Going. Take your time. guys Good luck .
I can't even being to feel for you and your team. That has to be one of the worst things to happen. So sorry. Do what you need to! I can't imagine what that must have felt... Push forward!!
That sure sucks, so much work. Keep the chin up guys, lesson learned and in a year it will be a memory. Keep up your awesome work!
Chapter 7 should be called the Phoenix, Good luck guys take all the time you need, we are human after all, and when we hit the bottom of the well we must take the initiative and rise again. We will wait no matter how long will take you to build your project again. God speed 💪😉
Thanks for your hard work bro 💪
Thats gotta hurt like hell, the 1000s or even more hours you guys spend on this VN, damn.... It reminds me of what happened to the DEV that makes the vn "A Mothers love", his m2 drive died with ALL his work, 1000s of hours of work, more or less gone, though he was lucky to get some data out. I have to say those big USB extern harddrives for backup, I love em, saved my ass a few times, unless you forget to make regular backups. But good to know you guys didnt burn out bcs of this and just went "To hell with this project"...
Heart goes out to you guys. We all make mistakes. It's how we learn. Happy you guys are dedicated to rebuilding. Wish you guys all the best. Much love.
Heartbreaking to read, but your resolve is inspiring. Losing months of hard work in seconds is devastating, but the fact that you are already planning the rebuild shows exactly why you deserve support. Stay strong!
I don’t know what to say. As a programmer (ML/DL developer) I always pushed my code and source file on github. Then why not you and your team. Its also unbelievable that, you Couldn't be able to recover data.
We completely understand where you're coming from—and you're right about version control for code. Here's the thing: Our script files were recoverable. One of our testers had a copy, and we got those back. The real loss wasn't code—it was render files and animations. We're talking about thousands of high-resolution images and video files, gigabytes of 3D-rendered content. That's not something you push to GitHub. As for data recovery: M.2 NVMe SSDs use a system called TRIM, which permanently wipes deleted data almost instantly to maintain drive performance. This isn't like a traditional HDD where deleted files sit in recoverable sectors. We spent $300 on professional recovery software, consulted with data recovery specialists—the answer was the same everywhere. Once TRIM does its job, the data is gone. We found the files, but they were just empty shells. Metadata intact, content zeroed out. We wish it was as simple as git pull. It wasn't.
Do it fast
Google 3-2-1 data backup rule. This sound sketchy as hell to somehow work as a team but only have a single point of failure? Amateur hour. And to blame the new guy? Seriously? May as well say your dog ate the thumbdrive
We're not blaming the new team member. Let us clarify what actually happened. When setting up file sharing for our new teammate, we accidentally clicked "Receive" instead of "Send." Since their system had no files yet, Syncthing interpreted this as the "correct" state and began syncing our folders to match theirs—meaning it started deleting our files to create empty folders. We caught it within seconds, but the most recent files went first. As for backups: yes, we had them. But they were also connected to the same Syncthing network. When the sync command triggered, it cascaded across all connected devices—including our backups. The foundation was wiped, so the backups went with it. Was our backup architecture flawed? In hindsight, absolutely. We should have had offline backups completely disconnected from the sync system. That's on us, and we've learned an expensive lesson. But we're not here to make excuses. We're here to rebuild and deliver.
NTR update when? also put your games on steam. you have enough content in all 3 games to go early access. your games are high quality it will catch a lot of attention from steam and adult curators on steam.
Thank you for the kind words about our quality—that really means a lot, especially right now. Steam is definitely in our plans. Actually, the new team member who joined us was brought on specifically to help with Steam preparations. We were just about to roll up our sleeves and start that process when this happened. As for NTR: We're planning to release it as a DLC for the Steam version. So yes, it's coming—just not as part of the base game. Once we're back on track, Steam is next on the list. Thanks for the support and for sticking with us!
