Topic: Been too long since I've done much JS hacking... |
|
---|---|
Author | Thread |
Paranoid (IV) Inmate From: USA |
posted 02-14-2007 01:48
Here's a little first-person dungeon thingy in 635 bytes... use the arrow keys to move and turn... and note that you CAN walk through walls, so be careful ;p |
Paranoid (IV) Inmate From: Florida |
posted 02-14-2007 03:28
That's slick. |
Paranoid (IV) Inmate From: USA |
posted 02-14-2007 04:53
To atone for my lack of 256b sins, here's a quickie that DOES fit into my desired size constraint... |
Bipolar (III) Inmate From: Underneath a mountain of blankets. |
posted 02-14-2007 05:43
That is something right there. I'd love to hear an explanation of how you planned it out. |
Paranoid (IV) Inmate From: London |
posted 02-14-2007 14:23
Lovely stuff! |
Paranoid (IV) Inmate From: USA |
posted 02-14-2007 18:27
rukuartic: |
Paranoid (IV) Inmate From: Norway |
posted 02-15-2007 01:02
Nice. |
Paranoid (IV) Inmate From: USA |
posted 02-15-2007 02:42
I'm almost certain that a raycaster could be done in 256b. I'm not sure it can be done with XBM's, however... there's so much overhead with making the XBM, you pretty much lose ~50-60 bytes before you even start. I suppose the ability to do 8 pixels at a go helps reclaim some of those... |
Paranoid (IV) Inmate From: Norway |
posted 02-15-2007 09:28
The 8 pixels at a go may be an advantage for a Dungeon Master like renderer, but I think it becomes more painful for a raycaster. Indeed, cramming a raycaster in 256b sounds tough but possible. I found a ~320bytes version in a backup folder. |
Paranoid (IV) Inmate From: Norway |
posted 02-15-2007 22:59 |
Paranoid (IV) Inmate From: USA |
posted 02-16-2007 00:16
I've been hacking at my dungeon program... I think it'd be MUCH smaller if I could find a way to render XBM's from the <body onload=""> handler (or, even, using setInterval ("...") instead of setInterval (function() { ... })). I find that it always fails, however, due to an "unterminated string literal," which means something must always get escaped improperly... due to having so many nested strings, I suppose. |