pStyl3

Another name suggestion: ModNX As in "Modern Nexus" and/or "Mods with Nexus". Also, are you guys already interested in people beta testing your new mod manager? I'm certainly interested in taking a peek at your new mod manager, and how well LOOT is working with it.

Skyrim Performance Monitor, while not yet working under SSE, is getting an update to do so. :)

You don't need the API archive, that is for other tool makers so that they can utilize LOOT's functionality. And the .tar archives aren't for Windows in the first place. The normal "loot-soandso_dev.7z" with no API and tar in it's name is everything what's needed for the normal user (on Windows).

@ f4b10z MO2 Beta 3 is the last version of MO2 that Tannin will release (reasons) and unfortunately it didn't reach a full stable version as for example MO 1.3.11 is one. MO2 was also developed for FO4, I have my doubts that tricking it into "working" for SSE is the way to go, especially given the previous things mentioned. In any case, MO/MO2 are not supported by LOOT, meaning that MO-only issues regarding LOOT will likely not be tackled by the LOOT team. @ lizzisbow If you see that wrinklyninja removes a snapshot, please do NOT reupload it - it probably has it's reasons why it got removed. I've edited my previous post to reflect the change (what happened here was that wrinklyninja merged the SSE support branch into the dev branch, which occasionally messes with snapshot-subversion-numbers).

Q: How do I install the newest LOOT snapshot with support for Skyrim Special Edition successfully? A: First things first. Understand that a snapshot build is unofficial and normally used to test LOOT and provide feedback for wrinklyninja, LOOT's main developer. You can think of snapshot builds as a Work In Progress (WIP), so please be aware of the fact, that you are using an unofficial build of LOOT, which may or may not function correctly. That being said, without further ado, here are the steps to install the new LOOT snapshot. Uninstall your previous LOOT installation. To do so, follow the instructions here, in the description tab "DESC", in the section "Installation & Uninstallation".Also make sure that you delete yourC:\Users\<USER>\AppData\Local\LOOTfolder in it's entirety. If that folder is hidden on your PC (the AppData folder to be more precise), you can alternatively copy & paste the following line in your Windows File Explorer:%LOCALAPPDATA%Both previous steps are required, because the new LOOT version introduces a new masterlist syntax, which is incompatible to the syntax used in previous official LOOT versions.Install the MSVC 2015 x86 redistributable on your PC. This is a new dependency LOOT 0.10.0 introduces and is therefore required (so it's the same with the latest LOOT snapshot). You can now download and install it manually or wait for the official LOOT 0.10.0, which will install it automatically via it's "LOOT.Installer.exe" executable on your PC.Download the correct snapshot from <here>. The correct one to use, if you just want a snapshot with SSE support, is the snapshot with the highest number after "loot_0.9.2-" WHILE having "_dev" in it's name, if "_dev" is not in it's name, it's a snapshot build with unfinished code.Extract the downloaded .7z archive (using e.g. "7-Zip" or "WinRAR") and copy it's content to a folder of your choice. It would be desirable if the target folder is NOT within C:\Program Files or C:\Program Files (x86), as these folders can be influenced by the User Account Control (UAC), which we do not want.Run the Game Launcher from Skyrim Special Edition (so click on "Play" within Steam).Close the launcher.Start LOOT via it's executable "LOOT.exe".

wrinklyninja is working on SSE support for LOOT, my guess is that it will take a couple of days (SSE support will not be the only new feature / aspect of the upcoming LOOT 0.10.0).

In response to post #43265980. #43266775 is also a reply to the same post. Also, Mord is the german word for murder.

In response to post #43224730. #43229715, #43231195, #43231225 are all replies on the same post. NexMO = Nexus Mod Organizer

The optional snapshot file from Nexus (294) seems to be the last snapshot that worked under MOv2 Alpha 4 (more or less, as said), but that snapshot does not yet account for the changed plugin loading mechanism (the one with the asterisks you mentioned .. that is by the way not a "workaround" .. that is the new way to load plugins coming with v1.5). If you experience crashing with that version, try to start it multiple times in a row from within MOv2 Alpha 4. Also try to add the --game=Fallout4 argument to LOOT in MO's executable window. That "might" help, but no guarantee. Since you use the 1.5 Beta however, which introduced the new plugin loading mechanism, you would (currently) need to use one of these LOOT snapshots, but their snapshot number is higher than 294, making them seemingly not usable under MOv2 Alpha 4. That's the current 'dilemma'. Conclusion in this is, if you use MOv2 Alpha 4 .. just know that there are currently problems with the latest LOOT snapshots (and only those support v1.5 of FO4) and Tannin will need to fix them with a new version of MOv2. Until that has happened you will probably need to change your plugins.txt manually, so that all active plugins have a leading * added to them.

LOOT on Fallout 4 Nexus Download the optional file and install it (before installing it, go to %localappdata%\LOOT\Fallout 4\ if present and delete everything that's inside). This version should work "more or less" with MOv2 Alpha 4, newer snapshots do currently not seem to work under MOv2 Alpha 4. Best would be to wait for Tannin to release an update to MOv2 to fix these issues. That said, this snapshot will only work as long as the upcoming next patch 1.5 for Fallout 4 hasn't been released. Once that goes live, LOOT users need to update to a then newly released snapshot of LOOT, so that it will work with v1.5 of FO4 (plugin loading mechanism will change for FO4 with v1.5). That version will however probably not work with MOv2 Alpha 4 either .. so MOv2 getting an update then will be urgent. We shall hope the best that the updates will come fast after v1.5 of FO4 is going live. :smile:

Actually, I mentioned the removal of the malicous file and the upload of the proper new snapshot here. If you view LOOT's Nexus page and click on the "Posts" tab, you should see the comment still on the first page (as of writing this post). So yes, the new file is safe. :smile: Please explain in detail what you mean by that. If it is true, that you discovered something going wrong, then it would be great if you could help to tackle the issue. In order for that to happen, we would need to know which version of LOOT you were using, what your load order was/is and what in your opinion should have been sorted differently.

In response to post #28768499. I was thinking exactly the same thing just now. Given the importance to understand that message, that timer should be at least 5 seconds, if not more.

I can confirm that this issue report is correct, both NMM as well as MO doesn't seem to be able to connect to the download servers anymore. The problem got already pointed out in the following topics (I am aware of): - [PSA] Nexus is having issues with downloads and logging in. - Reddit #1 - Can't login to Nexus Mod Manager? - Reddit #2 - Issues with MO can't downlod from Nexus suddenly. - STEP - Mod Organizer - Comment Page on the Nexus

Edit

Greatly appreciated, thanks!

-Deleted-

I download from the CDN servers for the time being, works perfectly fine. :)

In response to post #15477990. This, but only for "popular" mods .. so for example (I'm picking a random number now), mods with a minimum of 1000 endorsements and/or 100.000 unique downloads. That would assure that the staff isn't restricted too much when it comes to this, on the other hand the more popular mods would have another safety barrier. E: On a second thought .. I don't know if that's the solution either.. if the kid has already fallen into the well, so something "bad" was uploaded somewhere, it would sort of prevent the staff from removing it again.

That is basically spitting on the outstanding work of those most honorable modders. Disgusting. But great it could be dealt with quickly!

In response to post #15342655. #15343275, #15343360 are all replies on the same post. Uninstalled 0.50.0, installed 0.50.1, all problems are fixed. "JIP Companions Command & Control" as well as "Unified HUD Project - uHUD" can be activated once again. Thanks :)

In response to post #15341060. #15341150 is also a reply to the same post. Okay, this problem does NOT happen with every mod whatsoever. I just downloaded the newest version of New Vegas Bounties I. Deactivating the old version and activating the new (and just downloaded) version does work. But, if I try to activate the newest version of JIP Companions Command & Control (just downloaded aswell) the mentioned problem occurs. The same happens by the way for Unified HUD Project - uHUD, I can't activate that either - and that I did not update. I just wanted to deactivate/activate it in order to properly install the new JIP update.

Thank you for the update. Unfortunately I have a problem. I use FF (v28 ) on Win7 x64 Ultimate and have installed .NET Framework 4.5.1 (exact version: 4.5.50938, installed on the 27th of February 2014). I uninstalled NMM 0.49.7, installed NMM 0.50.0 into the same location (i use NMM for FNV). Login as well as downloading mods works as intended, but if I want to activate a mod, I get the following error message: Image For some reason the error message is displayed in the language my OS is set to, german. The message says: 0,0: An assembly with the same identity "snip" has already been imported. Remove one of the duplicate references. Any advice?

Könntest du bitte ein Übersetzungsprogramm verwenden, um zum einen in diesem englischsprachigem Forum nicht auf Deutsch zu schreiben und zum anderen auch das zu verstehen, was dir geantwortet worden ist? Ich finde es etwas dreist, die Übersetzungsarbeit einfach an andere (z.B. dem Modauthor) abzuwälzen .. mit deinen beinahe 800 Posts müsstest du es doch besser wissen.. Und um es noch einmal klar zu machen, dass hier hat djjohnjarvis dir geantwortet: Nun liegt es an dir, dies mittels z.B. Google Translator zurück ins Deutsche zu übersetzen. --- djjohnjarvis, can't wait to test Sofia. :smile:

Is it possible, that the site registration process has a problem once again? I noticed two people on YouTube reporting the following issue while trying to create an account: An error occured with the SQL server: mySQL query error: ALTER TABLE ibf_pfields_content ADD field_1 text NULL This is not a problem with the IPS Community Suite but rather with your SQL server. Please contact your host and copy the message shown above. To be exact, they posted that error messages and . That said, happy new year everyone!

Small issue with the Comment tracking centre: Image