As I suggested previously, I think that the mods should be moved into a repository. There are some almost-ready things out there to be used (
https://github.com/KerbalStuff/KerbalStuff or
https://github.com/phpbb/customisation-db) that can help out with this. If things like this are not done, it's pretty much useless IMO to try to categorize mods into subforums, as mods becomes obsolete, changes directions and so on and so forth.
--------------------
If the idea above is not implemented, here's my followup idea --------------------
For me, a good structure for the Mods forum would be this
Main Forum
+ Contributions
-- Mod Releases
--- Work in Progress Mods
--- Obsolete Mods
-- Modding Discussion
+++ Big Mods (optional)
--- Mod Development help
--- Ideas and Requests for Mods
--- Modding Interface Requests
+ indicates category (no topics allowed) - indicates forum (posting topics is allowed)
This implies in the removal of 'Big Mods' section. It's cool to have a nice place for those mods and discuss things, but I think they promote a higher confusion than they help if the user is browsing for mods, downloading or installing. The good thing about that category is that it brings much discussion, so it's fair for them to have their own sub-forum for discussions (see Dytech subforum for example).
Each mod should have it's own separated topic. The author may combine their threads if the mod is modular (see Bob's), or they can create a thread like "Bob's Integrated Mods" that has links to the mod's modules.
-----Edit: added the paragraph below-----
For me, any attempt to put mod into categories, be it based on general rules that's not easily changeable or be not allowing being part of more than one category, will fail really hard, even if chosen by the mod developer. The best thing we could do is some kind of list in a topic that lists mods based on categories chosen by the developer. That way it's easily editable, people can insert new mods and it's not confusing for the player.
Also, anyone posting in 'Mod Releases' forum should follow a simple naming for the topic:
[THING FACTORIO_VERSION] MOD_NAME ('vMOD_VERSION' - DATE_UPDATED - DESCRIPTION)
The mandatory part is the three first items, anything between parenthesis is optional and may come in any order. Let's see a few examples:
[MOD 0.11.19+] F.A.R.L.
[MOD 0.11.19+] F.A.R.L. (Factorio Automated Rail Layer)
[MOD 0.11.19+] F.A.R.L. (Factorio Automated Rail Layer - v0.7.5)
[MOD 0.11.19+] F.A.R.L. (v0.7.5 - 04/July/15)
[MOD 0.11.19+] F.A.R.L. (Factorio Automated Rail Layer - v0.7.5 - 04/July/15)
[PACK 0.11.22] ShadowMegaPega (01/June/15)
These are all valid options.
Any mod in the 'Mod Releases' category that does not match the current major release should be moved to 'Obsolete Mods' (let's say a week after a new major release for giving people time).
There should A topic with all guidelines for mod authors, containing information like topic naming convention, usage of the 'Report post' to request a topic to be moved, zip file naming convention and anything else relevant.
Also, as an optional, there could be a Template that would help mod authors to create better looking topics, as they are easier to read and draw more attention.
- See an example of what was done in this topic:
https://forums.heroesofnewerth.com/show ... ember-2012 - Although this is not the best, it's what we came up with, and it worked very well. It's not the nicest of the cleanest, but it works.
-
https://www.phpbb.com/customise/db/mod/ ... emplate_2/