Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
No, they don't play well together. Stick to Nexus for mods, as they will probably have the mods anayways, and the ones for Bethesda can be... suspect in terms of who created it.... (may be stolen work)
Either you mod for us, or go to court
When I recently realized the Texture pack was giving me problems and I had accidentally made it a dependency for the mod I made, I had no problems using XEdit to remove it less than a month ago.
Someone lied to you because I'm using Nexus mods on the current version just fine.
This.
I have been using mods on and off since the launch of FALLOUT 4 from both the Creation Club, Workshop and Nexus with no issues between any of them. I also don't use mod managers. I just toss em in the FALLOUT 4 main or data directory or click install from the Creation Club or Workshop and am done.
This is so entirely wrong on so many counts.
There is no "block" on making mods, witness all the releases since the update on Nexus mods? Those are all made with the same tools of Creation Kit as always. The ONLY thing that actually CHANGED was the formatting of the BA2 files.
That's it.
That's the total change for PC.
F4SE was updated 3 weeks after the NGU. Most mods are still compatible already, and were not interrupted by this change in the first place. Most mods that WERE affected that have active mod makers behind them have also already been fixed *where needed*.
Please don't spew such nonsense without actually being able to point to exactly the sources you are getting it from. And they would likely be either very out of date, or entirely false too.
Prove it.
Cite your sources.
The majority of mods that are not updated are also *not needing to be updated* because MOST MODS do still work without ANY issue.
Go back 9 months and start reading threads here about exactly this.
Yes and No. I'll explain.
Mods from Bethesda, and mods from Nexus or other sites work fine together. There's no issue with using the two beyond the standard compatibility issues that might arise from mods changing the same thing, but that can and will happen in anything except the very small load orders.
The problem stems from 1 manager or another (In your case). If your using Vortex, MO2 etc.. you'll want to import any mods from Bethesda's Creation club into that. (Vortex has a method of specifically doing this for you.) because the creation club system is poor, and has very little conflict resolution built into it. If your downloading from Nexus and other places, use a "real" mod manager to handle it all. It's simpler, and has the least potential to cause issues.
That doesn't mean you can't combine mods from both sources. You very much can. Just ignore the load order system in Bethesda's offering. It's, well, i'd call it "serviceable", but it's far from good.
I went up to around 80 mods, and in Skyrim had over 100 purely using the Creations system. It's not "bad", it's just completely inferior to the control you get with a dedicated manager.
Now mod away with Nexus...and Beth...but seriously...looook at the Nexus...it has an analog to the majority of what is available through Beth.