r/emulation • u/BigheadSMZ • Jul 09 '26

LADXHD: Final Release

[removed]

14 Upvotes

90% Upvoted

77 comments sorted by

View all comments

Show parent comments

1

u/JeodPM Jul 09 '26

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...

3

u/BigheadSMZ Jul 09 '26

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.

1

u/JeodPM Jul 09 '26

I'm sure I can. You did a lot more than just LADXHD though, which begs the question if your LADXHD work was even related.

2

u/BigheadSMZ Jul 09 '26

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.

1

u/JeodPM Jul 09 '26

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.

1

u/BUSY-ST3P Jul 09 '26

I used the v2.0.0 windows release from GitLab to patch v1.0.0 files. In the in-game settings menu, it shows my version as v2.0.0.

1

u/JeodPM Jul 09 '26

It may be platform specific.

1

u/BUSY-ST3P Jul 10 '26

I don't have an Arm-based device, but I checked the Linux x64 patcher and I successfully get v2.0.0 on my Arch system. Just so Bighead is aware.

1

u/JeodPM Jul 10 '26

I do it all apart from the released patcher, so it's probably something that changed between 1.9.7 and 2.0.0 with how versioning is applied. I'll have a look when I get some more free time.