Challenge #2: Motion CommotionThe challenge: Make a program that moves a pixel around the screen.
Inputs:
You may either use the arrow keys or wasd for input.
Outputs:
Each time a key is pressed, a pixel moves around the screen as follows:
up/w: up 1 pixel
down/s: down 1 pixel
left/a: left 1 pixel
right/d: right 1 pixel
If a key is held, it doesn't matter. 1 pixel of movement per press.
Scoring:
All non-calculator programs will be scored through this counter:
http://juju2143.ca/golf/Assembly programs will be scored on binary size (excluding the header), and Basic/Axe programs will be scored bn on-calc source size (once again, excluding the header).
Good luck, and may this contest
move you!
Rankings1) lirtosiast - 27 Bytes (TI-Basic)
2) ben_g - 47 Bytes (TI-Basic)
3) Siapran - 139 Bytes (PICO-8)
4) Juju - 144 Bytes (PICO-8)
5) LDStudios - 153 Bytes (PICO-8)
6) Scipi - 154 Bytes (GBA C)
7) alberhrocks - 253 Bytes (Pygame)
8 ) alberthrocks - 397 Bytes (SDL C)
Language Ranking1) TI-Basic (27 Bytes)
2) PICO-8 (139 Bytes)
3) GBA C (154 Bytes)
4) Pygame (253 Bytes)
5) SDL C (397 Bytes)
Show Posts
If you want (and if @pimathbrainiac agrees), we can create a dedicated topic for post-code-golf discussion and solutions. (Topic title would be something like: "POST-MOTERM Code Golf - Discussion and Solutions", or something along those lines.) We can even sticky the new dedicated topic if it helps! Of course, the only condition for this is that you don't necro-post in those old topics (like this one) again...
Same thing with the key repeat and also a perceived loophole that wasn't actually there