ESP flags shown on "MODS:Content" column

[OlasMarz]

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.

 

 

[OlasMarz]

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

[Pickysaurus]

I'm curious, why would you need this information in the "Mods" table when you manage plugins from the "Plugins" table. Perhaps revealing the "Mod" column in the plugins table would help you?

 

I don't really understand the problem you're trying to solve here.

[Guest deleted34304850]

are you not filtering on your plugins page to only show mods that could be changed to "light"?

you can also enable a mod column on your plugin page to show the mod/plugin relationship.

by utilizing those two features, i think you resolve a lot of what you're looking for?

[OlasMarz]

I'm curious, why would you need this information in the "Mods" table when you manage plugins from the "Plugins" table. Perhaps revealing the "Mod" column in the plugins table would help you?

 

I don't really understand the problem you're trying to solve here.

 

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.

[OlasMarz]

are you not filtering on your plugins page to only show mods that could be changed to "light"?

you can also enable a mod column on your plugin page to show the mod/plugin relationship.

by utilizing those two features, i think you resolve a lot of what you're looking for?

 

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.

[Guest deleted34304850]

if you filter as you say you do - are you then NOT making them light? because if you make them light, then they are not shown by the filter, as they are then flagged as light and removed?

actually - i will make an update - i filter on "could be light" not actually light - so - if i have say 700+ mods in my load order - and approx 500+ of them have been made light - then i never see them - i only see those that "could be light" and that could be a handful?

Edited May 23, 2022 by 1ae0bfb8

[OlasMarz]

if you filter as you say you do - are you then NOT making them light? because if you make them light, then they are not shown by the filter, as they are then flagged as light and removed?

actually - i will make an update - i filter on "could be light" not actually light - so - if i have say 700+ mods in my load order - and approx 500+ of them have been made light - then i never see them - i only see those that "could be light" and that could be a handful?

 

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.

[Pickysaurus]

 

I'm curious, why would you need this information in the "Mods" table when you manage plugins from the "Plugins" table. Perhaps revealing the "Mod" column in the plugins table would help you?

 

I don't really understand the problem you're trying to solve here.

 

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.

 

 

 

The problem is, the only date that would be relevant to the plugins table would be the created/edited date for the plugin which is often inherited from the archive.

 

You could make a basic extension which adds a new column to the plugins table with the date of install from the mods table, but I don't see this as a feature that would be used by many users. Most of the time you can filter by "could be light" and simply mark those as light.

[Guest deleted34304850]

 

if you filter as you say you do - are you then NOT making them light? because if you make them light, then they are not shown by the filter, as they are then flagged as light and removed?

actually - i will make an update - i filter on "could be light" not actually light - so - if i have say 700+ mods in my load order - and approx 500+ of them have been made light - then i never see them - i only see those that "could be light" and that could be a handful?

 

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.

 

that is a good point - you can have a mod that qualifies as "could be light" although making it light is going to give you a bad day, so you're correct to not trust the filter 100%, you still need to do your own due diligence around what the filter is telling you.

 

i have seen instances where someone has blindly set everything they could to "light" - simply to get more mods into their game, almost using the "could be light" flag instead of merging patches. of course the end result was a broken game.

 

i think Picky has come up with a plausible workaround - although I do agree with his point that this would be a niche use modification - but the point is - if it doesn't exist and someone creates it, its there for that niche case use, and to me, that makes vortex stronger.