What does this mean?
Any applications using this service will no longer be able to log in, retrieve mod information or handle downloads from our site. We've been working with the developers who maintain some of the most popular modding tools to help them make the transition to the new API, so many applications that were using this API have already been updated.
Why are we doing this?
The simple answer is that the legacy API was no longer fit for purpose and had become increasingly hard to develop on and maintain. We made changes last year to move the legacy API to https only which addressed a number of security issues, but the codebase is from an old version of the Nexus Mods website which made it difficult to keep secure without compromising usability.
Another important consideration is performance and scalability. The legacy API was designed primarily to be used by Nexus Mod Manager when our user base was significantly smaller. Other applications reverse engineered this API as time went on, but we never released any documentation for it. Continuing to use this system would eventually lead to significantly degraded performance for applications using the service. We've designed the new API with 3rd party developers in mind, making it much more accessible to integrate Nexus Mods functionality into their tools and games and we’ve built on a platform that we can scale easily going forward.
Which applications does this effect?
Any application that is still using the old API, examples include:
- Nexus Mod Manager v0.65.11 and lower
- Mod Organiser 2 v2.1 and lower
- Mod Organizer 1
Does this mean I can't use my mod manager anymore?
No, your mod manager will still work for any functions that don't require a connection to Nexus Mods until you update to a compatible version. You will still be able to download mods manually and import them into the application.
What will happen to Nexus Mod Manager?
Users with the last official release of Nexus Mod Manager (v0.65.2) will no longer be able to log in and will see an error message (below). We encourage these users to transition to Vortex or update NMM to the latest community-maintained version.
How can I update my app to use the new API?
We have documentation for the new API available here. If you require additional support implementing the new API, please contact BigBizkit or Pickysaurus.
776 comments
Comments locked
A moderator has closed this comment topic for the time beingIf you require support with Vortex, please see the Vortex Support Forum.
If you're looking for the updated version of Nexus Mod Manager, please use the link in the article above.
I want to like Vortex, I tried using it for months, but the lack of being able to manually sort your load order is beyond frustrating, and I continually have bugs with rulesets like "must come after" where vortex just...
Ignores the rule. ( Set Mod-C to load after Mod-A....organize... Mod-C is earlier in the load order compared to Mod-A )
Or yells at me that Im creating a loop or something. ( Mod-B load after Mod-A... Mod-C load after Mod-A.... Mod-C load after Mod-B - ERROR!)
- Which could all be fixed if I could manually move things. - Or If I really am creating a loop, maybe a more visual representation of whats happening vs a giant wall of text with duplicates because there needs to be "Mod-A load after Mod-B" and "Mod-B load before Mod-A"
if not, you should.
If I just wanted to quickly move things around manually, no Vortex does not do that. Hence why I dropped it for NMM, and am now dropping that for MO
REALLY?
he was using something else, then they broke it under his feet
I thought it was blatantly clear that I had tried it, listed my complaint, then moved on. God forbid if you actually went to the other comment I made it was clear I was giving the whole switch a genuine try, only to be met w/ a ridiculous problem that really aught not to exist. I swear, you act like everyone who gives criticism is a whiny kid throwing a temper tantrum. For someone who is telling me to move on w/ my life, you have a very poor choice of words. Have nothing better to do than browse comments and saying the equivalent of "umad bro"? It certainly looks like it given you take every opportunity to try and do so in other posts. I'd ask you how old you are but then again, it's just as likely you just never grew up. Enjoy having nothing better to do, because you certainly won't see me replying to your nonsense after this (trust me, the irony isn't lost on me I typed this). Have a good day, though I doubt you'd deserve it.
"Vortex has graduated from its initial alpha testing phase and we're now ready to open it up as the preferred mod manager for Nexus Mods users. While Vortex includes all the features we intended to bring to a full release, there may still be things we can tweak to improve performance and usability. There can also be bugs in the software from time-to-time that were not uncovered during the alpha release. "
How about Nexus opts to go with a finish program to replace another finished program instead of using one that is "still in the works". Yes, I am well aware that Bethesda releases all of their games in beta, but it doesn't mean I have to like it.
At least Nexus has the download history, which will come in handy as i try (again) to make the transition to Vortex, just so I can play Skyrim again.
That's basically a list of things Tannin/Nagev want to cover before Vortex 1.0 is done.
thanks.
What you mean is a "stable" release.
There is two ways software can have a "stable release". Either you defined goals in advance, both in terms of features and quality and it is stable when you achieve these goals - which is usually what you'd do in B2B contract work because somehow you have to agree in advance on the point the contract is fulfilled - or you have a preset release date that you can't/don't want to delay (any more) and whatever you can publish at that time is your "stable" release - which is what just about everyone does who releases to end users.
Thus your claim "Bethesda releases all of their games in beta" is cute but of course you don't get to decide what is beta and what isn't. They released it without a beta tag and therefore it's a "stable" release by definition. Whether you disagree with their quality standards is up to you, it's not relevant to the development state.
With open-source/free software or software as a service, "stable releases" are way less relevant. Devs will usually release features continuously instead of bursts (as you would see in something like Photoshop where features are used to market/sell a new release).
And since you're constantly adding new functionality, introducing new bugs while fixing others, the quality level will eventually just oscillate around a certain point where you introduce as many bugs as you fix.
This has nothing to do with users or programmers, it's just become less common that software sold in boxes at a fixed price where you buy a set of functionality and if you want more features you need to buy the next box.
With Vortex we decided to have stable releases that will receive only bugfixes while maintaining a separate release for additional functionality in parallel so you get to pick whether you want the newest functionality or a more stable version. Obviously that's a bonus for users, but extra work for us.
Thank you very much for the laugh, the irony of your reply is priceless. I bid you well in your life and hope you achieve everything you wish for.
The only time I run into any degree of difficulty is when there are mod conflicts, and the conflict resolution process is pretty much intuitive , as long as one reads the mod author's instructions. Most times Vortex recommends the correct remedial action (load this before that - suggested)..
Daunting as it was at first (again, first game I've played in over a decade) This stuff isn't rocket science.
The API section of the Nexus profile just has buttons that spit out an API key. Why do you have a bunch of "Requests" for API's of each application if all it does is give you a key the applications never use?!
Also quite the stealthy approach of capping the rates on the API while pretending it's just a move to retire the old one..
Lastly, there is no identification of what a "request" actually is (even in the documentation) Is it just when a new mod is downloaded or is it for the other functions such as Endorsements or any of the others mentioned in the "official" documentation.
Originally I was just going to ignore this move, but in practice, this entire debacle is beyond infuriating.
Clicking "Connect to Nexus" worked this time. Initially the webpage wasn't popping up. ( I could have sworn I tried after upgrading, but it worked now, so I assume user error on my part)
Still, it was hardly logical to assume that just because "2.1 and below are affected", that automatically means only after upgrading will the connect button work. (Unless by "affected", you meant literally that the new API can't affect/interface with older versions; in which case it's still incredibly obtuse since the interface is actually broken by the update)
You could have simply stated that "You need to upgrade your version in order to connect to the new API", then you could get on peoples' cases about not following directions.
This is what all of us NMM users need is a quick and sure way to integrate Vortex into our already modded games. It looks like to me this "import from NMM" feature is the answer, but it is also what has caused so many integration failures for so many NMM users. Where can I find a good walk through on the "import from NMM" feature? Are there any short cuts we can do and so forth? There has got to be a simple and sure way to integrate Vortex into our already modded games. That's what NMM users need.
SKSE works quite well with Vortex. If you are having problems with SKSE and Vortex, then raise these issues in the Vortex Support Forum. There are plenty of knowledgeable people there who can help get SKSE up and running.
Next I click the link "Manage your API Key(s) here". It takes me to some type of web page. There are uhhh... no instructions yet again. I click the request key button to get an NMM key. I get a bunch of gobeltygook in the box... but where am I supposed to paste this key so I can log in to NMM? Again no instructions. I then request a personal key. Another blob of discriblet in another box. As usual no instructions where to paste it or what to do with it. Login to NMM Community edition still fails even though I have both API 'Keys' displayed on the webpage.
I am not a programmer and don't have ages to research a solution. What am I doing wrong? This process is definitely not user friendly. :(