Here's how to better your chances of getting a game/example accepted:

<b>Under construction</b>

First off, these things are no longer accepted, and are grounds for instant denial except under special circumstances (a bribe, for example):

*Resource-pack sprites

*Example edits

*Installers (unless you are well known and trustable, like FredFrederickson, or Omicron1)

*Immediate errors upon runtime

These items are not allowed under any circumstances at all, and can result in warn:

*Non-GM items

*The work is not your own

*Viruses

<h1>General</h1>

I am not out to get you. If I deny your game, it is not because I don't like you. It is for some other reason.

Don't submit work not your own. Submission of work that isn't yours, without due credit and permission results in <i>at least</i> a hefty +4 warn. If you are using their engine and posted a barely edited version, or especially if you are simply claiming someone else's work as your own, you get warned.

The standards in general are lower for things without a preview pic - if your game isn't exactly very good, submit it without a preview. If I see something without a preview that I think deserves to be on the frontpage, I'll give it a preview. The opposite is true too. I can and will remove preview pics if I feel it isn't frontpage material.

Preview pics <i>have</i> to be relevant. Solid color preview pics are removed. Irrelevant preview pics are removed. Irritating preview pics are removed.

Another thing is double check your zip file before posting. Nobody likes downloading 3 mB at 20kbps only to find that the zip is corrupted.

Don't submit like 5 examples at once. First off this shows that you probably didn't spend much time on them. Second off, people like having examples by a variety of people, and so some will be held in-queue for a while to spread them out.

Polish is key - that extra little effort can make the difference between 'oh great another one of these' and 'wow that was cool'

I may deny a game for no other reason than that it sucks.

<h1>Games</h1>

Games should have at least a couple of minutes of gameplay. If I feel that it isn't worth the download, then chances are it will be denied. Many games get denied because I run the game, and I'm more interested in watching paint dry. Its nice that you are making a game, but stop and remember the law of necessary bias:

<i>As the creator of the game, you are necessarily biased in its favor, you will always think it is better than it is.</i>

An intro can be your best friend. It shows that you put effort into it. Also, a nice menu goes a long way into making a game look good. After all, a menu is generally the first thing you see after the splashscreen, and it is how you navigate, too. Don't make the menu too complicated though, because then it becomes a maze, inhibiting the user.

Clearly define your controls somewhere. I cannot stress this enough. There is nothing more irritating than a game that you simple cannot play because the controls are not explained. Nobody likes having to hunt around the keyboard at random mashing buttons in the hope of figuring out that the letter 'F' makes the character jump. Preferably do this somewhere in-game, but also defining them in the game topic is very helpful too.

WIPs need to be demos. A tech-demo is different. A tech-demo has no gameplay, it exists to show basics like running and jumping, and they are generally very boring.

<h1>Examples</h1>

Originality is king for getting examples accepted. If its something I've never seen before, I'll probably accept it. On the other hand, if it is something like 'basic platformer example' or 'particle example' which has been done a billion times before, it will probably be denied unless it is really nicely done.

Examples should be exactly that - examples. An example is useless if I can't use it. Comment your code, make it easy to read. Explain what you are doing, and then do it.

If something makes me go 'oh that was neat' I may accept it no matter how useless it actually is.

DnD is very rarely if ever accepted for an example.

Make the example interesting. If possibly, provide the example, and then along with the 'how to do this' bit, also show how it could be used in-game. Such as if you are making something like a homing AI, make a little minigame to play that shows how to implement your example. An example is useless if you cannot implement it.