Okay, this may be unorthodox, maybe even impossible.
But know little about coding, let alone how homebrew programs work.
But I'm crazy and think outside the box.
I really don't think this is possible, but like I said, I won't know unless someone tells me.
-------------------------
I got this idea from combining HANS…
…and NTRDebugger real-time debugging.
-------------------------
So, there's a config file, let's say, like the attached file…
Yeah I suggested something like this before, but hold on.
When you boot it from homebrew, you choose which name you want to load the mii information from (left of
Then it remembers the HEX to the right of the : for that name, and boots into a slightly modified version of Mii Maker romf.
Then choose to make a QR from any Mii that Mii Maker would normally accept, and the EnQRypt Mii feeds Mii Maker's QR generator the selected HEX code in place of the selected Mii's Data.
Now, I don't know if the first three bytes are used by the QR builder, if they are, the override starts on the forth byte. (I've seen the fourth byte as 0x10, or 0x30.)
Why not include the first three bytes?
First byte is 0x03, always. second byte, as far as I know is always 0x00, but I haven't filled Mii Maker, at all. and the third byte is placement in the Mii Maker grid.
-------------------------
And… yeah… basically, [tricking Mii Maker into QR-ing abnormal Miis. All the Miis in the sample file are official special Miis I StreetPassed.]
But know little about coding, let alone how homebrew programs work.
But I'm crazy and think outside the box.
I really don't think this is possible, but like I said, I won't know unless someone tells me.
-------------------------
I got this idea from combining HANS…
…and NTRDebugger real-time debugging.
-------------------------
So, there's a config file, let's say, like the attached file…
Yeah I suggested something like this before, but hold on.
When you boot it from homebrew, you choose which name you want to load the mii information from (left of
Then it remembers the HEX to the right of the : for that name, and boots into a slightly modified version of Mii Maker romf.
Then choose to make a QR from any Mii that Mii Maker would normally accept, and the EnQRypt Mii feeds Mii Maker's QR generator the selected HEX code in place of the selected Mii's Data.
Now, I don't know if the first three bytes are used by the QR builder, if they are, the override starts on the forth byte. (I've seen the fourth byte as 0x10, or 0x30.)
Why not include the first three bytes?
First byte is 0x03, always. second byte, as far as I know is always 0x00, but I haven't filled Mii Maker, at all. and the third byte is placement in the Mii Maker grid.
-------------------------
And… yeah… basically, [tricking Mii Maker into QR-ing abnormal Miis. All the Miis in the sample file are official special Miis I StreetPassed.]
Attachments
Last edited by that girl,
, Reason: Finishing the post.