Change Details

Hello! Mod publisher allows characters forbidden by file system for mod names, such as :/\ and so on. When we subscribe to a mod, steam replaces these characters with '-' since it must create symlinks with names matching mod names. But it doesn't solve the problem completely. Lots of mods are not stand-alone but rather depend on some other mods (such as compatibility mods), and it's not always visible that they are failing to be loaded. People doing dedicated server setup sometimes copy the mod names for -mod parameter from mod name instead of folder name and often don't bother to check the .rpt file. Thus the creator of such a mod with invalid name is not always the person solving the problem and can't immediately get feedback that he is causing such problems. Another issue is user-made mod update automation scripts, but these are less common and system administrators can generally handle that. We maintain a mod for the game and we often help people not being able to setup command line for the dedicated server, and this issue comes up sometimes. I suggest that a big warning is added to the publisher, stating that the mod name can cause issues due to illegal characters.

Hello! Mod publisher allows characters forbidden by file system for mod names, such as :/\ and so on. When we subscribe to a mod, steam replaces these characters with '-' since it must create symlinks with names matching mod names. But it doesn't solve the problem completely. Lots of mods are not stand-alone but rather depend on some other mods (such as compatibility mods), and it's not always visible that they are failing to be loaded. People doing dedicated server setup sometimes copy the mod names for -mod parameter from mod name instead of folder name and often don't bother to check the .rpt file. Thus the creator of such a mod with invalid name is not always the person solving the problem and can't immediately get feedback that he is causing such problems. Another issue is user-made mod update automation scripts, but these are less common and system administrators can generally handle that. We maintain a mod for the game and we often help people not being able to setup command line for the dedicated server, and this issue comes up sometimes, due to incorrect naming of other mods. I suggest that a big warning is added to the publisher, stating that the mod name can cause issues due to illegal characters.

Hello! Mod publisher allows characters forbidden by file system for mod names, such as :/\ and so on. When we subscribe to a mod, steam replaces these characters with '-' since it must create symlinks with names matching mod names. But it doesn't solve the problem completely. Lots of mods are not stand-alone but rather depend on some other mods (such as compatibility mods), and it's not always visible that they are failing to be loaded. People doing dedicated server setup sometimes copy the mod names for -mod parameter from mod name instead of folder name and often don't bother to check the .rpt file. Thus the creator of such a mod with invalid name is not always the person solving the problem and can't immediately get feedback that he is causing such problems. Another issue is user-made mod update automation scripts, but these are less common and system administrators can generally handle that. We maintain a mod for the game and we often help people not being able to setup command line for the dedicated server, and this issue comes up sometimes, due to incorrect naming of other mods. I suggest that a big warning is added to the publisher, stating that the mod name can cause issues due to illegal characters.