Seraffian

Good to know I'm not alone :)

Because sometimes I download and install mods for different profiles at the same time and I don't want them all enabled on the same profile. I know, I'm weird and probably doing it the wrong way, but I'm not very good at modding so I just have to do it the way it makes sense to me and the way it works best for me. Even when it doesn't make sense to others.

As long as it's an option you can turn off of you don't want it, I'm all for it as well. Sometimes it's nice to be able to download and install a mod (or a few) without enabling them right away. Maybe that's just the hoarder in me :D

Totally agree with Dargone. I'm constantly amazed at how easy and quick it is to use. I'm a noob when it comes to modding and I've currently set up Fallout 4 with two profiles, one for settlement building and one for a survival playthrough. I constantly expect my ruthless way of installing mods - which is basically to just throw a bunch of them in there and hope it all works together - to crash the game or completely ruin it, and every time I'm amazed that it just works. Sure, I get mod conflicts and error messages, but instead of having to spend hours trying to figure out what I did wrong with a game that keeps crashing, Vortex tells me exactly what's wrong and how to fix it. It even recommends which mod to load before/after the other in case of a mod conflict which is brilliant for someone like me who don't often know the right load order. I've spent some time learning Vortex - even asking questions here and gotten some really helpful advice from kind people - and for a noob like me the manuals could be a little easier to understand, but once I learned how Vortex behaves and what it does, it's been smooth sailing ever since. Vortex is the best mod manager I've ever used by far and I spend almost all of my time IN-GAME now, which is where I'd prefer to spend my time, rather than in the mod manager. :) Keep up the great work!

@HomerSlated Best.post.ever. :D

Correct me if I'm wrong but can't you just download the file that says "Vortex (custom install location)" from the Vortex Beta page? https://www.nexusmods.com/site/mods/1?tab=files

Please pursue this. I would think your best bet is to contact any of the Nexus staff who frequent these Vortex forums. Perhaps PM some of the staff? Do you think a Knowledge Base glossary of terms would help? I suspect that technical terms and language used in the Knowledge Base and these forums is both opaque and intimidating to many who are new to mod managers and to Vortex. I'll keep a notepad of things that pop up from time to time. Right now there's only two things in there and right now Vortex is working like a charm and requires no guides :) But I'm sure I'll stumble backwards into a serious of issues at some point in the future. I mean, I plan to mod Fallout 4 with 2 separate profiles in the future... After hearing Gopher explain the difference between 'Masters' and 'Masters', yes, a Knowledge Base glossary of terms would certainly be helpful I think :laugh: If we can look up some of the terms used both in the mod manager and on these forums from time to time, that would save all of us some time I think (at least if people actually care to look it up first - some people seem reluctant to ever opening a guide or manual...). We could then easily look up terms in your replies we're uncertain about and you don't have to explain them multiple times in multiple threads to multiple users. Ehm.. "take backups"...? :ohmy: that sounds like something really important one really should do a lot... I should look into that :laugh: It's great to hear there are patient people on here who are ready and willing to deal with questions from us newbies! I am really trying to learn but it's good to know there's a place to ask those stupid questions I for some reason can't find the answer to. Maybe we should start a "Stupid Questions About Vortex" thread just to make sure everyone dares to ask the questions they think are too stupid to ask (obviously with a disclaimer in the first post stating one should read through the guides provided first) :laugh: Hopefull it won't turn into a "Thorarinn Asks All the Questions No One Else Dares To Ask" thread...

Thanks for such a nice, detailed explanation which was easy to understand, even for me! That's basically how I've understood it as well, but it's always nice to have it explained properly. Clears up any confusion on my part :) Sing hosana's for Vortex, indeed. That's at least what I've been doing the last few days! I'm having so much fun modding now that I almost forget to actually play the darn game :laugh:

(I'm gonna assume you're trying to help and not make me look stupid. Plain text makes it hard to catch the "tone" of your voice, you know :) ) The way I understand it, a mod conflict occurs when two (or more?) mods are trying to edit/change the same file(s). I know in NMM at least (not sure about MO2) you had to install the conflicting mods in the right order, having the latter overwrite the former - in which case I just did whatever the mod page told me to and hoped for the best! :)

I wouldn't call the conflict resolution "a pain", but for someone like me, who doesn't have a lot of experience with modding in general, it's not... too clear? And it's not simply a case of "educating" myself as I've spent hours reading every guide provided by Vortex and I've watched all five videos by Gopher and I still struggle to figure everything out. That said, Vortex it's still better - at least in my honest opinion - than NMM and MO2. At least with Vortex I know there's a conflict that needs to be resolved right away, whereas in NMM and MO2 I would just have the game crash and struggle for hours figuring out why. Just like OP, I had issues with SMIM and getting several other mods to work with it. My problem was mainly that even though Vortex told me there was a conflict and that I needed to resolve it, and the guide I read and Gopher's video told me how to fix it, I still didn't know exactly in what order the conflicting mods needed to go. I'm talking about in the Mods tab now as I've never touched the Plugins tab. But if I understand it correctly, you have to resolve conflicts by setting up rules stating which mod needs to load before other mods - in other words, setting a small load order for a few mods that are conflicting? This is probably just because of my own lack of knowledge of each mod and modding in general but I found it a bit daunting when I had 4-5 mods conflicting with each other and I was trying to sort out which mods should be loaded before and after the others (and yes, I did only install and enable one mod at a time but Vortex still shows you all the mods that are in conflict and that can easily become 4-5 with texture mods). And the more rules I set up, the more of a mess it became (it looked like a mess to me, but apparently not to Vortex - see below). Maybe there's a simple overview screen of all the rules I've set up that I haven't discovered yet? Anyway, the Vortex guide uses an example that seems to be a very simple problem and with only 2 mods where you just have to make a basic choice of colors. Maybe I'm just too dumb to figure out my own conflicts based on that guide but it didn't feel like the guide addressed my particular issue, at least not on that occasion. That said, I realize Vortex is still in Alpha and the guides probably won't be anyway near complete at this stage, which is fine and I understand that, but I hope it's okay to still ask for help when I run into mod conflicts and can't sort them out despite having done all I can to figure it out (it seems like the standard reply in a lot of threads is "educate yourself before asking stupid questions!" which makes someone like me a bit afraid to ask I'm afraid :confused: ) I read the mod pages and googled a bit, which gave me a hint of which mods should be loaded before the others, but eventually I just had to guess (I don't know if that's something Vortex can help out with in the future? Like when it informs you of a conflict, it also gives you a hint or a tip, maybe based on previous experience, as to which order they should go in?). Anyway, despite guessing with my very little modding experience, the game seems to be working fine and I haven't had any other conflicts since. And that's where Vortex is in a league of its own! When there are no conflicts, I almost can't believe how easy Vortex is to use. Click download on Nexus, click install and enable in Vortex - Play the game. No LOOT, no figuring out the load order myself, just install and play. What a wonderful thing! :laugh: Btw, since I'm fairly inexperienced with modding and more often than not needs things spoon-fed to do things correctly, I could be a good help with guides in the future as I can point out where the guide seems to rely on "things everybody knows" except for us newbies and where it needs to be more specific. I've started jotted down a few things when I spot them so maybe there's somewhere to provide feedback on the guides and not just Vortex itself?

Good luck all!

I recently did a clean install of Skyrim and Mod Organizer after my ventures into ENB's didn't go so well... I'm currently installing mods – closely following Gopher's videos to make sure I get a stable build – to set up my game for a new character I think I have a cool backstory for, so I will be playing Skyrim again soon. Meanwhile, I've been playing a lot of Mad Max but have recently stopped. I've gotten to a point now where it feels very repetitive and I can't see myself actually finishing it. On my to do list: Morrowind, Oblivion, Fallout 3 and Fallout New Vegas. And Witcher 3. And Dark Souls 2. And 3... Oh, and Metro Last Light and 2033 Redux... I have them all sitting in my steam library but have never given them a proper play through. Might pick up Doom and/or Hellblade during the Steam winter sale as well... Think I might need to quit my job to get through them all! :laugh:

First of all, Championship Manager 2 97-98. Played that game so much my dad felt the need to hide the computer power cord just to get me out of the house every now and then :laugh: But I think my fondest memory of old school gaming was me and 3-5 buddies playing the original Halo on the original Xbox. We would set aside a Saturday evening (and Sunday morning) every now and then to play against each other. Multiplayer was a bit different back then; we would set up 2 or 3 TV's (depending on how many we were) and consoles in someone's living room, link them all together and play from 8-9 PM until early morning. Great game and great memories of long nights with junk food and a lot of laughter!

I started FO4 through Steam (since F4SE isn't updated yet) and everything seemed fine. All the mods from Nexus were there, I didn't get any warnings when loading up my save about missing mods and even Sim Settlements which relies on F4SE seemed to be working just fine. It shouldn't work though, right? I didn't save the game as I don't want to overwrite my current playthrough while F4SE isn't up to date. Just wanted to let you know and if you know why it seemed to be working fine and also why it's probably not, let me know :)

Just checked my Data folder and yes, all the CC I didn't order, pay for or want have been downloaded and are currently taking up 681MB of HDD space. I know, 681MB isn't a lot, even for someone like me who doesn't have a big HDD, but it's only for 10-12 mods. What happens when/if the CC grows to say 100 mods? Are we forced to store several GB's of content we didn't want, didn't pay for and don't have access to? It's probably legal - otherwise they wouldn't have done it I guess - but that made me really furious. F4SE will be updated because competent and brilliant people make it so I don't really care that I can't play FO4 for a few days, but forcing me to store extra content on I don't want on my limited HDD?! Anyways, I switched FO4 in Steam to only update when I launch the game but I'm wondering if that's good enough to prevent future updates or does launching the game through F4SE count as me launching the game and therefore enabling steam to update the game? #LetCCDie