1.5 Teaser (pledge reward)
Added 2025-05-07 02:04:41 +0000 UTCHi everyone!
Just wanted to give you a quick update! I'm working hard on the next update, but as I've mentioned before it's gonna take a while! I'm working to replace a LOT of the old images with the newer style and I think they look a lot better. You also may notice a couple new faces peeking through the cracks.
I'm hoping to have the update ready sometime in August, but it should be a doozy! I have already gotten a working replay system and plan to touch almost every part of the game before releasing it.
Thank you all for your patience!
Comments
Hey! Just seeing this. I really appreciate the feedback and advice. I'm not refactoring any of my code. Frankly Deight Class is super simple from a software side of things. Frankly of all of the time that I've put in, the software has probably been only a few percent of it. Most of the time goes into writing and generation of the images. I'm not sure how many people are aware of this, but I'm actually formerly a professional developer, so I'm definitely aware of the pitfalls you're talking about. As for redoing the images, that's something I went back and forth on. Ultimately the new AI is so much better that I feel great about redoing some of the old scenes. And I'm most of the way done doing so already. I believe I can do all of this while finishing the story of Deight Class. So hopefully you'll be happy to see the outcome!
Lucy
2025-06-24 02:50:38 +0000 UTCI know this is a post from a month ago, though as a fan and a developer/manager of software projects, I wanted to share my two cents: I'd strongly recommend resisting the urge to refactor/improve existing code and images for a project like this, and instead focus on finishing the story. I've seen a lot of projects in the working world and in this indy gamdev community go down a rabbit hole refactor then never finish. As a developer it's super tempting to clean up code that is obviously hacky, and certainly it gets hard to work on a project with tech debt. That said, there's a reason refactors take teams and years at medium/big companies. My recommendation is to just finish the story of the current project, then use your experience to shape the code architecture of your next Greenfield project. And to just find a quicker story endpoint to the Current project if it gets to a point you struggle to work on it. It takes a ton of effort and skill and time to refactor, with no observable benefit to the users, and meanwhile you likely end up with a broken state until the refactor is complete, making it hard to add new content to the refactored branch.
mushufasa
2025-06-18 15:31:54 +0000 UTC
