I have to know about this shadows trick. (How does poke2(63-๐,244)rectfill(x-1,y-1,x+W,y+Z,4)poke2(61-๐,-1,-1) create beautiful, dynamic shadows?)
part 1: bitplanes! basically itโs a pico8 feature that lets me write colors to the screen without completely overwriting the old colors. earlier in the code poke2(-15-๐,...) sets up the palette that makes this work
part 2: flr(63-๐)happens to be equal to 0x5f5e, which is the address I need to poke to configure the bitplanes
putting it together:
poke2(0x5f5e,0x00f4) --enable bitplanes. (poke would make more sense, but poke2 works and we have it saved as a single-letter-variable)
rectfill(x-1,y-1,x+width,y+height,4) --draw the shadow
poke2(0x5f5c,0xffff,0xffff) --disable bitplanes (also disable btn() repeat -- we need to do that anyway, and here is convenient)
I just had an instance where the game stopped auto filling the lowest cards to the top. At one point I had a stack where the 2 descended below the bounds of the screen. I was still able to grab it when I needed it later, but I don't know if that would be what did it?
Not a major issue at all, just thought you may be interested to know!
attached a screenshot of having all my ordered stacks not filling in:
yep, thatโs a known bug! itโs kinda interesting how it happens: if you play the game for longer than 18 minutes, T overflows and becomes negative, so if(T>52)q(14-๐,3)M=T%3 doesnโt run every frame anymore (because T is no longer larger than 52) so M never gets reset to 0, which is necessary to make the cards auto-move.
(why 18 minutes? T+=1 executes once per frame and pico-8 numbers overflow at 2^15, and (2^15 frames)*(1 second/30 frames)*(1 minute/60 seconds) is roughly 18.2 minutes)
If you wait for another 18 minutes, you might think that T would become positive and the cards would start auto-moving again, but before that happens the deck re-deals itself (starting when T reaches 0) and all sorts of weirdness happens.
Anyway, thanks for the bug report! That screenshot is really satisfying to look at :)
Wow... this is amazing. ๐ฎ This looks and plays SO well, considering the limitations. Nice & clean itch page too - glad the instructions were given. (Also - bravo for sharing some awesome char-saving tips for others! ๐) Superb entry ๐
thank you!! and thank you for running this jam; I had a lot of fun making this and golfing it down. (and if I find the time, Iโd like to write up an in-depth devlog dissecting the code!)
โ Return to game
Comments
Log in with itch.io to leave a comment.
I have to know about this shadows trick. (How does poke2(63-๐,244)rectfill(x-1,y-1,x+W,y+Z,4)poke2(61-๐,-1,-1) create beautiful, dynamic shadows?)
thank you! Iโm quite proud of those shadows
part 1: bitplanes! basically itโs a pico8 feature that lets me write colors to the screen without completely overwriting the old colors. earlier in the code
poke2(-15-๐,...)
sets up the palette that makes this workpart 2:
flr(63-๐)
happens to be equal to0x5f5e
, which is the address I need to poke to configure the bitplanesputting it together:
Beat it, and enjoyed it. Your code is a work of art :)
obsessed. i have this bookmarked on my phone. 10/10
I just had an instance where the game stopped auto filling the lowest cards to the top. At one point I had a stack where the 2 descended below the bounds of the screen. I was still able to grab it when I needed it later, but I don't know if that would be what did it?
Not a major issue at all, just thought you may be interested to know!
attached a screenshot of having all my ordered stacks not filling in:
yep, thatโs a known bug! itโs kinda interesting how it happens: if you play the game for longer than 18 minutes, T overflows and becomes negative, so
if(T>52)q(14-๐,3)M=T%3
doesnโt run every frame anymore (because T is no longer larger than 52) so M never gets reset to 0, which is necessary to make the cards auto-move.(why 18 minutes?
T+=1
executes once per frame and pico-8 numbers overflow at2^15
, and(2^15 frames)*(1 second/30 frames)*(1 minute/60 seconds)
is roughly 18.2 minutes)If you wait for another 18 minutes, you might think that T would become positive and the cards would start auto-moving again, but before that happens the deck re-deals itself (starting when T reaches 0) and all sorts of weirdness happens.
Anyway, thanks for the bug report! That screenshot is really satisfying to look at :)
cool
Absolutely mindblowing, really fun to dig through the early version.
But i should point out that it's missing the rectfillwh function ๐
thank you :D
oh, ha, good point! fixed
Wow... this is amazing. ๐ฎ
This looks and plays SO well, considering the limitations.
Nice & clean itch page too - glad the instructions were given.
(Also - bravo for sharing some awesome char-saving tips for others! ๐)
Superb entry ๐
thank you!! and thank you for running this jam; I had a lot of fun making this and golfing it down. (and if I find the time, Iโd like to write up an in-depth devlog dissecting the code!)
Nice work!
thank you!