The mod loading system has been changed.
There is no 'autoload' mod support. The reason is simple, we have no idea what mod is loaded/used when people throw everything in that directory, and it can cause other unforeseen conflicts between different mods, and while playing multiplayer games.
Now, all mods must be specified on the command line or shortcut!
You drop a multiplayer mod into the mod/multiplayer directory, and then on the command line (or shortcut) you specifiy --mod_mp whateverModIs.wz
You drop a campaign mod into the mod/campaign directory, and then on the command line (or shorcut) you specify --mod_ca whateverModIs.wz
You drop a 'global' mod into the mod/global directory, and then on the command line (or shortcut) you specify --mod whateverModIs.wz
When you are hosting a multiplayer game, then *all* clients must also have the mod installed in the multiplayer directory, and also must use --mod_mp whateverModIs.wz on the command line / shortcut, to have a more stable game!
The reason for that is, if each person is using different data files, then the game becomes unstable. I know allot of you have noticed this in 2.1.x and earlier versions of the game.
As developers, we need to be able to replicate bugs/crashes so we can fix them, and since people never say what mods they are using, or mods they forgot about in the autoload directory, it makes our job 1000x harder.
The new crash report file will give us what mods people are using, since it was specified on the command line/ shortcut.
We should have better mod support for 2.2.4.
Thanks for understanding.
And now, screen shots for windows users.
This is your normal desktop shortcut icon, and when you right click on it, and select properties, you will see: