0.4 - More, more performance

Changelog

Virtual amiibo emulation

• emuiibo was updated to latest libnx and libstratosphere, what might fix possible bugs those had before. (libstratosphere's new IPC API is far more accurate now)

• Internal heap usage was decreased from 0x75000 to 0x10000. (~7 times less heap!)

• Several implementation mistakes were corrected, which might have caused issues.

• Those problems with certain amiibos (mainly BOTW ones) have been fixed, which were caused by a bad handling of amiibo IDs (N sends them in a slightly different way)

• Now emuiibo has a settings file: settings.json inside emuiibo's directory. The only setting it has for now is whether input combos are enabled, and this defaults to false (disabled by default).

• If you want to disable input combos, just edit the file and change the field comboEnabled from true to false, or the opposite to re-enable them.

• Added logging, so that most interactions are logged to a logging file (emuiibo.log) in emuiibo's directory, to help with potential issues.

Custom service (nfp:emu)

• API changed, some commands' implementation is slightly different now.

• Version now isn't 3 u32, it's a struct made of 4 u8s (major, minor micro and dev - whether it's a dev build).

emutool (emuGUIibo was renamed to emutool)

• Small corrections in texts.

Have fun with those amiibos which didn't work before :)

0.3.1 - emuGUIvolution!

Changelog

• emuGUIibo

  • Thanks to AcK77's contributions, emuGUIibo now looks way better than on its initial release!

• General

  • 9.0.0 support

Have fun with your custom amiibos!

0.3 - Bye bye, dumps!

Changelog

• Emuiibo has been fully rewritten, what involves several changes:

  • Amiibo moves should be faster now since on previous versions the amiibo dir would be re-scanned (thus iterated over every amiibo) each time user moved to the next amiibo.

  • Amiibo structure and filesystem layout have changed to a WAY more proper one. (see below)

• New amiibo structure - dumps no longer required!

  • The only relevant part of an amiibo is its unique ID (the rest can be emulated), thus having online databases of this IDs, dumps are useless, but still supported ;)

  • Amiibos go now inside /emuiibo/amiibo/ for a better directory layout. Don't worry about backwards compatibility. (see below)

  • Amiibos can be placed inside /emuiibo/amiibo// to be only used in that specific game. Amiibos outside those directories will be used on any game.

  • Backwards compatibility for any kind of amiibo, considering that 3 types exist: single dumps, 0.2.x format and the new 0.3+ format

• Say hello to a new tool to create virtual amiibos easily - emuGUIibo!

  • Made using Windows Forms, so should be supported by Mono

  • Accesses a full amiibo list from an online API, so the user just has to select an amiibo and customize it!

  • Amiibos are generated on the user-specified directory. If a drive with /emuiibo directory is detected, emuGUIibo will assume it's a console's SD card and default (but not force) that path.

• (Probably developer only) nfp:emu service changes:

  • Commands were renamed and reordered, so make sure you update your implementation.

  • Added new command to get emuiibo version by 3 integers (major.minor.micro)

0.2.1 - Small fix (8.1.0)

Changelog

• 8.1.0 support, working as always

• A new command was introduced in nfp:emu (RescanAmiibos)

0.2 - The emu-evolution!

Changelog

• Amiibo progress saving support

  • Games like SSBU allow saving their progress on amiibos. Now this is supported by redirecting savedata to files inside amiibo's "areas" directory.

  • This, in fact, provides another advantage, as real amiibos just allow savedata for one title, while this system allows to have multiple saves.

• Amiibo system changed

  • First of all, don't worry. All amiibo BIN files found in emuiibo dir will be auto-converted to the new system.

  • The new system has every amiibo in a different directory, which contains the amiibo ("amiibo.bin"), a JSON metadata file ("amiibo.json"), an "areas" directory (see above) and a mii char-info copy ("mii.dat").

  • On this system everything can be customized. In order to change miis you would need the char-info data, which is stored inside the console. To help with this, emuiibo will dump all console miis inside "miis" directory in emuiibo dir, named with the index + mii name (example: "0-XorTroll.dat"). To use it, copy to the amiibo dir and name it as "mii.dat".

  • An interesting option can be added to the JSON ("randomizeUuid" boolean), which makes emuiibo randomize the amiibo UUID. Having this means special circumstances in certain games, like being recognized as a different amiibo each time in BotW, hence infinite supply.

  • IMPORTANT! After using 0.2, since the old system gets changed to the new one, 0.1 won't find any amiibos as they're not on the root dir now. Thus, avoid using 0.1 after using 0.2.

• HOME button LED blink (7.x+, sadly)

  • On firmwares on 7.x or higher, performing a combo makes the HOME button blink, which is a simple and nice system to signal that a combo has been performed. Not supported on previous versions for technical limitations.

• nfp:emu service changed, with new commands

Also, a remainder that the next Goldleaf version (0.6) is going to have emuiibo support, featuring real amiibo dumping to emuiibo-style and more!

Initial beta release

This is the first release of emuiibo, still a beta.
Check the README for more details.