[Bug]: Custom banned error codes are bugged on Nintendo 3DS.

[piplupness]

Checked Existing

• I have checked the repository for duplicate issues.

What happened?

Currently, banned error codes on 3DS are not displaying correctly. If the error code message is too long (one of the many causes is the ban reason being long enough), the message will not be visible in its entirety, there is no option to scroll.

Official 003-xxxx Nintendo error codes, can be scrolled on 3DS, for example.

What did you expect to happen?

Error codes 598-0010 and 598-0011 being scrollable if too long.

Steps to reproduce?

This assume your account is banned from Juxtaposition for breaking the Juxt Code of Conduct.

1. Open Miiverse (assumes Nimbus is loaded on Pretendo and the PNID is already set up)
2. Error code 598-0010 or 598-0011 (not really for the second code, 015-5007 can appear due to another bug!) appears.

Other relevant information. (OPTIONAL)

This user appealed their ban on Discord. Link to the thread here: https://discord.com/channels/408718485913468928/1320059674334335017

Ban message on 3DS:

Part of the message is cut, they realised only 5 minutes this was a ban since the initial "[PNID] has been banned until:" has been cut.

@jonbarrow already claimed this can't be fixed, but filing the issue anyway as some error codes are officially scrollable.

[jonbarrow]

Like I said on Discord, this is out of our control. If the 3DS decides to not scroll these then they just don't scroll. It doesn't matter if official errors scroll or not

If you actually check the code here you'll see that the way these errors are created is by using the cave API provided by the Miiverse browser. This is limited to only 2 functions

juxtaposition-ui/src/webfiles/ctr/js/debug.js

Lines 102 to 112 in 6009dfd

	error_callErrorViewer: function (errorCode) {
	const fakeMessage = 'Message for error code ' + errorCode;
	alert(errorCode + '\n\n' + fakeMessage);
	},
	/**
	* Calls system error viewer with specified error code and message
	* @param errorCode
	*/
	error_callFreeErrorViewer: function (errorCode, message) {
	alert(errorCode + '\n\n' + message);
	},

• error_callErrorViewer - Only takes in an error code, no message
• error_callFreeErrorViewer - Takes in both an error code and a custom message

This is the extent of the control that we have over how errors are rendered without making a custom error dialog ourselves from scratch. All we can do is give the cave API an error code and, optionally, a message. The console then just does what it does with this

So unless there's some jank under the hood which tells the console if a message should scroll based on the contents of the message, or by something in the error code, if the 3DS doesn't scroll the message then it just doesn't scroll the message