Don't let criticism get you down - no-one ever wrote a masterpiece first time out, there is a distinct "learning curve" with this sort of thing.

You have to write and have games play-tested to learn - that's how it is. BUT rather than publicly release work in your formative stages, you might be better off asking for "beta testers" to go through your game and help you refine it, point out problems occur, what doesn't work, what ought to work better etc.

A good beta-tester will give you CONSTRUCTIVE criticism and help you improve - they're worth thier weight in gold to a programmer. I have two people who regularly pull my work to pieces (Take a bow Ali & Rona!) and find 'loopholes' that I bever realised I'd left...

Code, beta test - listen to the critisms, if you can't see how to fix the fault ask here.. then fix it - re-beta test.. fix the new faults..

This 'loop' is the cycle of developing something that is up to "public release" standard - there are no short cuts!

You do like your laughing don't you : )