It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Old thread's been buried beneath all the inane chatter. You guys keep forgetting the important things!

The Wiki is one of these important things! Give us a hand!

We need all your bugs, fixes, mods, patches, compatibility guides, trivia and weblinks and more! Just go to the page for your favourite game and get everything perfect. Look at the pages for Duke Nukem 3D and Jagged Alliance 2 for good examples of what we're looking for.
May I suggest an alternative strategy? In fact I will.

Rather than pushing the community to recall the issues faced (I've helped people, but I don't remember where). Why not push people that have issues to the wiki (once the issue is established as not trivial), advising them to log a known issue, and encourage the solution provider to then update the same source.

The risk is that individual hardware errors will swamp the wiki. However it really needs to be issue driven, so that we can remember what we've discovered.
I can make a page for Thief games!
Oh, wait...

I'm starting summer holidays next week, will try to contribute in some way. In the meantime I'll keep this thread fav'd.
avatar
Thiev: I can make a page for Thief games!
Oh, wait...

I'm starting summer holidays next week, will try to contribute in some way. In the meantime I'll keep this thread fav'd.
Thanks very much! And don't worry, you'll be able to make a Thief page in a few months, I'm sure ;)
avatar
wpegg: May I suggest an alternative strategy? In fact I will.

Rather than pushing the community to recall the issues faced (I've helped people, but I don't remember where). Why not push people that have issues to the wiki (once the issue is established as not trivial), advising them to log a known issue, and encourage the solution provider to then update the same source.

The risk is that individual hardware errors will swamp the wiki. However it really needs to be issue driven, so that we can remember what we've discovered.
I disagree, the risk of swamping the wiki with trivial and meaningless stuff is just too high (just look at the amount of trivial stuff here on the forums, now imagine all that added to the wiki). Wiki editors would spend most of their time wading through "garbage info", just to make the wiki usable. Better to encourage the hashing out of issues in the forums, then once a particular bug is defined and/or solved, update the wiki with that info after the fact.
avatar
wpegg: May I suggest an alternative strategy? In fact I will.

Rather than pushing the community to recall the issues faced (I've helped people, but I don't remember where). Why not push people that have issues to the wiki (once the issue is established as not trivial), advising them to log a known issue, and encourage the solution provider to then update the same source.

The risk is that individual hardware errors will swamp the wiki. However it really needs to be issue driven, so that we can remember what we've discovered.
avatar
cogadh: I disagree, the risk of swamping the wiki with trivial and meaningless stuff is just too high (just look at the amount of trivial stuff here on the forums, now imagine all that added to the wiki). Wiki editors would spend most of their time wading through "garbage info", just to make the wiki usable. Better to encourage the hashing out of issues in the forums, then once a particular bug is defined and/or solved, update the wiki with that info after the fact.
Yes, it is a risk. So I suppose we need people to pay attention to "truly solved" posts, or "truly a bug" posts, and refer them to the wiki. We can't however, just go on there and recall all the fixes we've encountered. That would probably lead to a similar swamp.
Forgot about this. Made a small change, I'll look for more to do later.

So I've never actually edited a wiki before. How can you create redirects? For instance, if I wanted mdk2 to redirect to mdk 2 (no space, which is the actual page title).
Post edited June 27, 2011 by kodeen