Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flatpak build generates as many patched versions of a game as there are patches to apply (IPS format) #54

Open
bitrot-alpha opened this issue Jan 4, 2023 · 1 comment

Comments

@bitrot-alpha
Copy link

bitrot-alpha commented Jan 4, 2023

Scenario: I download a pack of related patches (IPS format) for a game. Each one is like an ActionReplay code, it does one thing. I open Flips GUI and select the patches I want applied through the dialog box, then select ONE file for patching. The result: 3 different files are generated, each named like the patch name, and with different checksums for each.

Shouldn't the intended operation (for IPS format) be that several patches are applied to the game at once, and ONE file is generated as a result? Or is that not supported behavior?

I'm using Fedora 36 with the Flatpak build if that is relevant.

@bitrot-alpha bitrot-alpha changed the title Flatpak build generates as many patched versions of a game as there are patches to apply Flatpak build generates as many patched versions of a game as there are patches to apply (IPS format) Jan 4, 2023
@Alcaro
Copy link
Owner

Alcaro commented Jan 4, 2023

That is the behavior I intended to implement. It's intended for level design contests at SMW Central where you get dozens of patches, each representing a different ROM hack.

Whether that's the behavior anyone else expects is, of course, a different question. I agree a 'merge patches into the same ROM' button would be useful, but I'm not sure how to design the UI (I'd rather keep both options available, and I'm not sure how to represent it on command line), and I don't have the motivation to implement it either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants