Table of Contents

1. Rating
2. Constructive Criticism
3. Examples
4. Common Pixel Art Terms

First of all, Just giving a rating without any CC is considered spam! Spamming on Sal's can result in warns, so you should always give CC in your posts.

1. Rating

Giving ratings is optional. Many people like to give ratings, and if you do here are some guidelines that might help with rating (written by Celtic, revised by Steve and Doomcreator0):


The easiest thing to do is don't rate the graphics. A rating does really doesn't help say how good the graphic is, as everyone uses their own method. It also is very vague, since no specifics can be given with a simple rating. CC, on the other hand, gives specifics to be worked on that will help the artist improve (below).

Remember that Pixel Art is very hard to make so you should never say that it's terrible unless it is obvious that little to no work was put in. Respect that the artist took the time to create this piece. Unlike many other forms of art, pixel art requires a lot of patience and time because you need to place each part together pixel by pixel which can be quite time consuming.

Remember: Just giving a rating and no CC is spam!

2. CCing

CC stands for Constructive Criticism (sometimes Comments and Criticism). It is to help make the artist better at what they do. Here are some tips when CCing:
1. ALWAYS give CC in your post. When a person makes a topic, they always want CC. Without CC, your post is spam.
2. When you point out errors, always give a solution so that the artist knows how to get better at graphics.
3. End on a positive note, even if you dislike the signature. Find something you like and end with that. Using a smiley can also help. (Thanks Codex for these.)
4. Everyone starts somewhere, and starting out can be difficult. So be easier on newer artists so they don't get scared away from making graphics.
5. If you don't like someone's work that is okay, but keep it respectful. Point out what you don't like, and say why. That way the person knows what not to do in the future.
6. Similarly, if you absolutely love someone's work, point out specific parts that you like so the artist knows what to continue doing. Even if you think that there it's really good, there's always room for improvement.

3. Examples

Here are a few examples of what is allowed and what isn't. Alex has posted a sig of his, and Steve is commenting. We will use Green to denote a good answer and Red a bad reply.

This isn't allowed both because it doesn't give any CC to help the artist and because it is extremely rude. It does not beneficial at all and could have been said in a much better way.

This example is good because Alex now knows how to improve his piece.

This is useless and is spam because Alex now knows that his sig is alright, but doesn't know why or how to make it better. Do not do this, always include a piece of CC in your post.

If you see someone spamming, report their posts so they can be removed. It can be hard to decide what's spam, since some spam-ish posts can actually help, so I'll do my best to leave those that could be considered helpful.

4. Common Pixel Art Terms

• AA= Anti Aliasing
• CC= Constructive Criticism
• Saturated= Bright colors
• Dithering= The use of dots and pixels to blend colors together
• Palette= The selection of colors used in a piece
• NPA= Not or Non pixel art.
• Shading= The use of many colors to give depth and lighting to a piece
• Light Source= The place where the light in a piece comes from
• Ripped= Stolen from somebody else or somewhere else without permission
• Pillow Shading= Shading where there is no defined light source and it is shaded from the center

Thanks!

Nice, I hope people actually read this before ccing or giving a rate.

-Lupin

NICE GUIDE 8/10

At the moment, this is an exact replica of the Digital Gallery topic. Some changes are probably necessary to make this more applicable to pixels (such as changing the examples), so if anybody would like to do that it would be greatly appreciated. I don't pixel so I wouldn't know how to fix it.

Change the CC referring to the render

Alright, you got it.