MasterObserver

It's the combination of a connectivity issue with NM's servers and poor coding. Examining the crash dump reveals that the error occuring is a pointer referencing a NULL object. The object in question is part of an API used in FOMM to login to NM. The method of the object being executed: WebsiteAPIs.NexusAPI.get_LoginKey()is failing, and thus the object that should be returned after successful execution is not. This is poor error handling on the developer's part, plain and simple. ALL object oriented programming languages have the capacity to catch exceptions and deal with them appropriately. Turning the options off is a workaround but it shouldn't be necessary; A patch should be released. The application's inability to connect to NM's servers is another issue entirely though; At least NMM traps the error appropriately. From my experience, the inability to connect to their servers is a natural DoS. NMM even says so upon attempting login, essentially: "Could not reach blah blah server." I've had maybe 2 successful logins in NMM, all other attempts failed thanks to server issues. Whether it's a server capacitance issue or a ploy by NM to get users to buy access to their premium servers matters not. PROBLEM SOLVED... well, at least accurately identified. :pirate: