while(true){💩};

  • 1 Post
  • 339 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle




  • I don’t like flatpaks or snaps or anything like it either, but I think they help a lot in situations like the Steam Deck or PinePhone where you want the base to be able to move slowly and be stable, while letting the apps on top move quickly.

    The problems with flatpaks and similar is that it allows and even encourages developers to stick with horrendously outdated libraries, and your system is only as safe as the container’s isolation defenses.

    They also make it more difficult to go in and directly modify or tweak the program as the user.

    And many developers are no longer offering bare-metal options.












  • So, I have a hacked switch 1 and I can assure you that any game that has had a “complete overhaul post launch” still uses about 80% of the data on the cartridge. Or rather, it loads the entirety of the cartridge, and then every update to the game after that gets strapped on top of it to overwrite whichever sections of the game it needs to or adds new stuff.

    So let’s take animal crossing for example. If there were 2 major updates for Animal Crossing, youd have something akin to the following list of files:

    • Animal Crossing New Horizons.nsc [8 GiB] (the cartridge itself, if you dumped it - in this case we’re referring to the actual cart itself here though)

    • base.nsp [16 B] (some kind of token file for DLC attach points or something)

    • 184810dheincoiepn02.nsp [300 MiB] (patch 1)

    • 01849...ahd4819.nsp [24 MiB] (patch 2)

    The switch loads the entirety of the cartridge, then it loads the base patch over the top of it to hook into the right location, then it loads patch 1 over the top of that, then it loads patch 2 over the top of patch 1, base, and the cartridge. Theoretically you could delete the latest update file and still have a working downgraded game. No original data is lost.