WHAT MADNESS BE THIS?
This guide seeks to assist map reviewers and other players in the task of giving a good feedback to other mapmakers who seek the former's opinion. This article is an expression of what I personally feel should be done when reviewing maps. This is not an objective, definitive and rigid set of rules to follow when reviewing, but merely a loose *guide*.

WHY START THIS THREAD?
When I first saw the Map Helpers thread on the forums, I thought that it'd be a nice place to get expert help on making my maps better. What I saw instead were some people who were acting like backseat map crew, and laying judgments and opinions on the maps. I personally witnessed this as I submitted a map [that eventually became P6], and all I got was "Gameplay is boring/overused".

It got me into thinking how the group would fail in a short time because they say nothing that tells people how to improve their maps. I decided to join the group to "show them how it's done". Sure enough, when I submitted my application, the ones handling the thread thought I was good enough for a separate role as a sort of manager. I continued my mantra of "giving helpful tips" when giving out reviews.

Soon, my reviews got noticed as being high-quality and arguably the best among the reviewers. I don't want to stop there, though. I want the other mapmakers to learn HOW to give helpful reviews so there wouldn't be a need to consult me. The ultimate way to help other people make maps is to teach other people how to do it themselves.

DOES THIS THREAD APPLY TO ALL?
I have never been map crew, nor do I want to be. Hence, my guide will focus on reviewing maps as a trusted friend or adviser. My assumptions for this guide are as follows:

1. You want to help the reviewee make his/her map better.
2. You do not have the powers of a map crew member.
3. You have a time constraint to give a helpful advice in as little time as you can manage.
4. The reviewee is responsible and reads and applies your feedback.

This thread may perhaps not be helpful enough to those who aspire to some day be part of the map crew, but this can certainly be useful for people who want to know how to give better reviews.

THE MINDSET OF THE REVIEWER
Before starting a review, I keep in mind my goal: TO HELP MAKE OTHER PEOPLE'S MAPS BETTER
This is a very important part of the reviews I make. I understand that not every map I make or review will be promoted to a higher rotation because the standards of the map crew are different from my own. The only thing I can do is point out which parts of the map have flaws and which ones are good and should be kept.

For me, the concept of the map is its essence. A map which in its very essence is a walljump map in concept should not have the walljump challenge removed since it is the core of what the map is. A map of Temple's mother can have all those blocks forming Temple's mother removed and rearranged as long as Temple's mother is still there.

THEREFORE, it is important for the reviewer to understand first what the concept of the map is, and keep in mind to not ask the mapmaker to change the concept unless the concept itself is worthy of deletion [crash, copy, offscreen, etc.]. This is why I keep saying that it's never in a reviewer's place to call a map generic. You are basically telling him to abandon his map. How is THAT helping him make his map better?

There is also a prima facie assumption on my part that my reviewees do not know any sort of mapmaking jargon that isn't used on their own map. Again, the goal is to help the person make his map better, and a key to that is to make yourself understandable. When I see a messy and unaligned map, I assume that its maker doesn't know the concept of alignment, so I point out which grounds in particular are unaligned.

Of course, the assumption being prima facie means that it's disputable. For reviewees I've given tips to before, I assume that they've read my previous review and that they have already learned from my previous example what not to do in maps. Therefore, I don't need to assume once again that they don't know anything.

Last, keep in mind that you're supposed to make the map better based on what you CAN do. If you can no longer find things to improve in the map, it's best to admit that you no longer have anything you want to change in the map. Forcing yourself to suggest things may make the map worse, if you're not careful!

EXAMINING THE MAP
This is another crucial step which requires the reviewer to explore all the details of the map as he can. I have previously asked for XMLs in my review in-game just so I can gain a deeper understanding of what's in the map. For others, I recommend exploring every nook and corner of the map to check for things like hidden grounds, crash lava, hidden cheese/hole and mech triggers. It would be embarrassing to give out a review that doesn't cover everything that the reviewee wanted you to review!

Make sure also that you have a profound understanding of how the map type you're reviewing works. I never give reviews of bootcamp maps because:

1. I never play bootcamp.
2. I've never had a bootcamp map promoted to P3/P13.
3. I don't know how the map crew judge quality for bootcamps.
4. I don't even like bootcamp anyway.

I do give reviews for P6, though. I've had some maps made P6, so I have an idea what things the map crew look for. I also have a respectable amount of knowledge in glitching and Transformice physics. Also, Temple said "Nice map" to me before. I swear I didn't faint.

Anyway, you should use this knowledge of map-building to first break down the different ways that maps can be solved [for shaman maps] and the different ways that the maps can break [for mechanism maps]. Only then can you say that you can give a full review.

One of my assumptions earlier is that my time is limited. Because of that, sometimes it's easier to just remake the map, instead of putting into words what you want the mapmaker to do. Besides, a map sample is sometimes easier to understand than a bunch of words, so this is more effective eitherway. Just keep in mind not to make the mapmakers rely on you to make the entire map for them. Maybe just do the bits you want changed.

For people who haven't had much experience reviewing maps, here are a few things to note in a map:
1. Whether the map looks "deliberate" or "spammed"


This image explains it all. The top one looks messy the grounds are all uneven and there's a bit of cheese spam to the right. The bottom one won't get P7, but at least it looks more "planned out" in comparison because the grounds look like they were carefully planned and plotted on the map.

2. Whether the map is centered


Notice how all of the gameplay elements are on the left half of the map. It doesn't seem logical for the screen to be 800 pixels wide, but all the action is just on the left side.

3. Whether the map has a large useless space


On the same map, we see how the entire right side of the map don't contain grounds, but the shaman won't build on them, either. Certainly a waste of space!

4. Misalignment


Compare how on the top set, there's a tiny gap between the grounds. Not large enough for a mouse to pass through, so why even have the gap there? Also notice how the cheese seems to be floating randomly on the top set while it's "settled down" on the lower set. Further, the grounds on the lower set are neatly lined up at the bottom to suggest that they could form part of the same unit of the map, and how there's a grass skirt on both the grounds on the bottom set.

5. Crash/Offscreen/Copy/etc.
I shouldn't need to mention this, but please check for bad map elements as these will make the map eligible for deletion by a mod or a map crew. For more information on what maps are considered bad, please contact your friendly neighborhood Spidermapcrew.

WRITING THE REVIEW
I generally start my review my saying something nice about the map. Yes, it's true that this is because I want the reviewee to be more accepting of what I say about their maps. How can I expect my review to be helpful if he doens't read my review because of something nasty I said?

Anyway, that's not the only reason. I also try to point out what things I like in the map since the goal of my review is to tell the mapmaker to change some parts of his map. I tell him which things I like so he won't change those parts!

My reviews tend to be longer than those of some others because I get as detailed as I can. I assume as little about the mapmaker's knowledge as possible, and that he can learn through me, so might as well teach as much as I can. Whenenver I see something in a map that I want changed, write these:

1. Why I think that particular part of the map should be changed.
2. Which ground/s or item/s should be removed or cut, as much as possible giving the exact number of pixels.
3. Which ground/s or item/s should be moved to a different place, as much as possible giving the exact coordinates.
4. Which ground/s or item/s should be added, as much as possible giving the exact coordinates and dimensions.
5. Why I think such changes would benefit the map. For example, what would change in the gameplay or aesthetics.

I also use the best English I possibly can, but again with the point of being simple enough to understand. My goal is to communicate with the reviewee, not impress him with my language skills. Of course, this is just my style, and you can use different languages if you deem that such would make for a better review.

Anyway, thanks for reading my quasi-sermon. I probably forgot to mention a few things, so I might edit this from time to time.

Thanks ._.

Great tutorial for reviewing, now people can help others with maps more, creating a stronger bond in the communities! *-*

Thanks guys. I'm curious to learn which parts in particular were of the greatest help, and what else I could say on the opening post to give you guys a clearer understanding.

This'll help a lot seen as I'm only new to the team thanks!
Also CtG I've got a few questions about the team aswel, just for whenever you're on.

Ctg a dit :

This is why I keep saying that it's never in a reviewer's place to call a map generic. You are basically telling him to abandon his map. How is THAT helping him make his map better?

Most reviewers do this to try to improve a reviewee's maps, not their map. If the reviewer doesn't tell them the flaw in the concept, the reviewee is just going to be beating around the bush.

On the other hand, if one is just reviewing a single map then it's fine to not add the "it's generic" comment.

woah, informations too long , but saw all the pictures and readed the others.

Admshumaker a dit :

Great Guide! Who actually Read it all? I did (; I'll be using this alot!

I read it all
EDIT: I'm going to have to go for a more attractive color.

Fatsexybeast a dit :

I dont believe you! :O

But-but-but-but!... He did say it! ;-;

*Bump* Because CtG asked me too.

Very good guide ctg! (:

Very long guide o=o/ nice though.

Agree (DIDNT EVEN READ IT XD(WAS SO LONG)

Bumping it helped, you're welcome CtG.

great great and great rsrs

really helpful

Seeteegee a dit :

Also, Temple said "Nice map" to me before. I swear I didn't faint.

-chuckles-
Even though I might never use these kinds of things, I still read most of your posts about things like these. Then again, I read most of your posts in general. xD
And yeah... I read the whole post. (It might have a secret hidden somewhere!)

Seeteegee a dit :

But-but-but-but!... He did say it! ;-;

What if he meant the part about you not fainting? :o

Anyway! Nice guide with pictures, and with colored texts and stuff~ (And funny pictures of your mouse)