JavaScript game of Tron in 219 bytes • Hacker News Board

creamyhorror wrote: post #15

I can't see the white line in my browser, just a square of black. I know it's working because I get "game over" if I start the game with i, j, k or l. I'm on Firefox 14.0. Do fix it.

works well on Opera 12

Re: JavaScript game of Tron in 219 bytes

#35

Post by amenghra » Mon, Jun 18, 2012, 12:10 PM UTC

necubi wrote: post #4

It's unfortunate that they decided to save 2 bytes by using onkeyup instead of onkeydown. That choice makes the game nearly unplayable for me. Compare the version in the demo to the one here: http://micahw.com/tron.html (221 bytes). In any case, this is really impressive. It's always fun to see the tricks people employ to get these tiny sizes (smaller than this comment!).

I initially thought it was a cool way to "bend the rules" and save a few bytes, but lots of people told me the same thing! In hindsight I would have instead changed our rules to disallow this :)

Re: JavaScript game of Tron in 219 bytes

#36

Post by amenghra » Mon, Jun 18, 2012, 12:15 PM UTC

dekz wrote: post #6

You have a typo in the first sentence, 'exercice'. I like your presentation of code walk throughs with slides.

thanks for pointing it out, fixed!

Re: JavaScript game of Tron in 219 bytes

#37

Post by amenghra » Mon, Jun 18, 2012, 12:19 PM UTC

epaga wrote: post #5

Clever stuff, thanks! typos: "exercice" -> "exercise", "brining" -> "bringing"

thanks for pointing things out, fixed!

Re: JavaScript game of Tron in 219 bytes

#38

Post by amenghra » Mon, Jun 18, 2012, 12:22 PM UTC

anoother wrote: post #32

Why are the control reversed (mirrored)? Is that normal?

the controls are absolute, with: j goes left l goes right k goes down i goes up.

If you are a vim user, you'll be confused and fell like things are reversed. Sorry :(

Re: JavaScript game of Tron in 219 bytes

#39

Post by amenghra » Mon, Jun 18, 2012, 12:23 PM UTC

itsbits wrote: post #11

219 bytes makes it look gr8 work but lot of bugs...

not bugs; tradeoffs by design :)

Re: JavaScript game of Tron in 219 bytes

#40

Post by amenghra » Mon, Jun 18, 2012, 12:41 PM UTC

Irfaan wrote: post #10

I think I see a way of shaving another byte: instead of "0 My goal is to shave 2 bytes, so you can change the key handler back to onkeydown. :P

There are 5 possible collisions: top edge, left edge, right edge, bottom edge and the tail.

Your proposal does not cover the top edge.