What a mod loader actually does, and why you need one

Nothing in a game is waiting for your mods. The developers compiled it, shipped it, and it runs the code inside it. A mod loader exists because that is the whole problem.

The thing it actually does

A loader starts before the game does. It reads a folder, finds what you put there, and then rewrites parts of the game in memory as it loads, so that when the game finally starts it is running code that was never in the file you downloaded.

That is worth sitting with, because every strange thing about modding follows from it. The loader is not asking permission. It is patching compiled internals that nobody promised would stay the same.

Why that makes mods fragile

A mod says, in effect, "find the function that handles damage and add this to it". It finds that function by name, by signature, or by the exact shape of the surrounding code.

When the developers ship a patch, they are free to rename that function, split it in two, or delete it. They owe modders nothing, because from their side nothing changed: the game still works. The mod, which was pointing at something that no longer exists, does not.

This is why a mod can break on a patch that changed nothing you can see. The thing it was holding on to moved.

Loaders are not interchangeable

Most modded games have more than one loader, and a mod built for one will not run on another. They differ in how they patch, what they expose, and what they promise to keep stable, so a mod written against one is written against a set of tools the other does not have.

The practical rule is that the loader comes first. Before you check whether a mod supports your game version, check whether it supports your loader, because a version mismatch sometimes still works and a loader mismatch never does.

What this means when you install something

Three things have to line up, and the order matters.

1. The loader has to support your game version. This is the one people skip.
2. The mod has to be built for that loader.
3. The mod has to be built for that game version.

If the first is wrong nothing works at all. If the second is wrong the mod is simply not seen. If the third is wrong you usually get a crash on startup with a message naming the mod, which is the friendliest of the three failures.

Why nothing here is automatic

Every mod page on this site lists which loader and which game version its author declared, because those are the two facts that decide whether it will run, and neither is guessable from the name. A mod called "Better Combat 3.1" tells you nothing about either.