Tweet
One of the 3 or 4 major goals of this site when conceived was solving people's Quake issues and that has been a resounding success.
The questions that come up any more tend to be more obscure or narrow in nature, instead of 5 alarm fires where someone simply can't play due to a very big problem.
Lately it seems like certain things keep coming up again and again of a more technical nature.
Some examples:
1. Detailed information on how to setup a server (Windows or Linux).
2. Detailed information on mods. CAx features, setup, administration. CRMOD features, setup, administration. Yada yada.
3. Technical information on the different engines -- not from a developer point of view, but from a user's point of view. Like what can engine X do, what can engine X not do, what weaknesses does engine X have, etc.
4. Maybe compiling Quake on Linux.
There might be other examples.
The reason I bring this idea up is that there are questions that will come up over and over again that do not mesh well with a forum-style help resource, but the information should be stored somewhere for everyone's benefit and for editing contributions.
Does a user-contributed Wiki sound like a good idea for the types of information this Quake community needs or do you think it would go unused?
[There is a Quake Wiki by the developer community, but it focuses on technical specifications, history, QuakeC/engine characteristics and modding. This type of wiki would have a very narrow focus on recurring topics that come up here that no other community would have much interest in (server setup, mod administration, proper server promotion, etc.) and would serve more as a living manual/living tutorial for things of importance.]
The questions that come up any more tend to be more obscure or narrow in nature, instead of 5 alarm fires where someone simply can't play due to a very big problem.
Lately it seems like certain things keep coming up again and again of a more technical nature.
Some examples:
1. Detailed information on how to setup a server (Windows or Linux).
2. Detailed information on mods. CAx features, setup, administration. CRMOD features, setup, administration. Yada yada.
3. Technical information on the different engines -- not from a developer point of view, but from a user's point of view. Like what can engine X do, what can engine X not do, what weaknesses does engine X have, etc.
4. Maybe compiling Quake on Linux.
There might be other examples.
The reason I bring this idea up is that there are questions that will come up over and over again that do not mesh well with a forum-style help resource, but the information should be stored somewhere for everyone's benefit and for editing contributions.
Does a user-contributed Wiki sound like a good idea for the types of information this Quake community needs or do you think it would go unused?
[There is a Quake Wiki by the developer community, but it focuses on technical specifications, history, QuakeC/engine characteristics and modding. This type of wiki would have a very narrow focus on recurring topics that come up here that no other community would have much interest in (server setup, mod administration, proper server promotion, etc.) and would serve more as a living manual/living tutorial for things of importance.]
) they would find a lot of those questions answered in either the guides or forums.. in general ppl r just lazy.. and popping a question is just easier then doing a litle searching for the answer.. (in the same way that it is easier to vote for dm6 instead of downloading a missing custom map)
Comment