AL12

Thank you very much for this write up, really appreciate these reports and updates, it shows of your openness to the community.

In response to post #67632606. #67634316, #67634966, #67636786, #67637301, #67650701 are all replies on the same post. We do a lot of trickery to get around the api limit. Like using a single call to get list of mods that have been modified in the last moth and cross referencing those with your modlst. Another thing is that all mods with the same nexus mod id (so patches, duplicated mods etc) will only be checked once. But your setup seems like it would be a really great stress test for the dev build, to determine if indeed the limits are too harsh, and if we can improve things on our end. We did for example add an option to updateCheck a single mod (right click menu). Here is the link to the discord server with the dev builds: https://discord.gg/6GKR9jZ

In response to post #67632416. #67634251, #67635721, #67635836, #67636566, #67637641, #67638186 are all replies on the same post. Really Nexus will not know anything you are not sending yourself. And all you are sending is the header Kerber showed you before, and that really is basic information that is actually useful to debug problems.

In response to post #67632606. #67634316 is also a reply to the same post. The new API features an account based limit of 2500 daily requests, after which you get an extra 100 each hour. If you are with no requests left, all nexus requests are blocked (this includes downloading manually). Downloading a file is 2-3 requests, checking a mod for file updates is 1-2 requests. Logging In uses requests as well. Limiting API calls is standard procedure to avoid overloading servers with requests, slowing them down. Otherwise the API functionality might get compromised for everyone because someone is abusing it. This particular implementation is pretty simplistic, but should serve it's purpose well. Nexus staff mentioned that they are monitoring usage and will adjust the limits in case they deem it necessary.

In response to post #67632451. #67632701 is also a reply to the same post. There are sill people that are fond of NMM, despite the fact that that it's no longer supported. I do believe someone of the long term fans might update it, even though I personally don't agree on that trustworthiness statement. Like with MO1 it all depends on whether there is someone there willing to put in the time and effort. Nexus staff will, understandably, not update NMM.

Congrats for the release! As people on the Mod Organizer 2 discord know, we are already testing dev builds with the new API, so you can rest assured MO2 will get an update in time to support the change. (It has been in the works already for a while) About MO1, there hasn't been any discussion yet about updating it. Since the update does take quite a considerable amount of time an effort, it could be that there is no one with enough free time to dedicate to it.