Do you intend to personally contribute/program this feature?

No

I would like to see this change made to improve my experience with

Gameplay as a Player

Description

While handling player reports, I have noticed a recurring source of confusion.

Many players report that a mod is not updating, or that Steam Workshop has downloaded a newer version but the game still appears to be using an older one.

After troubleshooting, these cases are often related to an active local Mod Pack. However, many players are not aware that a Mod Pack can affect which mod version gets loaded, so they usually assume the update has failed or that the mod itself is broken.

As a mod developer, I have encountered this situation multiple times. In many cases, the solution was simply to ask the player whether they had a local Mod Pack enabled.

I think the current UI does not make this behavior obvious enough, which can lead to unnecessary confusion and bug reports.

What does this proposal attempt to solve or improve?

The goal is to make it easier for players to understand when an active Mod Pack may be affecting mod version selection.

Currently, players often see that a Workshop mod has updated successfully and naturally expect the newest version to be loaded. When that does not happen, they may spend time troubleshooting Steam, Workshop, tModLoader, or the mod itself before eventually discovering that a Mod Pack was involved.

Making this behavior more visible could reduce confusion, version mismatch issues, and unnecessary support requests directed at mod developers.

Which (other) solutions should be considered?

Some possible approaches:

• Display a more noticeable warning when a local Mod Pack is active.
• Add a clearer explanation in the Mod Pack UI that it may affect mod version selection.
• Show a reminder when Workshop updates are detected while a Mod Pack is controlling loaded versions.
• Consider making version locking optional instead of the default behavior, if technically feasible.