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!).
Rant aside, I actually do applaud them. Impressive bit of engineering here.
It's not very playable, but "who cares"?
instead of "0<x%n&", you should be able to do "x%n&&". Works for me on Chrome.
My goal is to shave 2 bytes, so you can change the key handler back to onkeydown. :P
Your proposal does not cover the top edge.
Tron is usually a multiplayer game and the speedup next to light trail you mentioned is missing.
Btw. back in the BBS days there was a Finnish freeware Tron-with-weapons game called "DeLuxe Moposota" (rough translation: moped wars). I have very nice memories of it. It works nicely DosBOX. Here's a youtube clip:
n=632,x=1e6 (or similar)
I suppose you only start approximately in the center, though.
setInterval is set to update in 9 ms intervals - I assume because whilst it's probably more playable (easier) at higher intervals doing so would require additional bytes.
It doesn't mean that a 1 pixel-wide line is invisible, or that you won't see a single white pixel on a dark background.
You mention saving 11 bytes, bringing the total to 212. Then another 9 (seemingly making it 203). But go on to say you saved 2 more bytes, making it 219. I'm confused.
Works fine on Chrome. Use it. And read the rules next time. :)
i once participated in a similar competition only that it was in x86 Assembly, my friends and I brought it down to 70 bytes and the winner from Finland did it in 48!
typos: "exercice" -> "exercise", "brining" -> "bringing"
If you are a vim user, you'll be confused and fell like things are reversed. Sorry :(