OlasMarz

I see it is included in this FOMOD on the CBBE 3BA (3BBB) Nexus page...maybe its included in other CBBE Base mods too? Hopefully this points you in the right direction. You can view the contents of each mod file before downloading them by clicking "Preview File Contents". In this screenshot I previewed the Main File". If you already have this installed, you may have missed a step when going through the FOMOD and might need to reinstall it.

I have had instances of this too. I've experienced: - Plugins being left in my game mods folder even though I have the mod enabled but plugin disabled. - Upon deployment, prompts stating that certain files (which I havent even modified recently) have been deleted outside of Vortex. "Would you like to delete file or revert to original file?") - Deploying (with Autosort enabled), and the new plugins are still disabled after completion. I'm currently using Vortex (Stable 1.10.8) which has been very stuttery. However, I've experienced the above issues on previous versions of Vortex too. I never use the in-game Mod/Plugin Menus.

I'm experiencing this same thing now. I've tried rebooting a couple times and closing all other applications. Vortex version (Stable 1.10.8) Skyrim 1.6.640 System Specs OS: Windows 10 Pro CPU: AMD Ryzen 9 5900X 3.7 GHz Cooler: NZXT Kraken Z73 Liquid CPU Cooler MB: Asus ROG Crosshair VIII Formula ATX AM4 RAM: 2 x (G.Skill Trident Z Royal 32 GB (2 x 16 GB) DDR4-3600) GPU: NVIDIA Founders Edition GeForce RTX 3090 24 GB Game Storage: M.2 WD Black SN850x 4TB (among plenty of other storage disks)

Sry to reopen the issue but... I was curious if anyone had any suggestions regarding any useful info for making myself a Vortex extension that can do either of the following: 1. Add a "contains light plugins" symbol to the CONTENTS column OR 2. Add a new MODS tab column that adds the "contains light plugins" symbol. I don't know how to code, but I'm trying to piece things together using modding.wiki and the index.js from a few other extensions.

BIG +1 The idea of that portal sounds amazing. It kind of reminds me of Modmapper. I think this would immensely improve user's load orders. I think the easiest way to implement that would be to allow modders/uploaders to simply link the compatibilities/incompatibilities (the same way Nexus currently allows them to link "Requirements/Mods requiring this file" mods to the Nexus description. At the moment everyone just types it in the description or posts a sticky in the comments, ...which is somewhat inconsistent. All of that data (I think) should be able to carry over to Vortex nicely. vvvv Even just adding inter-mod compatibility to the mod page tabs (i.e. Files, Comments, Bugs) could be a huge help a lot just to. vvvvvvv I've just been using google sheets to make compatibility spreadsheets for certain category compatibilities that get confusing for me (like animation mods; MBO, JBO, 360WaRP, Underdog, TDM, TUDM, TK Dodge, etc). Which is annoying, but it is what it is. At the same time, users should still know exactly what they are adding to their game.

I feel like an idiot....ALLLLL this time and I'm learning today (ON ACCIDENT!)... that you can use split screen in Vortex. I don't think I've ever even seen some one use that in a tutorial. Split screen feature solves my problem. Still doesn't fully solve my problem but it helps a lot. smh. all this time. Also, thanks for your help folks.

I get what you're saying and that's actually a good workaround because it filters through a lot more... but it doesn't fully solve the problem imo. I don't think that Vortex is always right when it comes to "whether or not a plugin can be light". It even tells me that "Hearthfire Multiple Adoptions" could be light, but it has scripts so (at least from my understanding) it cannot. So the plugin might show up, but it also might not. For instance, if I install 10 mods and want to see in Vortex which newly downloaded ones are light, ..some of them might come up if I filter for "could be light", but possibly not all of them that "could be" (and they'd still be scattered). Plus if Vortex deems that a plugin is not/cannot be light I wouldn't be able to see it and wouldn't immediately notice because it would be filtered out.

I do filter on my plugins page to show only light plugins and have the Mods column enabled. However, it will also show all of the other mods I dont need to ESLify or have already converted to ESPFE. I have 1700+ mods active so even when I use the "light" filter that's 900+ plugins. In order to know what the latest mods/plugins are that I've recently downloaded and that I'm inquiring about at that moment...I'd need to go to the Mods tab and filter by the latest date/time to figure out what I'm even searching for (Unless I'm missing another way of finding that). Then, I'd need to go to the plugins tab and search for the mod to figure out if it is a light plugin. This method is fine for one or two mods.... but it just seems like there must be a better way than the constant going back and forth.

because,.. there is no filter for date/time on the "Plugins" tab. So... say, just for example, I download 10 mods and I might need to ESLify some of them in SSEEdit. Unless I've memorized the 10 mods I've just downloaded...I'd need to go back to the "Mods" tab every time to see which mod I'm inquiring about. I guess what I'm saying is, if there was a either a date/time filter on the "Plugins" tab OR some type of lightplugin content flag on the "Mods" tab...it would eliminate a lot of that back and forth when finding which mods I need to make light in SSEEdit.

another main fix would be to add filtering by installation date/time on the PLUGINS tab... same way it is on the MODS tab.

My problem: It gets very inconvenient when I need to convert/see what is and is not already converted to an ESPFE...because I have to individually search in the "PLUGINS:Flags" tab for each mod to see if it is flagged as a light plugin. Possible solutions: Since the "PLUGINS:Flags" column currently allows you to see if a specific plugin is flagged as light and each plugin's mod already has a link back to the "MODS" tab..... would it be possible to set some small script that mirrors that (plugins:flags:light plugin leaf icon) back to the "MODS:Content" column? It would make things so much easier to identify when converting many mods to ESPFE and I feel like it would be the easiest way to implement that. To go even further,.... Additional forms of the (mods:content:plugin icon) could be a solution. There is already something in Vortex that identifies whether a mod has multiple plugins during installation. For example, if a mod has two plugins (one a regular .esp and the other an esl-flagged .esp) it could show both and . (the second icon I obviously just quickly altered in paint for illustration) The script could also quantify something like... "If there is only one plugin..and the plugin is light...only add (mods:content:light plugin icon)". You could even still use the (plugins:flags:master plugin star icon) on the "MODS:Content" page for .esm combinations. To be clear,.. I think still using the (plugins:flags:light plugin leaf icon) instead of the one I just made up above would keep it more consistent..but you get what I mean. Alternatively.... You could just mirror the "PLUGINS:Flags" column to the MODS tab for each item.

I had to change the LoadOrder.txt file for it to work for me. idk why. (FYI, I use NMM) My solution: Copy the "loadorder.txt" file and paste it somewhere as backup (just in case) Open LOOT Assuming everything is sorted, click the vertical ellipsis button in the upper right corner. Click "Copy Load Order". Open MS Excel, paste the data in cell A1, then highlight all the data Select the "Data" tab in Excel, then click the "Text to Columns" button. Click "Next", "Next", "Finish"....then delete the first few columns that don't have the .esp filename in them. Copy all the data... paste it in the text document (replacing the data that was there before). Make sure that the format looks just like it did before. When I ran Merge Plugins again the error was gone. Again...this was just the solution that worked for me.