Introducing a new series of contests: CWick Contests! (Pronounced like "quick", but with a CW pun. Everyone like puns.) It's much like the Code Golfs we used to do on Omnimaga, as in, the tasks asked should be simple to do, perhaps done in a few hours and you have a week to do so, but it's not a specific task with defined input/outputs you have to make in the least bytes possible, it's more your usual contest/game jam/puzzle where the best one wins. So, each week or so, I come up with a topic, puzzle or constraint and you have to make the best one within a week. You'll be rated and you can win WalriiPoints according to it, which will be shown in your profile. Sounds good enough? Maybe actual prizes will be related to them in the future? Who knows?
This week, I'd go with the most vague topic ever: program anything fun. But there's a constraint: you should be able to send it on Twitter. 140 characters or less, or if you're on a calc, the source should be 140 bytes without the header. You can make anything, a demo, a game, but it should be entertaining. Every language I can run is accepted, but calc languages are evidently advantaged (for obvious reasons). PM me the source to your entries or email them to contest @
codewalr.us (with your username, of course, subject line mentioning the name and number of the contest and a readme) by next Thursday at midnight EDT, have fun! Of course, you should be a member of CodeWalrus so you can claim your prize
The rating will go as well (adapted from the last 4x3 contest, may change anytime):
Spoiler
*(20 pts) Originality: Is it just another tic-tac-toe clone that looks exactly like the 100 other ones in
ticalc.org archives?
*(20 pts) Creativity: How you managed to cram something into the constraints? Was your choice reasonable? Did you used a clever trick?
*(20 pts) Fun: Is it fun? Would you play it again in the future?
*(20 pts) Size, speed, installing & bugs: Is the file size reasonable for what it offers? Does it looks like it's above the constraints? Does it actually respects them? Is it too slow? Is installation easy? Is it bug-ridden?
*(10 pts) Gameplay: How well does it plays? Are controls well-chosen, if any? Is it too slow to be playable?
*(10 pts) Graphics: How well it is shown under such constraints? Does it look well-polished?
And if you have ideas for a future quick contest, if you have a suggestion, or if there's anything not clear, please PM or email me about it
(EDIT: Changed name of the contest for DJ's pun, I like it
)
EDIT2: More rules! You can't release the source before the contest ends, it's preferable to keep all the 140 bytes in the same file (no cheats and workarounds!), yes, 140 bytes is the source size (bonus if you keep the compiled program under 140 bytes too!), unless you go with PICO-8 (or any tokenized language like 83+ BASIC/Axe), then it's 140 tokens. Anyway, I should be able to figure out how to compile your program with only your 140-byte source file alone and the knowledge of the standard libraries used (if you provide a makefile or something like that it isn't counted, but don't abuse compiler options or putting additional stuff in libraries). I may or may not run the source through a number of tests, such as compiling it and executing it, but also checking the algorithm and running it through various alternatives compilers and interpreters, if any, or just generally messing with it.
EDIT3: Vote! The entries are
here!
