Here's my 558-char TweetTweetJam3 entry, including memory poked sfx (thanks to @eruonna for documenting that).

jammerboard

Cart File | Forum Post |

	More cartridges by alexr

More Cartridges [View All]

 

jammerboard

by alexr

Cart #jammerboard-1 | 2019-11-17 | Code ▽ | Embed ▽ | No License

Good but the score starts out negative when you are hit.

It’s a countdown to the next record holding milestone. I couldn’t find the code space. Am at 560 exactly already. Would need an extra 6.

EDIT:
Fixed.

Looking at your code at 598-chars, I think it's possible to make it smaller. Let me see ...

Here it is at 558-chars:

-- jammerboard
-- by alexandre rousseau
s=sub m=mid k=poke f=sfx t=0
function o()r=""for i=1,16 do
e="0" if(rnd()<.03)e="1"
r=r..e
end
return r
end
x=60y=0 a=0 b=1z=-8w=""for i=1,17 do w=w..o()end
d=12868 k(d,138)k(d+1,5)k(d+65,7)::_::t+=1if(btn(0))a=m(-2,a-.2,0)f(1)
if(btn(1))f(1)a=m(0,a+.2,2)
a*=.93if(abs(a)<.01)a=0
a2=abs(a/2)b=3-a2 x+=a y=90 z+=b
if(z>0)w=o()..s(w,1,256)z=-8
cls(7)
?"∧"..t,60,120,6
?"🅾️",x-a,y+a2+2,3
for r=8,136,8 do
for c=1,16 do
if(s(w,r*2+c,r*2+c)=="1")print("▥",c*8,z+r)end end
?"웃",x,y+a2,0
if(pget(x+3,y-1)!=7)run""
flip()goto _

Sweet. Thanks @dw817.

Sure, glad to help.

Played your game a bit. Noticed that it's possible for the player to be positioned where no snow-rifts can hit them. As you are checking vertical scrolling pixels.

Might change the image from

	[8x8]

to

	[8x8]

or somehow combine the two

	[8x8]

I was thinking of that, but that would be too easy. I just need a better way to collision check that fits in 29 characters. :)

Collision improved. if(band(pget(x+1,y),pget(x+5,y))!=7)run""

jammerboard

by alexr

Cart #jammerboard-5 | 2019-11-18 | Code ▽ | Embed ▽ | No License

For some reason those are going through me. Start the game without moving and there are no collisions ?

Hmm. You found a nice bug there. Will look into it.

The red dots are the pixels I pget. Now to fix in 6 chars or less.

Good observation there, @alexr. Nicely debugged.

So then Check the distance between pixels at an EVEN level.

Either one extra pixel to the left for the left or one extra pixel to the right for the right. But not both.

That should fix it.