[REL] [WIP] Easy SCSModManager (ESCSMM)

[bronto45]

Hello.The program is very good and useful.But please change the font in the drop-down windows.Black on black is completely unreadable.Thank you.

[BeckysFootSlave]

Hello.The program is very good and useful.But please change the font in the drop-down windows.Black on black is completely unreadable.Thank you.

New version 1.3.0 is out and should fix it!

[00player00]

Can a function be added to delete non-workshop modules?

[BeckysFootSlave]

Can a function be added to delete non-workshop modules?

Woah, that's a really good idea and should be easy to implement.
Why didn't it came up into my mind bc I already deleted some by hand

Give me some time, I'll implement it in the next release!

[LLBBC]

I’ve run into an issue: after enabling multiple mods consecutively, the original location categorization gets altered.

[BeckysFootSlave]

I’ve run into an issue: after enabling multiple mods consecutively, the original location categorization gets altered.

Thanks for the report! To make sure I chase the right thing, two quick questions:

1. Where does it change - in the mod grid on the left (the category/position of the cards), or in the "Active mods" list on the right (the load order itself)?

2. Can you give me a quick before/after? Something like: "I enabled A, then B, then C - and mod X, which was at position 5, jumped to the top." A screenshot of both states would be perfect.

One thing that might already explain it: mods whose names contain one of the "Map base" terms (Settings -> Map base, e.g. "map", "loading screen") are automatically pinned to the top block of the load order when activated - that is by design, and the term list is editable there. If the mods that move match those terms, that is the feature doing its job; if not, I definitely want your exact steps.

And as always: which version are you on (1.3.0 is current), and Windows or Linux?

[LLBBC]

I’m running Windows 11 and using the tool in version 1.3.0.
For reference, on the left side of the tool, Mod A is classified under Trailers, and Mod B under Trucks.
If I enable Mod A first, it will show up in the Trailers category on the right. After that, when I enable Mod B, Mod B correctly appears in the Trucks category on the right, but Mod A is also automatically moved to the Trucks category.
If I reverse the enabling order, the problem does not occur. I believe this issue is caused by the vertical positioning of different categories on the right panel.

[BeckysFootSlave]

I’m running Windows 11 and using the tool in version 1.3.0.
For reference, on the left side of the tool, Mod A is classified under Trailers, and Mod B under Trucks.
If I enable Mod A first, it will show up in the Trailers category on the right. After that, when I enable Mod B, Mod B correctly appears in the Trucks category on the right, but Mod A is also automatically moved to the Trucks category.
If I reverse the enabling order, the problem does not occur. I believe this issue is caused by the vertical positioning of different categories on the right panel.

Confirmed, and thank you - that was a textbook reproduction, it let me trace the bug in minutes. Your theory was spot on: group membership in the right panel IS positional (that is how the list mirrors the real load order). The actual bug: activating a mod always inserts it at the very top of the list, ignoring groups. So when you enabled the Trucks mod after the Trailers mod, the Trucks entry (and its group header) landed above your Trailers mod - which then visually ended up inside the Trucks block. That also explains why the reverse order works: it accidentally produces the correct group sequence.

The fix is straightforward: activation will insert the mod at the end of its own category block instead of at the top. Coming in one of the next releases.

Until then, two workarounds: enable mods roughly in load-order direction (top groups first), or just drag the entry to the right block - dragging works correctly today.

[BeckysFootSlave]

Can a function be added to delete non-workshop modules?

Done - your feature is in! Since v1.3.1 (current version is 1.3.2) you can right-click any local mod -> "Delete...". A few details on how it behaves:

- Deleted mods go to the system trash, never permanently removed - you can always restore them from there.
- Multi-select works: select several mods, one right-click, one confirmation dialog listing them all.
- If a mod is still part of a load order, the dialog warns you and names the profile before you confirm.
- Workshop mods are the exception, as you guessed: those are managed by Steam, so the entry is greyed out for them - unsubscribe in the Workshop instead.

Asked Saturday morning, shipped Saturday. Thanks for the idea - this also lays the groundwork for a future "cleanup helper" for huge mod collections.

[BeckysFootSlave]

I’m running Windows 11 and using the tool in version 1.3.0.
For reference, on the left side of the tool, Mod A is classified under Trailers, and Mod B under Trucks.
If I enable Mod A first, it will show up in the Trailers category on the right. After that, when I enable Mod B, Mod B correctly appears in the Trucks category on the right, but Mod A is also automatically moved to the Trucks category.
If I reverse the enabling order, the problem does not occur. I believe this issue is caused by the vertical positioning of different categories on the right panel.

Fixed in v1.3.2, which is live now. Your diagnosis was spot on: group membership in the right panel is positional, and activating a mod always inserted it at the very top - ignoring groups entirely. That is why the enabling order mattered.

New behavior: activating a mod now inserts it at the end of its own category block, so Trailers land under Trailers and Trucks under Trucks, no matter in which order you enable them. Bonus fix in the same release: double-clicking a mod that is already active no longer moves it around - it just highlights it in the list.

And a small thank-you that might amuse you: your exact reproduction (Trailers mod first, then Trucks mod) is now a permanent automated test in the project - every future version has to pass your scenario before it can be released. That is how good a bug report it was.