Operation: OHR

-January 20, 2003
-Sep. 30 - Oct. 5
-Aug. 18 - Aug. 24
-News archive

-Wingedmene
-Resistance
-Kidworld
-Soulfire
-Review Archive

-Levels Of Player Control
-Forget The Utopia
-Encouragement
-Reviewer's Guide
-Article Archive

-BTE 3: Ends of the Earth
-BTE 2: Monterey Penguin
-BTE 1: Wandering Hamster
-OHRlympics Results
-Features archive

-What is it?
-Add a game
-Edit your game
-View the list

-Aug. 23 - Aug. 29
-Aug. 16 - Aug. 22
-Aug. 9 - Aug. 15
-Jul. 26 - Aug. 8
-Jul. 18 - Jul. 25

-Zantetsuken MB
-Help Me MB
-Reasonably Septaweekly
-Hamster Republic

-Aethereal
-James Paige

Reviewer's Guide

By: Chaos Nyte

  This is a detailed guide specifically written for RPGs being rated at Operation OHR. Of course, you could always use it a primer for other formats...

  If your reading this, there's a good chance you want to review games for O:OHR, but are confused about how. "Is a 7 an average score? How much of the rating should be opinion, how much hard facts? What requirements do should I have before I go rating other people's work?" Though O:OHR takes any reviews you send them, I doubt you want people thinking your stupid because your review misses important points. Lets start off with the 1-10 rating system.

  10/10- The highest score you can give to a category. Games that deserve this score usually are some how more innovative then anything currently out.
  9/10- A game that makes the category proud, with no flaws in the design of that part of the game. It falls short of 10 simply by not being unique.
  8/10- When the category performs well but suffers from one major flaw or several smaller ones. None of these flaws should detract from the overall game enough to cause the reviewer not to enjoy it.
  7/10- The game performs slightly below great. Usually caused by a good idea that the creator didn't use to its full extent. Some people assume that since 7 can be interpreted as a "C" that this is the average score. Not so in game reviewing.
  6/10- The games good points out weigh the bad, but there's definitely some lack of effort by the creator.
  5/10- Average. The game neither performs good or bad. The reviewer sees the game as boring, or there's a lack of imagination in the design.
  4/10- Usually given when the game performs in a category that irritates the reviewer, but its obvious that the creator at least ATTEMPTED to be interesting.
  3/10- Major flaws prevent the game from being enjoyed, or in some cases played. This could be simply from the creator not playing their own game.
  2/10- Lack of effort is obvious, usually given when the game becomes frustrating to play, i.e. to many battles, poor map design, etc.
  1/10- The creator didn't even attempt to make the game playable. This score is often given in the music department. When a game gets a one in a category, it should tell the creator that this part of their game is simply unacceptable and destroys the integrity of the rest of the game.

  Of course, these are just guide lines for scoring...one of the most important points is...are you ready to be a reviewer?

  Reviewers, as a generalization, are a tough lot. We have to be prepared when we tell the truth about a game and get flamed for it. Most people can't handle that kind of commitment to their writing. Game Creators are always proud of their work, no matter how bad it is and will sometimes to attack the reviewer. These people lash out, blameing their game’s problems or even their own back on to the reviewer. Fellow reviewers will do the same, and the worst thing you can do is to let them influence your decisions. Were mostly loners, slackers by nature, and we all have egos. The trick to becoming a good, even a respected reviewer is to never ignore your enemies slander, but to fight back with well thought out arguments, and to continue writing reviews. The hacks will flame you once or twice, but the real reviewers will stick it out.

  Before you start reviewing RPGs, you should have a good understanding of the Rpgs that have been out in recent years. This helps you identify when plots, music and other highly recognizable aspects of a game have been ripped for some loser's RPG. Music is a gray area though, since most OHRers aren't skilled in composing and it would silly to think that people would learn how to create music just for their game. If your not sure if something’s ripped or not, ask the author.

  So you think you've got what it takes to be a reviewer huh? One that isn't going to be swayed by their peers? Well maybe, but what about being swayed by yourself?

  When most people finish a game, they either loved it or hated it. But if we base a review solely on our opinions and not enough facts, you'll only serve to confuse the readers. Just because you enjoyed doesn't mean everyone else will, especially on those almost great games. I suggest you keep a pad of paper handy when writing your review, letting you make notes about names in the game, and about things you want to mention in your review. I usually split part of the paper into two columns, and mark bad stuff on one side and good stuff on the other. You'll be amazed at how much time this saves when you actually write the review.

  If you find something in the game you enjoyed so much that you think it warrants a higher rating simply because its there, don't. The worst thing you can do is inform the author that you loved something so much you raised his score just for it. Mention how much you liked it, but let it fit into the bigger picture of the category, not making it the focal point. Areas of the game should be seen as a whole, judging the good with the bad, not awarding points for the good. (I know this can happen with the bad things too, but it happens much more often with the good.) Try to keep a level head when you write, otherwise you'll find scores biased without you knowing it.

  After the review, what do you do? Should you just forget about the game and move on?

  I'm not going to talk about the actual reviewing, since as long as you keep your grammar and spelling intact and follow the above guidelines, you should be fine. This pertains more to after the review has been written. I like to send the author a note telling them the review will go up, and either congratulate them on a game well done, or inform that this game didn't make the cut. You can skip the specifics in the letter, but it makes the creator feel at the very least, acknowledged, regardless of the scores their game received.

  That wraps my Reviewer's Guide up, and I'd like to thank Pepsi Ranger for his article on the same topic, he brought up some valid points on the reviewing system, even if they are a tad hard to understand through all those metaphors. I can only hope people will read our guidelines and tips, and write even better reviews.