Forge could set a standard for mod filenames by refusing to load mods and/or throwing errors if the filenames weren't correctly formatted.

 

A lot of people are learning to program by creating MC mods and giving them a sensible guideline for naming their files would help them develop good habits. After years of running Linux, I've become accustomed to dismissing apps with garbage filenames, but that doesn't necessarily apply to MC. Some of these people are becoming reasonably competent programmers without having learned to format their filenames in a conventional manner.

 

As a pack dev, a standard for file names would make updating packs and identifying buggy mods less frustrating. Beyond that, I can easily imagine it being used by mods and websites to develop repository-like systems for mods. An "apt-get" for mods could be pretty sweet.

 

And of course, there are the fundamental arguments that support the use of filename conventions by developers.

 

We will not throw errors because everyone and their dog has their own idea of what the standards should be and trying to impose anything on modders is like herding 3 year olds.

As it sits FG and Forge SUGGEST that modder follow a standard and FG prods it in that direction using some of the mechanics it has in place. But there isn't anything we can do to Force it.