• 7 Posts
  • 46 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle





  • I hate AIOs in general, but this isn’t as bad as some I’ve seen. Still got quite some issues though. You should clean up that contents folder.

    Lots of completely useless stuff there. For example 010000000001013 can actually cause problems during boot and doesn’t do anything. A lot of other random sysmodules that are unnecessary to 99% of users as well.

    Crap dnsmitm config that uses the 127.0.0.1 *nintendo* line, which is very general and uses more resources to filter. The rentry or nhguide’s dnsmitm configs are far better.

    Mission control is installed, but it’s BT patches are missing, so it’s not going to work.

    There’s a system settings file in config for some reason, but doesn’t appear to have any modifications.

    The Hekate ini has no way to boot syscfw for users that want it. (And uses cal0blank even though exosphere.ini already exists)














  • Yes, but make sure you have dns-mitm setup to block Nintendo servers. You can confirm this by booting into emummc, then checking the dnsmitm startup logs. A report will be generated in sd:/atmosphere/logs called dns_mitm_startup.log. Open this file in Notepad and confirm it looks something like this, where it has Nintendo domains redirected to 127.0.0.1:

    Also, NEVER launch the Tinfoil installer on sysCFW/sysNAND. I know it’s impossible to do in Stock because there is no HBMenu, but it is possible if you boot Atmosphere on Sys. Be careful not to do that, or else you will get banned.