Review Guidelines

Table of Contents


Introduction to Reviewing

Why Review?

Reviews have two main functions, both equally important:
1. They are for other players, to tell them what sort of file it is, how enjoyable it is and whether it is worth downloading.
2. They are for the designer, to tell him/her how well the file works, how you enjoyed it and anything that you think could improve it. They encourage better scenario design.

Why a Review Guide?

The Review Guide is a set of guidelines and rules which, firstly, help channel the reviewer’s thoughts into what to look out for when playing a downloaded file and secondly, to give advice on how to write the best reviews.

What if I ignore it?

We assume you’ve read the guide before reviewing. If you write a review or give ratings that aren’t consistent with the guide, your rating will be removed.

How do I write a Review?

Reviews at Medieval 2: Total War Heaven have one category. You should try to explain in depth why you gave the score that you did. The review can be as long as you like but you should give the author and the person downloading the file information on the file; what did you like? Was the file helpful or enjoyable? Were there problems? What would you like to see improved? Never insult or ridicule a designer. Be honest, but encouraging. Spell and grammar check your review, I can’t stress this enough, very little looks worse than a review chock full of spelling mistakes.

Treat the designer with courtesy

If there are glaring errors in the file which would make for a particularly negative review, it would be nice if you notified the author by email first. This allows them a little time to fix the problems before you submit a scathing review. It is appreciated, however, if you put up a comment with no rating that the file is flawed to prevent people from needlessly downloading it.


Battle Videos

Generally, try not to rate battle videos unless you think it was a really awesome game. Make your review of Battle Videos long enough to thoroughly explain why you gave the rating you did. Try not to rate on skill level, suggestions for what the player could have done are great, reviews stating that “These guys suck.” are not. There are a few rare cases that a couple sentences may be adequate, but these are the exception rather then the rule. The bottom line is that a good review will always be lengthy enough to thoroughly explain the reviewer’s choice of rating. A review consisting solely of “This recorded game was pretty cool” or “This recorded game sucked” simply won’t cut it and will be removed. If you want to post something like that post it as a comment.


Custom maps

Scoring Overview:

You have a choice of rating each file from 1 to 5. Decimal scores can be given if you feel the file isn’t quite a full number value.

5.0 – Outstanding:

Only to be given to the best of maps. There should be no problems and nothing you feel that can be improved upon on.

4.0 – Excellent:

If you think the map you’re rating is better than average, but hasn’t reached the near perfection expected from a 5.0, give this score.

3.0 – Average:

A good, playable map; no glaring problems, but still things that can be improved.

2.0 – Below Average:

Mediocre or with errors or many points that need improving, but the map can be played and completed.

1.0 – Well Below Average:

The lowest score you can give. For example, if there’s bug that makes the map unplayable it’s a 1.0.


Campaigns

Scoring Overview:

You have a choice of rating each file from 1 to 5. Decimal scores can be given if you feel the file isn’t quite a full number value.

5.0 – Outstanding:

Only to be given to the best of campaigns. There should be no problems and nothing you feel that can be improved upon on. If it’s of the same quality of the official campaign map this is the score it should receive.

4.0 – Excellent:

If you think the campaign you’re rating is better than average, but hasn’t reached the perfection of the official campaign map, give this score.

3.0 – Average:

A good, playable campaign; no glaring problems, but still things that can be improved.

2.0 – Below Average:

Mediocre or with errors or many points that need improving, but the campaign can be played and completed.

1.0 – Well Below Average:

The lowest score you can give. For example, if there’s bug that makes the campaign unplayable it’s a 1.0.


Miscellaneous Files

Generally, try not to rate miscellaneous files unless you think it is a really good file. Make your review of Miscellaneous Files long enough to thoroughly explain why you gave the rating you did. There are a few rare cases that a couple sentences may be adequate, but these are the exception rather then the rule. The bottom line is that a good review will always be lengthy enough to thoroughly explain the reviewer’s choice of rating. A review consisting solely of “This is a cool file” or “This file sucked” simply won’t cut it and will be removed. If you want to post something like that post it as a comment.


Modpacks

Scoring Overview:

You have a choice of rating each file from 1 to 5. Decimal scores can be given if you feel the file isn’t quite a full number value.

5.0 – Outstanding:

Only to be given to the best of modpacks. There should be no problems and nothing you feel that can be improved upon on.

4.0 – Excellent:

If you think the modpack you’re rating is better than average, but hasn’t reached the near perfection expected from a 5.0, give this score.

3.0 – Average:

A good, usable modpack; no glaring problems, but still things that can be improved.

2.0 – Below Average:

Mediocre or with errors or many points that need improving, but the modpack can be used.

1.0 – Well Below Average:

The lowest score you can give. For example, if there’s bug that makes the modpack unusable it’s a 1.0.


Saved Games

Generally, try not to rate saved games unless you think it is a really good game. Make your review of Saved Games long enough to thoroughly explain why you gave the rating you did. There are a few rare cases that a couple sentences may be adequate, but these are the exception rather then the rule. The bottom line is that a good review will always be lengthy enough to thoroughly explain the reviewer’s choice of rating. A review consisting solely of “This is a cool file” or “This file sucked” simply won’t cut it and will be removed. If you want to post something like that post it as a comment.


Utilities

Scoring Overview:

You have a choice of rating each file from 1 to 5. Decimal scores can be given if you feel the file isn’t quite a full number value.

5.0 – Outstanding:

Only to be given to the best of utilities. There should be no problems and nothing you feel that can be improved upon on.

4.0 – Excellent

If you think the utility you’re rating is better than average, but hasn’t reached the near perfection expected from a 5.0, give this score.

3.0 – Average:

A good, usable utility; no glaring problems, but still things that can be improved.

2.0 – Below Average

Mediocre or with errors or many points that need improving, but the utility can be used.

1.0 – Well Below Average:

The lowest score you can give. For example, if there’s bug that makes the utility unusable it’s a 1.0.


Questions?

If you have any questions regarding reviews at Medieval 2: Total War Heaven please direct them to Kor.

Thanks to Spineman, Rasher, GillB and everyone else who has worked on the numerous review guidelines all over Heavengames. This review guideline is based on, and incorporates many of their ideas.