But back to the topic at hand.
Ok here is my problem with all this. People complain that forum descriptions are too ambiguous, yet I do not see anyone offering up better wording. You say that this is your community? Well maybe it is time that you help us make it better. (Note: This is a generalization, some people actually do have input)
I think we can only organize topics once we understand
1. What our topics are, and
2. How they feed into each other
Now, I think the following demonstrates the 'genealogy of knowledge' on QHIMM - the ways that one sort of knowledge begets another, and therefore where threads are likely to cross topics. Objects above are 'parents' to, or 'lead to' objects linked below them:
So, we start by
reverse engineering the PC and PSX builds. From this, we learn about file formats and how the data they hold is processed. This knowledge leads to, respectively,
Extractors and
Mechanics Documentation. Extractors soon become
editors. All QHIMM members need to do now is create ideas for
Mod Projects.
Once we have these ideas, we can apply our mechanics knowledge and editors to create
Mods. People play them, and submit bug reports, telling us about their
Technical Problems. Meanwhile, non-modders visit our forums wanting to get the PC build up and running. Because their bug reports usually concern our patches for the PC version, Technical Problems and
PC Build Tech Support are effectively twinned.
If we can agree to this, or something similar, we can recognize how and when topics will merge and fork. Understanding this is key.