palt(0b0111111111111111) print(palt()) |
This prints "true". Isn't it supposed to print the bitfield?
On the other hand print(0b0111111111111111) prints 32767
1 comment
Wanted to take a stab at creating blackjack in pico-8. This was surprisingly more complicated than I thought it'd be 😅. Anyhow, from what I've tested it's pretty much there despite some weirdness that might come up in scenarios where you're splitting your hand. If you do give it a spin, feel free to lmk what you think.
Cheers,
l4nk332
0 comments
"Keep It Alive"
280 characters
p,v,t,m,z,f,s=0,0,0,64,128,circfill,sin::_::cls(0)c=3 for i=0,m do if(i==m)c=0 x=m+9*s(i/z+p/z)y=z+4-i+4*s(i/z+t/z)-4*s(p/32)f(x,y,18+c-i/8,c)end f(m,t%m,2,12)for i=0,m do f(x+i/4*s((i+p*5+t)/z),y+7-i/2+i/7*s(p/z),4-i/16,8)end flip()a=.1-rnd(.2)t+=2v=max(-1,min(1,v+a))p+=v goto _ |
2 comments
This is the submission page for the no sprite sheet challenge.
For details about the challenge and all submissions or if you have a question, go to the No Sprite Sheet Challenge page.
If you have a game you would like to submit, comment the link and name of your game.
0 comments
Auto reload a cart if external changes are detected so we don't have to keep pressing ctrl + r, this would help for a faster workflow and help with experimentation.
0 comments
How to reproduce:
- switch to spritesheet
- select pen tool
- draw
- middle-mouse click to pan
- draw does nothing outside the initial zone
1 comment
I made that one minigame from please don't touch anything as a tweettweetcart
Press (X) to drop bomb
(you can also press z, to speed up the plane, since you win by touching the lower right corner)
By the way, the whole cart is public domain.
Do whatever.
0 comments
How to reproduce:
-- outputs zero local b=band(nil,4) -- throws error (arithmetic on field ?) local b=nil<<4 |
6 comments
How to reproduce:
- cart with 3 includes
#include includes/bold.lua #include includes/bigscore.lua ... some other code ... #include includes/tquad.lua |
- reports invalid 'printb' not found (included in bold.lua)
- info produces random output:
- ctrl-r clears the error and runs the cart ok
0 comments
Onslaught
You are the pilot of a small grey craft going through space. You are being attacked by a whole host of munitions that are being flung your way, from missile volleys to plasma melters to anti-flagship beams. This wouldn't be much of a problem for such a nimble ship like the one you have, but you are running on emergency fuel that doesn't have nearly the kick of the regular fuel. No help is coming, so you must hold out for as long as possible.
CONTROLS:
Left Arrow: Go left
Right Arrow: Go right
X: Resets the game (Only works after a game over)
0 comments
Prototype of a chalkboard simulator/math scratchpad. (I might add special characters for that later)
Controls:
- LMB to draw, RMB to erase
- Shift+LMB to draw harder, Shift+RMB to erase more
- Arrows to move cursor
- Tab to move cursor to the mouse position (note: tab is also detected as shift, I don't think there's much I can do about that)
- Keyboard to write
- Enter, Space, Backspace work but slightly unconventionally
- Shift+Up/Down to move cursor half a line up or down - this makes subscripts and superscripts possible
- Mouse wheel to scroll the board (it's infinite downward, but performance is not great yet)
2 comments
 (1).gif)
Maybe the BBS code parsing is lagging behind the Pico-8 release?
https://www.lexaloffle.com/bbs/?pid=74848
Downloaded Code shows fine in pico8 app.
In Code tab that cartridges listing, it just says:
0001
2 comments
A Quick Example
Use the arrow/action keys to move through values and show the outcomes of the new functions:
chr() ord()
0 comments
The code is still messy as heck so I'm going to at least tidy it up a bit before I share it :)
Next step, figuring out what to do about the perspective distortion. On a PS1 I'd just subdivide those triangles. On PICO-8, I'm already at 60% CPU, and while there's still room for optimization and I could always drop to 30 FPS, I don't think throwing more triangles at it is necessarily the right solution here.
Currently it calculates the UV coordinates correctly once per scanline. The first thing I'm going to try will probably be calculating them twice instead, splitting each rasterized line into half.
5 comments
No more compromises and workarounds like Ben's article (https://medium.com/@Powersaurus/3d-floor-rendering-in-pico-8-a01f241db98d). The new tline() function simply lets us draw one row at a time instead of one pixel.
2 comments
Operator >>>= is mentioned in the 0.2 changelog, but the parser does not seem to recognise it:
x >>>= y |
syntax error near '>' |
Apparently the preprocessor changes the code to:
x > = > >> ( y) |
0 comments
