The ACT module handles NNID accounts. This module behaves very similarly to the 🔗 Wii U implementation (nn::act)

These commands are common to both act:u and act:a

These commands are exclusive to act:a

This is the service used by regular applications.

Like the friends sysmodule, the ACT module supports multiple accounts internally, although this functionality is not exposed to the users. Unlike the Wii U which supports up to 12 accounts, the 3DS only has 8 account slots.

Some commands require require the account slot as an argument, which is 1-indexed. The value for using the current loaded account is 0xFE.

Data blocks can be accessed from specific commands depending on the data that is requested. These follow a similar order to the Wii U 🔗 ACTInfoTypes.

With each request, ACT-sysmodule specifies request-header “X-Nintendo-Device-Model”. This is the only *dedicated* request-header that’s contains anything Old3DS/New3DS specific. This was implemented with 9.0.0-X, and presumably 8.1.0-0_New3DS. The value is from a string initialized during ACT-sysmodule startup. The value-string is the codename string for all 5 of the model values from Cfg:GetSystemModel. When the output from GetSystemModel is >=5(switch statement default case), it runs this: “len = snprintf(outstr, outmaxsize, “3DS-%u”, model);”

ACT module uses a RootCertChain for all HTTPS requests, the only trusted root CA is default CertID 0x3.

Even though ACT-sysmodule uses ptm:s, it doesn’t use CheckNew3DS at all.

Category:Services