Hy everyone, I`m developing a homebrew app and want to know how to properly generate the TITLE ID for the package, acording to the standards and also avoid an existing title ID?
Im trying to make a fork of Emuiibo, but specific for Skylanders, so its an nsp + overlay.Are you trying to make an NSP package? AFAIK there's no point since other homebrew can easily create forwarders for NROs.

Post automatically merged:
Im trying to make a fork of Emuiibo, but specific for Skylanders, so its an nsp + overlay.
I think i'm very close to a beta release, but need to understand this TITLE ID standard, I want to publish in homebrew app store later on.
So, as I mentioned the project is based upon Emuiibo, and I can see emuiibo generates and exefs.nsp, so do my module.I think that nsp are not allowed in the app store... Most of them are generated with Nintendo keys.
The only geniuine nsp I know is the Atmosphere's hbl.nsp
Its not necessarly a fork, I`m just new to homebrew developemnt, and the module needs to interact with nfc, so I started by looking emuiibo code, its already working and a very decent state, does not affect or conflict with emuiibo module at all.my man wants to FORK an existing (and perfectly functioning) project and is already asking how to change the title id? we're in for a good one
I'm being pedantic, but installable nsp's (more specifically, nca's) can very well be made without the need of encrypting the data, thus not requiring keys.I think that nsp are not allowed in the app store... Most of them are generated with Nintendo keys.
The only geniuine nsp I know is the Atmosphere's hbl.nsp
Starting with 05 is the standard that forwarders have went with. You do not need to ship a forwarder however. Just ship the nro and have the user make their own forwarder should they wish.Hy everyone, I`m developing a homebrew app and want to know how to properly generate the TITLE ID for the package, acording to the standards and also avoid an existing title ID?
It's a fair question to ask imo. There is no documentation for homebrew tid stuff. Other scenes, such as the vita scene require you to pick your own ID, as well as the vpk's being installable. Being new to the switch scene, it's easy to assume that's what you need to do.my man wants to FORK an existing (and perfectly functioning) project and is already asking how to change the title id? we're in for a good one
This project is specifically for Skylanders, not Amiibos. Skylanders Imaginators is the only entry in the series on Switch, and notably the only one that functions without a portal by using the controller's NFC reader. This version also includes a digital library to store scanned figures, removing the need for a physical portal.emuiibo delivers two amiibo for Skylanders.
Are there any others?
If not, why bother?


Not even that, the HBL.nsp is not genuine signed but Atmosphere have a internal patch to allow run it without official signature.I think that nsp are not allowed in the app store... Most of them are generated with Nintendo keys.
The only geniuine nsp I know is the Atmosphere's hbl.nsp
I'm being pedantic again, but nsp's are not signed. An nsp is just a container, like a folder or a zip file without compression. It can contain anything you want.Not even that, the HBL.nsp is not genuine signed but Atmosphere have a internal patch to allow run it without official signature.
Nobody outside of Ninja Servers can generate a «Legitimate» signature, and ninjas charge you a lot of bucks for that.
as you need sigpatches to run any NSP on your console all of them are considerate piracy.

Exactly, there is no official signature.I'm being pedantic again, but nsp's are not signed. An nsp is just a container, like a folder or a zip file without compression. It can contain anything you want.
Its the nca's that are signed. The header is signed and the program nca has an additional signature (ACID). The nca is then hashed which is then stored inside the cnmt nca, as well as being used as the nca name.
hbl.nsp does not contain ncas. It just has main and the npdm iirc, which is what a program nca would contain.
Hi im a fellow switch homebrew developer working on a modern fork of triplayer, here's what we should know about title ID's. prefix 42000000 is refered to as the homebrew ID range then you add your choice of 8 hexadecimal characters. that prefix let's atmosphere know that this is not a game. So basically 42000000XXXXXXXX. Do your best to not make an ID that conflicts with other known modules. Mine will use 4200000000000FFE, Triplayer uses 4200000000000FFF.Hy everyone, I`m developing a homebrew app and want to know how to properly generate the TITLE ID for the package, acording to the standards and also avoid an existing title ID?
Atmosphere doesn't care about that. As long as it's not replacing currently existing program id, if you have boot2.flag in flags folder atmosphere will try to launch it at boot.that prefix let's atmosphere know that this is not a game