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

Seperate contents folder for SysNAND and EmuNAND #2364

Open
souldbminersmwc opened this issue Jul 27, 2024 · 1 comment
Open

Seperate contents folder for SysNAND and EmuNAND #2364

souldbminersmwc opened this issue Jul 27, 2024 · 1 comment

Comments

@souldbminersmwc
Copy link

Feature Request

[ If any section does not apply, replace its contents with "N/A". ]

[ If you do not have the information needed for a section, replace its contents with "Unknown". ]

[ Lines between [ ] (square brackets) are to be removed before posting. ]

[ Please search for existing feature requests before you make your own request. ]

[ Duplicate requests will be marked as such and you will be referred to the original request. ]

What feature are you suggesting?

Overview:

You could configure a contents folder only used for Sysnand / Emunand to avoid bans with larger mods, while still having access to online safe mods on your SysNAND

Nature of Request:

[ Remove all that do not apply to your request. ]

  • Addition
    Adding 2 contents folders

What component do you feel this would best fit within?

Why would this feature be useful?

This would allow easy mod management between both NANDs and reduce ban risk.

@zemixe
Copy link

zemixe commented Jul 27, 2024

Duplicate of #704 and #870

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