Tetris Code Challenge

hi mitko, I'm the person behind the tetris challenge. I've thought of doing a challenge that sends every client the same 1000 or so pieces. This is why the API has been designed to be 'stateless'. You are right, right now the same client's score can vary by a huge amount just by the luck of the pieces. I've sat down to draw some round robin challenge that matches up pairs of clients to challenge them with the same pieces - but unfortunately I haven't had any time to code it! :)

Keeping the stack low is the easiest task in the game. Tetris scoring is designed to reward the risks involved in building a high stack.

You can't give 100% repeatable inputs as that opens the door to a fixed, hand-optimized placement pattern. If this is an issue, sample 100 runs and take one from the best, worst, and median cases.

What could be improved is to add some amount of "next piece" data. More data = more ability to use planning instead of probabalistic AI.

Initial configurations with garbage filling the bottom are a good way to test AI robustness, so I would recommend adding a mode for that.

Last, the most prestigious test would be to include the two-player modes. Like C-Robots or Corewars, but with Tetris :)

> I don't think the scoring system is good. According to it the best behaviour would be to build all tetraminos on one side and wait for "I" tetramino to arrive and score 4.

Except, of course, that's exactly the way every single real game of tetris works.