* reliable and semi-regular with contributions
* articulate and opinionated
* passionate about games

As you've probably noticed, we have articles of two types: features and reviews. Both types must have a semi-professional tone and as close to perfect English as you can (including spelling, punctuation, and grammar) -- British English and American English are equally acceptable. Both must also be accurate and original - do not submit the exact same article from another website, and do not pull facts out of the air. Do your research, if you're going to cite facts and stats. And of course, be ready for a grammar-nazi editor and the criticism of an honest forum-going audience.

First, decide what kind of article yours is. If it's about one particular game, it's probably a review. We do not want features that are about one game in particular -- for example, Game X is Way Overhyped is not a feature. Neither is Game Z is the Best Import Ever. However, if we don't have a review of the game, we'd very much like a well-written review of it, whether it is in fact overhyped or underappreciated. On the other hand, if it's an analysis of various game elements, an interview with a game developer, or an opinionated column on any game-related topic, it is probably a feature. For example, an article about the elements of games that contribute to cult status, or about tips on how to spot undeserved hype, would be fine.

Review tips: Find the game's whole title, publisher, and year of publishing (Gamefaqs.com is a good place for this). At the beginning of the review, include a description of the gameplay and basic genre, even if you think it is self-evident. Spend some time describing the basic player experience. Then, write "The Good" section and "The Bad" section, and in your final analysis, give a short conclusion that sums up your whole evaluation of the game. This should reflect the points you scored it (out of 10). Remember that scores are only in .5 increments (7.5, 8, 8.5, etc). Finally, please include at least 3 screenshots, with captions. You may take these from other websites if you cannot create your own - just include credit for where you found them.

Feature tips: Have a central idea for your discussion. Make sure you are interested in your topic - if you're not interested, how will anyone else be? Don't let it wander too far. If you can bring in other sources (books, journal articles, interview quotes from developers), that's wonderful, but plagiarism is the opposite of wonderful.

That's it! Let me know if you're at all interested!