n64: with homebrew header, don't default to install a controller pak#2382
Merged
LukeUsher merged 1 commit intoares-emulator:masterfrom Jan 19, 2026
Merged
n64: with homebrew header, don't default to install a controller pak#2382LukeUsher merged 1 commit intoares-emulator:masterfrom
LukeUsher merged 1 commit intoares-emulator:masterfrom
Conversation
When the homebrew header was first introduced, in its first limited spec, Ares defaulted to enable both rumble pak and controller pak: ares-emulator@bc8c308 Back at the time, there wasn't any way to specify that a controller pak was needed by the ROM, and Ares didn't even provide a GUI to install it. So basically this was the only way to allow a homebrew game to use the controller pak at all. Fast forward 4 years and now we have a GUI to select which pak to install on each controller, and the homebrew header allows to pre-install whatever you want into each port. In case the user doesn't specify a suggested controller configuration in the homebrew header, the default of using a controller pak has the annoying side effect of creating a useless .sav file next to any ROM. CPak is not very common in homebrew ROMs anyway, so enabling it by default now seems to create more hassle than it solves.
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the homebrew header was first introduced, in its first limited spec, Ares defaulted to enable both rumble pak and controller pak: bc8c308
Back at the time, there wasn't any way to specify that a controller pak was needed by the ROM, and Ares didn't even provide a GUI to install it. So basically this was the only way to allow a homebrew game to use the controller pak at all.
Fast forward 4 years and now we have a GUI to select which pak to install on each controller, and the homebrew header allows to pre-install whatever you want into each port.
In case the user doesn't specify a suggested controller configuration in the homebrew header, the default of using a controller pak has the annoying side effect of creating a useless .sav file next to any ROM. CPak is not very common in homebrew ROMs anyway, so enabling it by default now seems to create more hassle than it solves.