Log In  

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

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

P#69964 2019-11-17 11:40 ( Edited 2019-11-17 23:58)

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

P#69969 2019-11-17 15:18

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.


P#69971 2019-11-17 15:43 ( Edited 2019-11-17 23:58)

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"
return r
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)
a2=abs(a/2)b=3-a2 x+=a y=90 z+=b
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
flip()goto _
P#69998 2019-11-18 02:15

Sweet. Thanks @dw817.

P#69999 2019-11-18 03:18

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
or somehow combine the two

P#70001 2019-11-18 03:50

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. :)

P#70003 2019-11-18 03:58

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

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

P#70006 2019-11-18 05:03

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

P#70009 2019-11-18 06:01 ( Edited 2019-11-18 07:04)

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

P#70016 2019-11-18 12:41

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

P#70017 2019-11-18 12:46

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.

P#70020 2019-11-18 16:55 ( Edited 2019-11-18 16:56)

[Please log in to post a comment]

Follow Lexaloffle:          
Generated 2024-04-19 08:22:24 | 0.022s | Q:32