Virtual amiibo (amiibo emulation) system for Nintendo Switch, no longer requiring dumps 🙂
- Download the latest release and place it on your CFW's titles folder (so it would be like <cfw>/titles/0100000000000352).
- According to tests, should work on any CFW which allows NSP sysmodules (Atmosphere, ReiNX).
- You also have to set the boot2 flag, whose location depends on the CFW:
- Atmosphere: create a file named boot2.flag inside titles/0100000000000352/flags directory.
- ReiNX: create a file named boot2.flag inside titles/0100000000000352 directory.
All the input combos are performed with R-Stick pressing and pressing the D-pad in an specific direction (at the same time). Combos must (should) be done before or after the game starts looking for amiibos.
- Toggle amiibo emulation: Press R-Stick (like it was a button) and also pressing the D-pad up. Toggles/untoggles emulation.
- Toggle amiibo emulation once: Same as above, but pressing the D-pad right. Toggles emulation once, after emulating an amiibo then it will untoggle automatically.
- Untoggle amiibo emulation: Same as above, but pressing the D-pad down. Untoggles amiibo emulation, and should be used as a way to fully ensure it is untoggled, in case you don't know whether it's toggled or not.
- Swap amiibo: Same as above, but pressing the D-pad left. Moves to the next amiibo in the amiibo directory, if last one starts again with the first one. Only has effect if amiibo emulation is toggled.
Emuiibo's amiibo directory is sd:/emuiibo. Place your amiibo dumps (must be *.bin files) there.
Emuiibo no longer requires dumps to emulate amiibos. Instead, you can use emuGUIibo PC tool in order to generate virtual amiibos.
How do virtual amiibos work?
Virtual amiibos consist on a folder containing several JSON files.
A virtual amiibo, in order to be recognised as valid, must contain valid tag.json, register.json, common.json and model.json files. This file names were chosen according to the way the console processes amiibos, which are splitted into 4 processed data blocks (TagInfo, ModelInfo, CommonInfo and RegisterInfo).
The only relevant part of an amiibo, which identifies the type of amiibo, is the amiibo ID. Every other parameter can be emulated or isn't that relevant. The NFC UUID, present on amiibo NFC dumps, is randomly generated with virtual amiibos, since it isn't something important whatsoever.
Miis can be an issue when attempting to make emuiibo user-friendly. Since mii format is a 88-byte data block named "CharInfo" and we have no way to see char-infos rendered but in the console itself, there is no simple way to change the mii.
If (with emuiibo activated!) the title responds with an error similar to "No controller which supports NFC was found" probably means that emuiibo failed to supply the amiibo (wrong amiibo, internal error...). That error is displayed due to limitations with real NFC error codes.
All the persons who contributed to the nfp-mitm project before me: Subv, ogniK, averne, spx01, SciresM
libstratosphere libraries (SciresM again)
Que novedades incluye la versión 0.6
- Support for latest Atmosphere (0.14.4), and next releases unless breaking changes are introduced
- emuiibo no longer handles conversion of raw amiibo dumps or old emuiibo formats - only the current format is supported (the one used since 0.5.x)
- Heap size has been considerably reduced (last version used 0x40000, current one only uses 0x4000!) - in addition, the exefs NSP's size has been reduced too, being now 5 times smaller than 0.5.x
- Regarding the known issues with time services and sysmodules, emuiibo no longer makes use of this service to avoid creating more issues, even though this implies that virtual amiibos' "last write date" won't be set when a virtual amiibo is modified - luckily, not emulating this anymore doesn't change anything relevant nor break anything
- emuiibo's IPC interface other processes may use to communicate with it has a minor change - thus, 0.5.x or older overlays WON'T WORK with this version's emuiibo!