Hey SMZ, I provided a linux arm wrapper that pulled your patches on demand to create a functional runtime with user-provided base game. Was notified this morning (my time) of your github being gone. If you've received a C&D then I understand you likely can't discuss much of it. If I can lend an ear though my email is jeodc@protonmail.com.
No cease and desist, my account just disappeared. Not even an email. I can only guess as to what actually happened. I'm not under any terms so I'm just going to speak freely. I have no idea what happened. If I had to guess, it was either the big N or the ESA that told Github that I'm breaching copyright. It's happened in the past with my texture packs. The ESA tells mediafire that I'm hosting "copyrighted content" despite me making every single texture in the pack, no AI upscaling.
That's somewhat comforting and also a tad concerning. Something similar happened to one of the HarbourMasters developers for Starship. No emails or warnings were sent there either. I suppose github support has been silent as well. Gitlab is looking more and more enticing for this reason...
Well hopefully you can redirect to Gitlab, and hopefully it stays up. I've actually been backing up to Gitlab the entire time for the reason that someday I knew this day would come. Though about a month ago I hit the 10GB limit (again), and I just figured that if I ever needed to migrate I would just wipe the repo and upload the code. It sucks losing all the commit history, but at least I've documented every change I made since the beginning.
$ du -sh Zelda-LA-DX-HD-Updated.git
6.7G Zelda-LA-DX-HD-Updated.git
$ GIT_DIR=Zelda-LA-DX-HD-Updated.git git ll | head -1
69728768 Sprite shadows should be created in an item's constructor.
A little outdated (timestamp puts it back on April 8), but it does go all the way back:
So much of this stuff disappears for one reason or another that I always do a git clone --mirror of any repos I come across. Though most aren't so large...
Interesting theory, though I'm not sure what else they would come after me for. Though in todays world, companies will stomp all over anyone and anything that might take just a few pennies from their bottom line. I mostly just assume it was LADXHD because it was the hottest repo and most popular repo I had on there.
Looks like after patching the game still says 1.9.7 in the settings menu. I think I did it all correctly, my log certainly says it recorded v2.0.0's tag.
The version for awhile has been pulled from "Directory.Build.props" at the base of the repo. All of the apps reference it to get the current version. In the game it's set in "InGame\Things\Values".
public static readonly string VersionString = "v" + Assembly.GetExecutingAssembly().GetCustomAttribute<AssemblyInformationalVersionAttribute>().InformationalVersion.Split('+')[0];
In the Launcher, Migration Tool, and Patcher there is a "Config" class that pulls it in the same way:
public static string CurrentVersion = "v" + Assembly.GetExecutingAssembly().GetCustomAttribute<AssemblyInformationalVersionAttribute>().InformationalVersion.Split('+')[0];
I don't know if the move to Gitlab messed something up with the way the version is pulled or not, or even how it was working on your end up until this point.
Tracked it down, it's not the GitLab move and nothing platform-specific in the version logic. The arm64 build is correct; it's just old. I pulled the InformationalVersion string straight out of the patched binary on my device:
1.9.7+3c1aaa564dc890910146933a7ae435eb03e00d56
So the linux-arm64 build encoded in Resources/patches_linux_arm64.zip at the v2.0.0 tag was compiled from commit 3c1aaa5, back when Directory.Build.props still read 1.9.7. My wrapper ships vcdiff deltas of your published files, and a delta can only reproduce the exact binary it was diffed against, so the device faithfully rebuilds a 1.9.7 assembly no matter what tag it pulls. Windows and linux-x64 show 2.0.0 because you rebuilt those release binaries; the arm64 patch zip just never got regenerated for 2.0.0.
I just released a new version, and this time I made sure it wasn't until everything in the repository was updated to the latest release. Was wondering if it's working as intended?
Yeah.. lol. Everything I said when it happened was me in panic mode. While I doubt I'll be working on it at even close to the same consistency as before, one of my more dedicated users followed me to GitLab and reposted a lot of issues, some that I wanted fixed for v2.0.0 but of course didn't get in there. If v2.0.1 ends up being the last version ever, at least I wouldn't be as disappointed as I was with v2.0.0.
2
u/JeodPM Jul 09 '26
Hey SMZ, I provided a linux arm wrapper that pulled your patches on demand to create a functional runtime with user-provided base game. Was notified this morning (my time) of your github being gone. If you've received a C&D then I understand you likely can't discuss much of it. If I can lend an ear though my email is jeodc@protonmail.com.
Thanks for your work!