shibagani48

Weekly report Apr 2/4, 2025

Added 2025-04-14 16:33:56 +0000 UTC

Hello everyone!
Thank you as always for your support.
Let's take a look at this week's progress!

Demo Update

download it from here. The new password is "S4sWHWmX85ZPVuf".

Hellish Recovery Work

Immediately after the data loss, I died and was reborn. The universe is a singular entity, and all life forms are merely fleeting remnants from a galactic perspective.
Yes, the truth has always been right beside me—so close that I failed to notice it. By casting my consciousness to the sky, I can transcend the limitations of the physical body and continuously elevate the maximum amount of happiness.

Having lost touch with reality, I went alone to a miniature pig café and was crushed under the weight of pigs.

No matter how much I lament, I am the only one who can rebuild. Time will simply pass if I look away.
The first thing I tried was checking whether any remnants of the lost data remained on Git. I inspected the most recent stash using Git Bash, but unfortunately, it was dated two months ago.
Apparently, no data remained on Git either. So the next thing I tried was…

Use of AI

Talking about AI tends to provoke extreme reactions from many people and usually results in unwanted consequences for me.
Therefore, I will refrain from mentioning AI for a while.
For those at Abyss tier or above, I’ve created a separate article about this topic. If you're not comfortable with AI, please avoid reading it.

Continued Recovery Work

The only surviving version of the latest development state is the build data released in March. I considered whether I could use this to recover the lost data.
After doing some research, I discovered the technique of decompilation. I wondered: can someone like me really do something so hacker-like? Is it even ethical?
At this point, I had no choice but to try everything.
Decompilation is like black magic—something that isn't really recommended. For that reason, I will omit the specifics.
Please understand that this was an emergency, and I had no other choice. Since it's my own project, let’s overlook it just this once.

The result… was a huge success. While I couldn't recover everything perfectly—messages and variable names I had inserted as memos were all wiped—the overall structure was still in my head, so it wasn’t a major problem.
I was so overjoyed that I screamed and danced wildly. My neighbors were likely terrified.
The most time-consuming and complex parts were fully restored. Out of the 2.5 months of progress, I recovered about 2.2 months.
Although I couldn’t recover Unity-specific settings, I was able to reconstruct the framework necessary to reference the data structure.
With that as a base, and by using the development data from January (which is fully intact), it looks like I can restore everything in a short time!

I quickly revived the frame display system. I compared the new and old data and made steady manual adjustments.
Feeling relieved and getting overconfident, I soon made another mistake.

A Series of Major Mistakes

To make sure I never lose data again, I decided to move my project folder to Google Drive for backup.
Then—on top of that—I thought it would be a good idea to update Unity to the latest version.
This led to a cascade of unexpected problems.

For some reason, I could no longer drag and drop data in Unity. I had no idea why, and wasted a lot of time.
The root cause I finally discovered: placing a Unity project inside Google Drive breaks all folders, making file movement impossible.
Due to syncing behavior on Drive's side, folders become locked. I had to move the project back to local storage, delete and recreate all folders manually.
I had completely forgotten, but I think I ran into the same issue in the past. It’s probably mentioned in an old report.
Now I understand why I never put my project folder on Google Drive before…

Also, updating Unity corrupted my background data. The ground textures became horribly stretched.
Apparently, this is a Unity bug where tiling settings for certain material types get disabled. I fixed it by switching to a similar-looking material.

But the mistakes didn’t end there. For some reason, I thought this was a good time to reorganize action categories.
As a result, all action references broke, and I had to re-enter everything manually. I’d really like to punch my past self.

I also noticed that Zudrada's draw animation lacked smoke for draw situations, so I overwrote the sprite sheet to add the effect—which then broke several animation data.
In addition to the recovery work, I ended up spending a lot of time cleaning up mistakes I caused myself.

Recovery Complete

Despite all the twists and turns, the cut-in illustrations remained safe, and I still remembered how to make shaders to some extent, so I restored most of them quickly.

Using that knowledge, I created a shader for a burn status effect that I had long wanted to implement. Once I add a pillar of fire effect later, it'll look even more impressive.

I also implemented clash handling. Now a 5A attack can interrupt Zudrada's super.
Although handling round transitions took more time than expected, I’ve managed to get it working decently. if you beat the opponent on same time hit, a "crush" massage will appear.

I sincerely apologize for causing so much worry this time.
But somehow, I managed to recover everything within a week.
Since I rushed to apply so many fixes, I expect there are still some minor bugs. I would really appreciate your help in debugging if you spot any issues!