As someone who's been right up in the guts of this thing, is fixing it easy enough, or would a ground up remake be more efficient?
Do you have any idea what exactly could be causing problems on the devs end? Or was seeing the insides just proof that they're just sitting on their arse?
Either way, good work and thanks for all this.
In it's current state being what's in D22-23, it's easy enough since a lot of the background stuff is done and just needs converting previous data over although most of it was already done too, the calendar data was the biggest outlier to me.
The way the calendar is built now is WAY better than it was (not talking about how progress is saved) before (Although it has bugs, if they read my code maybe they will see where I point something out
) and is why I think the replay & gallery system should be remade. I never really considered before at how the music UI is handled but that might actually be a fit-in-replacement for these systems with a little modification.
What do I think is causing them problems? Assuming it's not a scam, then I would put it down to two things - Scope & Willpower.
Scope - We've seen some images Bluecat has posted before in discord showing him working on stuff, I think it was a D4 script and it showed some modification to how things are handled, which in this case was patch related IIRC and streamlining how it worked that would make a shorter script but have the same substance. This is purely wasted effort that won't have a perceived difference to the end user or himself - you should only be going back to these to fix how things are saved (as I did) to make them compatible with the new approach.
The character profile system is another example of this. The old code worked fine but they broke it at some point but it didn't need redoing like it has been in D22-23. I might've mentioned this in a previous post before I released it, but at first the D22-23 character profile system didn't work for me either even after enabling it, so I initially just reverted back to the previous system in and looked at how it worked in Week 1 fixed it, so it displayed & saved things correctly. Only after I ran into issues later unrelated to this and having fixed the old system, I revisited the newer one and decided to put that back in since the fix applied to this system as well. There's a lot of dead code in the new system, almost like they were trying to work out why stuff wasn't saving...... (FYI for them... defaulting != defined in trying to save something).
Willpower would be the main cause though I'd bet. Putting wasted time on things that don't matter aside, you just need the will to work on something and see it through which Bluecat clearly had in the beginning and has now lost. Sure coding is different to creating images, but both required the willpower to see it through + someone else is supposed to be helping on the coding side anyway last I saw.
Oh, also it's easier to fix something than it is to restart from scratch but it does have it's downsides in that you don't know exactly how everything comes together when it's not your code so it can slow you down at times. Starting from scratch would be a good excuse to delete it's UI though (I really do not like it, it's so wasteful in space).
I literally just realized this now, despite myself writing some commented out lines on certain things while I was doing this but this actually had no code documentation in it at all. Who TF coded this again? I'm actually pissed now since I've realized this because this is standard code practice LOL. They might not of broken their own features if they had documented it, who knows.
Damn wall of text again too. GG
