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

Allow to trigger patches from the game's folder #359

Open
lwcorp opened this issue Sep 25, 2021 · 1 comment
Open

Allow to trigger patches from the game's folder #359

lwcorp opened this issue Sep 25, 2021 · 1 comment

Comments

@lwcorp
Copy link

lwcorp commented Sep 25, 2021

Unlike cheats, which might be formatted differently for each emulator, patches are universal.

If someone has a folder like c:\games that only has NES files, then the current approach requires to duplicate its IPS files and put them in Nestopia's own IPS folder, meaning to keep each IPS file twice.

May you allow to just use IPS files that exist in the current game's own folder?

image

@rdanbrook
Copy link
Member

Actually the auto patch feature is a little weird, because you do need a similarly named patch file in the patches folder, I agree on that.

But there is actually a way to do what you want to do: just open the patch file instead of the rom. If there's a similarly named .nes file in the same directory, it will just apply the patch you loaded to that rom. So if you want to run patches from the same folder as the game is in, just load the patch instead of the rom.

There is another option too, you can just load any patch and if it doesn't find a matching rom it will prompt you to choose one to apply the patch to. You can also load a rom and then load a patch to apply that patch to the rom that's currently running.

I'm leaving this issue open because I do agree that the system is kind of awkward, but hopefully this helps you do what you want to do more easily.

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