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

[Feature]: Custom error messages to replace stock ones #38

Open
1 task done
ashquarky opened this issue Jul 13, 2024 · 0 comments
Open
1 task done

[Feature]: Custom error messages to replace stock ones #38

ashquarky opened this issue Jul 13, 2024 · 0 comments
Labels
awaiting-approval Topic has not been approved or denied feature A feature request

Comments

@ashquarky
Copy link
Member

Checked Existing

  • I have checked the repository for duplicate issues.

What feature do you want to see added?

Inkay could hook into erreula and replace various system errors with customized ones. The error code itself and the message are potential targets for replacement. Pretendo would need to provide a list of error codes, their replacements, and their messages, as well as translations into all of the Wii U system languages.
If Inkay is aware of errors occuring on the system, this could also potentially be used for analytics in the future to help us quantify error rates and in what games. This might have been useful during the great 101-0502 era. Plus, graphs.

Why do you want to have this feature?

Inform users of:

Any other details to share? (OPTIONAL)

Shutter has done some work on this in the past: https://github.com/PretendoNetwork/Inkay/pull/5/files#diff-34d21af3c614ea3cee120df276c9c4ae95053830d7f1d3deaf009a4625409ad2R393

We need to work on what the actual design of this would look like. libcurlwrapper from Aroma would make shutter's design more reasonable now than it was then, but it's still not super flexible to uses other than ban reason. I personally think something based on BOSS would be great, but it's unclear if BOSS can securely deliver personalized files (-> ban reasons!).

Either way, hardcoding errors into Inkay is almost certainly not the answer here, please don't just PR that! It should at least come from a JSON file, which we can then fetch over BOSS or curl or whatever solution we settle on.

@ashquarky ashquarky added awaiting-approval Topic has not been approved or denied feature A feature request labels Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-approval Topic has not been approved or denied feature A feature request
Projects
None yet
Development

No branches or pull requests

1 participant