In #88 the profanity endpoint got updated to support wregion, though in an incomplete way. I have now finished documenting how this field works and how it affects the response data. I tested against both NAS and NASC and confirmed the same results happen on both, so this documentation should be enough https://nintendo.wiki/wiki/Online/Nintendo_Network/NASC#/pr
wregion determines which regions profanity lists to use. On the Wii U, 3DS, and Switch this is called "NgWord", which is made up of several lists of a bunch of regexes/blacklisted/whitelisted words, which each list belonging to one or more regions and languages. I'm not sure what this is called on the Wii/DS, but I did confirm that it's the same system being used since the "test patterns" (badwordj, badworde, etc.) work here, but it's an older version of the system since not all words from current NgWord (even from the 3DS) work on NAS
I would have PRed this in myself, but I lack the Wii/DS word filters and I didn't see any way to do this in this current NAS implementation as it seems to just use one master list
In #88 the profanity endpoint got updated to support
wregion, though in an incomplete way. I have now finished documenting how this field works and how it affects the response data. I tested against both NAS and NASC and confirmed the same results happen on both, so this documentation should be enough https://nintendo.wiki/wiki/Online/Nintendo_Network/NASC#/prwregiondetermines which regions profanity lists to use. On the Wii U, 3DS, and Switch this is called "NgWord", which is made up of several lists of a bunch of regexes/blacklisted/whitelisted words, which each list belonging to one or more regions and languages. I'm not sure what this is called on the Wii/DS, but I did confirm that it's the same system being used since the "test patterns" (badwordj,badworde, etc.) work here, but it's an older version of the system since not all words from current NgWord (even from the 3DS) work on NASI would have PRed this in myself, but I lack the Wii/DS word filters and I didn't see any way to do this in this current NAS implementation as it seems to just use one master list