The Stardew Valley preview is an opportunity for you to get involved, test it, and let us know what you think. It currently has all the features needed to help you easily mod Stardew Valley, such as mod updates and installing collections.
There are many features we are still developing and hope to introduce you to them soon, along with support for additional games in the future. To see this take a look at our roadmap. We’d like to remind you that the app is still in development, and with anything in development, you may encounter bugs. If you come across anything in your testing, please report it to us on our Discord, GitHub, or forums.
Now, I know what you might be thinking…
How does it make modding easier?
- Easy and Reliable Mod Installation – The app ensures a smoother installation process for most mods.
- Collections – Easily turn them on and off, allowing you to experiment with using mods in conjunction with collections so that you can configure your perfect setup. Premium users will also have the extra benefit of super-fast collection installs.
- Loadout Management – It offers loadouts and loadout switching, with separate configs per loadout, and fast loadout creation and cloning. This means you can easily swap between different sets of mods, perfect for switching between single-player and multiplayer setups.
- Health Check – This feature will give you guidance on possible issues in your setup and how to fix them.
- Workspace System – View and use every feature side by side with panels, with the ability to open 4 panels side-by-side for seamless multitasking, on demand. So you can cross-reference with ease and quickly compare information across pages, manage mods, and check details without losing your flow.
- Faster Than Vortex – Experience up to 10x faster collection installation compared to Vortex.
How to try the app
If you’d like to try it, you can download the app here.
Important: Pre-existing Mods Will Be Removed If You Uninstall
For the best experience, we recommend starting with a clean game installation. If you already have mods installed before setting up the app, they will be detected and listed as "External Changes".
However, if you uninstall the app or stop managing the game, any pre-existing mods will be automatically removed from your game folder. This is to keep your game folder clean and prevent potential issues.
To avoid losing any mods you want to keep, we strongly recommend backing up your files before installing or uninstalling the app.
If you would like to import your mods from another mod manager, you can find all the information you need about transferring existing Stardew Valley mods to the App here.
What’s next?
The app is still in active development, and we’re continuing to improve it based on community feedback, so please keep sending us that feedback on our Discord, GitHub, and forums. Some features, like full collection support, are still in progress, and we’ll keep you updated on future releases on the app mod page.
Get involved
The app is proudly open source, meaning anyone interested can contribute to its development. If you’d like to help out or just follow its progress, check out our Documentation.
We encourage Stardew Valley modders to download the app, explore its features, and share their feedback. Your input is invaluable as we continue improving the app. Download the app here.
As an extra incentive for you to give it a go, we’ll also be giving away 10 copies of Stardew Valley for people who don’t own the game but would like to play it and help test the app. Simply fill out the Google form linked below and you’ll be in with the chance of winning 1 of 10 copies of the game on your choice of Steam or GOG.
Enter to win a copy of Stardew Valley
50 comments
We appreciate your feedback and want to keep the discussion on this page focused on the new Nexus Mods app. Please make sure your comments are relevant to this news post - off-topic posts will be removed.
We understand that many of you are still getting used to the new search and game home page updates. It's clear to us that passionate members of the community have a lot to say about it and we welcome your feedback, but to help us gather feedback in the right place please keep posts about the Mod Browsing Overhaul changes in this forum thread.
Thanks for being part of our community!
Also, a bug: When you have the Health Check window open and click on the "Library" main menu button twice, it changes the Health Check window to the Library list.
There doesn't appear to be a button to go back to the Health Check window when you click through to a Missing Dependency window.
Let me know if there's anywhere you'd prefer suggestions and bug reports.
Is it purely from an organisational point of view you would want to do this?
For example my mod, Als Pre War Moddable Clothing has optional files such as "Womens Casual Outfit - Black Polkadot Override". It tries to install with the full mod name "Al's Pre-War Moddable Clothing (CBBE-TWB-3BBB-FG-BT)" or the other name. Neither are helpful for me to know what I'm looking at, using the mod name means I have two versions of the same mod? Using the file name means I don't know what it's a part of. Plus why do I need to know all the bodies I only have 1, or 3? So I rename my main install to "Al's Pre-War Moddable Clothing" and then I rename the override to "Al's Pre-War Moddable Clothing - Casual Outfit Black Polkadot Override". Now I know they belong together. It makes managing mods simpler and easier.
You guys are only looking at SDV which doesn't to my knowledge have any mods with multiple versions so you wouldn't have considered it. There's tonnes of mods for other games where the files are called "trees" and "landscape" and "pack 1"....Also from a development standpoint I have a dev version so I rename the mod to say it's a dev version so I can differentiate it from the live package.
For Kingdom Hearts 3 for example i have multiple mods that replace the same keyblades, and i have renamed them all so they're all uniform and i can simply sort by name and swap out what model i want to see in-game.
and in general it's often useful to reduce confusion, some mods have multiple files but in vortex they'll have names like "mod name - file name" which can become really, really messy in some instances. especially when the file name includes the mod name and/or the file name is actually a separate, standalone mod or a million other cases where i would rename the mod so my overview is much, much clearer.
or maybe a mod uses a name that's hard to search, or a mod has a hundred patches, some of which use the full name of the mod and others use the acronym. here it's useful to rename the mods to use either/both the full name or acronym so you can search for one and find all the relevant mods and patches or addons or w/e.
Obviously unless the mod requires it it won't show things that aren't masters, but I feel like it's a help.
And not to be "That guy" but is there any chance we will be seeing a Bethesda title or Cyberpunk added at some point soon?
Love you all!
Where are mods downloaded through the Nexus Mods app stored?
We've got a ticket in to improve translation handling. Here's a short video on how to do it with the Advanced Installer in the current release. In essence, you need to tell the app which folder to put the files into.
With that, you can easily restore a mod setup, if you for some reason have to re-setup your pc with a new windows. Just import the file and let vortex (or nexus app) re-download all mods from the nexus website and apply the conflict rules.
Do you think this is something that could be implemented? Or is that even a thing already, but i just missed it?
I mean, collections do kinda go in that direction, but there is no real way to have that for private use, is there?
Or can i just create a private one?
https://nexus-mods.github.io/NexusMods.App/users/gettingstarted/MovingToTheApp/
Collections can be unlisted, which means they don't appear in the search.
Thanks clarifying that for me. I'm sure that'll save alot of time, if anything ever happens to my pc setup.
Unfortunately however, many games lack any sort of metadata information required to implement true dependency tracking. And for some games (such as Skyrim) there may be several possible alternatives for dependencies. But what we currently have implemented is a health check system that can identifiy commonly missing dependencies and provide links to users to allow them to quickly find these missing files. We have plans in the near future to add a "fix this for me" button to these health checks that could include the ability to install dependencies if we're 100% sure that's what the user would want. So dispite the technical issues involved in dependency tracking hopefully we can get half way to what you are looking for.
And like, if the answer to this is just "it's not a priority right now because we're working on other things, but there's not really a technical barrier", or, "actually, the API doesn't really support accessing that from the mod manager app we're developing, so that'd be a really big workload to add at this point", either case is fully understandable. It just seems to me like you're reading past what they're actually talking about in order to push the new features you're excited about because you've been working hard on them. And like, I get that, full respect, but they aren't talking about the health check, and they aren't talking about collections. What they're describing is, "I go to install this one mod, it has dependencies explicitly listed in the database that the mod manager is using, the mod manager takes care of those (or at least the ones that are on the same service) automatically, the mod is installed without any further user interaction". Which is how the alternative mod manager they bring up works.
In the future if we have richer information, it may be possible to get better about this, but even with file-level dependencies, we'd have to rely on mod authors to update their dependency information whenever a mod updates. Is ModFoo version 3.0 compatible with ModLoader 3.5, is ModFoo 3.1 still compatible with ModLoader 3.5 or does it need ModLoader 3.1? If mod authors retire, who's going to keep the dependency information up to date?
These sorts of issues are solvable, but not without some changes to what we store on our servers, and a lot of involvement from mod authors. So we may look into this sort of thing in the future, but for now there's not much we can do on the mod manager side of things.
I've pretty much maxed out the capabilities of Vortex performance wise with how many mods I have, and find myself having to wait for the program to finish responding a lot even while on my fastest m.2 for simple things like disabling a few mods. Sorting by my custom categories makes it a little more responsive and my biggest curiosity is how those will be changed in NMA since I do find it to be a requirement for debugging my modlist in groups especially for performance. It was an interesting experience making modular collections before I discovered custom categories, but with both I noticed they could use the ability to search by when a mod is not in a specific category rather then only not in any at all, and I would have rather had a dropdown option for it than having to sort by a grouped table, much preferring the sort of installation time over anything else.
Glad to see Nexus put their resources to good use with this new launcher, excited to see more!
PS. I would like maximum theme customization support as it would be fun to see what I can do and develop with C# based UI over SCSS.