Project Corruption, Refusing To Give Up, And Moving Forward (Patreon)
Content
Hello everyone! First of all, sorry that things have been so quiet this month. I promised that the first preview build of A Tiny Furry In A Huge World v1.4 would be out at the beginning of this month. The short version is that I haven’t been taking time off or abandoning the game… I’ve been working. A lot, actually.
Unfortunately, none of that work has been particularly exciting about, and for a while I was genuinely unsure of what to say… I kept thinking that if I just gave it another day or two, I’d solve the problem, get v1.4 out of the door, and this whole thing wouldn’t be an issue. The days have kept creeping and creeping though… because like I said, I’ve been dealing with a problem that has consumed a ridiculous amount of time and energy this month: project corruption.
Last month I ended up delaying the game for a few days because of this. I thought I was past it because I had a backup, but the issue is, whenever I transplant the content into the game, save it, and then reopen it, the project file is like, completely corrupt. This happens consistently… I should know, because I tried copying it all in there, like, five times at the beginning of this month.
So naturally this is a bit of a problem…
I am not sure why this happening. Unfortunately I am neither no expert on examining corrupted data, nor do I know anyone who is. So the best that I can do is hypothesize here. In my opinion there are three potential theories:
- There was something wrong with the new rooms that I was trying to create. This one was very easy to test: more on this later.
- Upgrading to the latest version of Quest (there was an update late last year/early this year, or somewhere around there) was a mistake and something somewhere along the lines has been messed up by doing this.
- The game is simply too big. Too many rooms, too many objects, too many things going on. Pretty much since 2022 the game has been giving me a warning on export, so this would make sense.
The first theory, as I said, was easy to test out: take the code blocks, put them in a different project, save that project, see if it corrupts. I did this: created a new project, copied in the code blocks, saved it. No corruption. So we can rule out the additions that I’m attempting to make to the game as a problem, or… we can mostly rule them out, at least. There is still a slight and circumstantial chance that it interacts with the existing project in a bad way, but if the exact same code behaves normally in a fresh project, then we can rule out the code being fundamentally broken at the very least.
So, that leaves us with two other theories.
The second theory is the most frustrating because it is the hardest to prove. I updated Quest without really giving it much thought. In hindsight, that was probably a mistake. It is entirely possible that some change introduced by the newer version altered how projects are saved or loaded, exposing a flaw that had previously remained dormant.
However, it is the third theory that is the most plausible to me anyway.
The game has been in development for years. It has accumulated hundreds of rooms, thousands of lines of code, and countless objects, exits, scripts and interactions. Since 2022, Quest has been warning me that the game is becoming large. At the time, I treated this warning as something to keep an eye on rather than an immediate concern… the game still worked, after all. But perhaps those warnings were an indication that I was gradually approaching the practical limits of what Quest was designed to handle.
If this is the case, then the corruption may not have been caused by any one thing tha I did wrong. It may simply be the result of pushing the engine beyond the scale for which it was originally intended. Nothing dramatic, no single catastrophic mistake… just years of additions slowly increasing complexity until something gave way.
I wish I had a more definitive answer for why this is happening than this. The best I can do is make observations and educated guesses, however. Based on those, I can say that the new code is not the culprit. Beyond that, though… either the newer version of Quest introduced an incompatibility somewhere along the line, or the sheer size of the project eventually caught up with itself.
But theorycrafting doesn’t really matter. How do we fix this?
I guess the first question is whether we can, or, should. A Tiny Furry In A Huge World is four years old, stuffed with content, and I am actively making efforts to develop a different game, so this would work out as a convenient excuse to shutter the whole thing and move my focus onto different projects.
Being completely honest, I did consider it… there is a certain logic to walking away, right? The game has exceeded every expectation that I ever had for it. What started as a small project that I did on a whim has spiraled into something larger than I initially intended it to become. A dedicated community, an absurd amount of content, literal years of work. By the most reasonable definitions, I could call it finished and move on.
The more I thought about it, though, the more I realized that I wasn’t really ready to let it go… I love the game. I have ideas for it. Every time I considered ending development, I became incredibly sad and despondent, which is part of the reason why I’ve been quiet for the first half of the month… part of me was thinking that I would have to come here and announce that the whole thing was canceled, or that development was finished, which is kinda miserable and also isn’t a great look for me given that I promised a v1.4 in the first place.
Beyond that, though… I have invested almost seven years of my life into this project. Thousands upon thousands of hours of writing, coding, testing, adding content for the love of the game. The idea of letting a corrupted project file be the thing that finally kills it just doesn’t sit right with me… if I’m going to end the development of A Tiny Furry In A Huge World then I want that to be my decision.
So, after a whole lot of thought, I’ve made up my mind. I’m gonna fix it. Or, in this case, rebuild it I guess.
Before anyone panics, no, this is not going to lead to some huge months long setback. I’ve been working on it all week and I’d say I’m about 30, maybe 40 percent of the way through it. It will be done before the end of the month. It is a case of moving existing things from one place to another. Many, many existing things, but this isn’t going to be a difficult process, merely a time-consuming and mostly tedious one…
I’m not completely happy about it, and I wish there was a quicker fix. I would much rather be making new content for v1.4 than reconstructing the foundations beneath it. Creating a fresh Quest project, moving over the existing rooms, scripts, objects, systems, testing as I go, it is definitely not work that I relish, but there is an upside to it… which is that, by the end of it, I’ll have a project file that I can actually trust again.
There are also many benefits to doing this… for example, if I’m facing corruption because of a project file that’s too large, then there are lots of things that can be removed from the game entirely. I’m not talking actual content, I’m talking test rooms that have been buried in there for years, clean up sections that have become messy, and generally just leave things in a better state than they were. This means that the likelihood of this happening again will be significantly lower, or… that is the hope.
That’s the other thing… I am not even sure if this is going to work! I have a very good feeling that it will - I am highly, highly optimistic that cleaning things up in a new project file will solve the issues that I’m having - but there’s a chance, albeit slim, that things will reach critical mass again and just kinda… explode.
But! I have to at least try. And if it doesn’t work? Well, I’m stubborn as shit and will just try something else. I will not stop until my game is working, because I love my game, and it is important to me. It’s really as simple as that.
I will be much more active for the remainder of the month - I gotsa bunch stories I wanna post up here, after all - and I will be sure to keep everyone posted. All going well, though, I should be posting up v1.4 at the end of the month… and, like I said, despite this corruption-related detour, I have been working this month even if I have been quiet publicly.
Proof of that will be coming in just a few hours. Yes, yes, I have a story all queued up and ready to post, and you’ll be able to feast on it soon. I have a few more planned for this month, too!
Apologies once again for all the issues. If you’ve scrolled all the way down this post without reading it - I understand, it’s quite long - then the too long didn’t read of it all is that I am still tangling with the project corruption issues from last month, but I have a solution in mind that is very viable and it should be fixed by the end of the month. From there, finally, we’ll be back to smooth sailing...
It’s annoying to have so much creative energy only to get persistently bogged down by outside issues, but I am not going to let it hamper me. By the end of this month, I’ll have a nice clean project file, I’ll be moved into a new apartment, and, all going well, the majority of the drama that this year has thrown at my feet will be behind me. I am looking forward to being able to settle properly and get back to doing what I do best: following the move, I’d like to get back to being consistent, if nothing more than for the sake of my mental health.
I’ll be back in a few hours with a story. Tune in then!