Modding is easiest to manage when the player treats every mod as a dependency and version decision rather than as a pile of files to copy into a game folder. The interesting part is not merely that the detail exists; it is the reason it could exist in the first place.
With Mods / Modding, keeping the explanation attached matters because gaming trivia has a habit of becoming cleaner, stranger and less accurate each time it is repeated. A sourced oddity does not need extra mythology to be memorable.
Why this Mods / Modding detail is worth keeping
Steamworks — Workshop documents the point directly: Steam Workshop provides an integrated system for games to distribute and manage user-generated content where developers support it. That first fact supplies the hook, but it also points to a real design, technical or business constraint. The surprise becomes more useful once it tells us something about how the game or platform was actually made and used.
Nexus Mods — Vortex documents the point directly: Nexus Mods' Vortex is a mod manager designed to organise downloads, deployment and mod profiles across supported games. This adds the context that a one-line trivia post usually drops. It shows that the detail was connected to a wider system rather than appearing as an isolated accident with no history around it.
Nexus guidance recommends starting from a clean game installation and launching the game before beginning the mod setup process. That is where the fact starts changing how the subject looks. It reveals a priority or limitation that is easy to miss when the finished game is treated as if its current form was always obvious.
Load order, game version and dependencies can make two individually working mods conflict when used together. The useful caution is to keep the claim exactly this size. A documented detail can be genuinely strange without proving every theory, meme or community story that later attached itself to the same subject.
Keeping the original game and save data recoverable makes experimentation safer than changing many files with no rollback path. Put together, the evidence gives the oddity a proper place in the Mods / Modding story. Start from a known-working clean game state. Add mods in small groups and test before adding the next group. Record dependencies and keep a rollback path for saves and configuration.
That is the version worth remembering: specific enough to check, connected enough to explain something larger, and still interesting after the exaggeration has been removed.
The sources — Steamworks — Workshop and Nexus Mods — Vortex — are what keep the interesting detail from drifting into folklore. They support a specific claim about Mods / Modding, not every theory that can be built around it. That is a feature rather than a limitation: a small fact with a clear provenance stays useful for longer than a larger story whose most memorable pieces cannot be traced back to the game, developer, platform or historical record.
There is also a useful scale check. Start from a known-working clean game state and Add mods in small groups and test before adding the next group keep the oddity connected to the part of Mods / Modding it actually explains. The fact does not need to prove that the entire game or franchise was secretly built around one detail; it only needs to reveal one documented constraint, decision or connection that is easy to miss without the context.
Reporting notes