pancelor [Lexaloffle Blog Feed]

Open URL in browser (export plate)

Sat, 28 Jun 2025 06:31:30 UTC

Here's a snippet I made to launch webpages in the player's browser from within a pico8 cartridge. It only works in html exports, because it uses the GPIO pins to send the url to a custom html template.

Example (player perspective)

For an example of this in action, play https://pancelor.itch.io/make-ten-deluxe and click "info" on the title screen. A paper will pop up with some clickable URLs on them, which will load new tabs when clicked.

Setup

folder config, open the "plates" subfolder, copy the default template (TODO: is there a default template, or did I make it myself by exporting a cart and then undoing pico8's ##js_file## / ##label_file## replacement?)
Find var pico8_gpio = new Array(128); (it's near the top, around line 30)
Replace it with this:

var pico8_gpio = new Proxy(new Array(128),{
    // pancelor's gpio-url, https://www.lexaloffle.com/bbs/?tid=149864
    set(arr, pin, value) {
        // console.log(typeof pin, typeof value); // string number 0.o
        pin = parseInt(pin,10);
        arr[pin] = value;

        // write url chars to pins 1,2...
        // then set pin 0 to ord("u") to open the url
        if (pin==0) {
            var code = String.fromCharCode(value);
            if (code=="u") {
                // read URL (and reset pins to undefined)
                var url = "";
                for (var ii = 1; ii < 128; ii++) {
                    var state = arr[ii];
                    if (state==undefined) break;
                    url += String.fromCharCode(state);
                    arr[ii] = undefined;
                }
                arr[0] = undefined

                // open
                if (!url.startsWith("http")) url = "https://"+url;
                console.log("opening gpio url:",url);
                window.open(url,'_blank');
            } else {
                console.log("unknown gpio command:",code,arr[0]);
            }
        }
    }
});

Save your new template as plates/gpio_url.html
Inside your cart, use this function to open a URL in the player's browser:

function open_external(url)
  assert(#url<=127)
  poke(0x5f81,ord(url,1,#url))
  ?"\^!5f80u" --must be last
end

Export your cart with export -f mygame.html -p gpio_url

Example cart

-- export -f test.html -p gpio_url

function _update()
 if btnp(4) and not launched then
  launched=true
  open_external("pancelor.com")
 end
end

function _draw()
 cls(launched and 2 or 1)
 print(launched and "done" or "press z",54,64,7)
end

function open_external(url)
 poke(0x5f81,ord(url,1,#url))
 ?"\^!5f80u" --must be last
end

License

CC BY 4.0. Just leave the "// pancelor's gpio-url <link>" comment in the code itself and you can use this for anything. (I think CC BY normally means you need to give more credit than just leaving a code comment, e.g. a shoutout in the game's description or something, but in this case I'm not bothered about it.)

Make Ten Deluxe

Wed, 21 May 2025 14:02:02 UTC

Make Ten Deluxe (demo v1.3)

by pancelor

[Click to Play]

tl;dr: use left-mouse to play, this is a free demo, the full game is on itch. have fun!

Make Ten Deluxe is an expansion pack that builds on the original Make Ten, featuring 35+ variant modes. Some modes modify the rules slightly in ways that significantly change the flavor of the game, some modes are particularly puzzley situations for you to solve, and some modes are too strange and specific to describe.

There's something for everybody to love: each of the game's dozens of modes were carefully chosen to be interesting, surprising, or otherwise delightful.

Make Ten Deluxe! Featuring...

Drop10: Make10 + gravity: new numbers fall from the sky
MakeHeaven: Make10 with wildly different RNG
Make42: exactly what it sounds like
MakeTen: not at all what it sounds like
MakeWar: explosions! made of numbers! (does that count?)
BlueGoo: Make10 with negative numbers
MakeChä̶̝̣́̈́o̴̯͊s̶͉̟͒: ???
and many more!

The demo (playable in-browser, above) features a handful of these modes, including a daily mode, a mode with negative numbers, "MakeX", and a mode with no timer and infinite undo. If you're left wanting more, you can purchase the full game for Linux, Mac, Windows, and PICO-8.

The full game is downloadable, but I haven't figured out how to port it mobile devices yet. I'm hoping to add an Android APK file in the future, and I'll see if there's anything I can do about iPhone support (though that seems unlikely). I hear there are PICO-8 or windows emulators that run on phones -- I'll update this section later when I've done more research.

The whole game can be played with the Left Mouse Button: click and drag to select groups of numbers. If they add up to 10, they'll be removed from the board, increasing your score.

In some modes, you can press Z to undo. You can pause the game with Enter or P. There are volume controls in the pause menu, and ctrl-plus, ctrl-minus, and ctrl-m also control the volume.

Game by pancelor, itch page by tally and pancelor.

An homage to Fruit Box by GameSaien, circa 2010.

Made using PICO-8, shrinko8, Sublime Text, Aseprite, Krita, Obsidian

Thanks to all my playtesters, and especially to: biggiemac42, Dad, droqen, Gabe, incnone, polychotomous, q1, Roland, tally, Waporwave

patches

Mon, 19 May 2025 09:50:23 UTC

patches

by pancelor

[Click to Play]

An interactive quilt for TTJ10, made in <500 chars of code.

More toy than game; think of it as a jigsaw puzzle, if you like.

controls

Left click to pick up a patch, left click again to drop it.

Also hosted on itch.io

Fast loops

Mon, 31 Mar 2025 09:07:04 UTC

There are many ways to loop over an array-style table. For example:

local tab = {10,20,30,40}

-- method 1
local calc1 = 0
for i,elem in ipairs(tab) do
  calc1 += i*elem
end

-- method 2
local calc2 = 0
for i=1,#tab do
  local elem = tab[i]
  calc2 += i*elem
end

Which way is fastest? Well it often doesn't matter, since the work inside the loop usually far outweighs the cost of the loop itself. Or tokens might matter more to you than speed. But in some situations you want your code to be as fast as possible, and that means minimizing the overhead from the loop itself.

Setup

So, which way of looping is fastest? Here are the methods we'll compare:

function for_i(tab)
 for i=1,#tab do
  local x=tab[i]
  -- do some work
 end
end

function for_all(tab)
 for x in all(tab) do
  -- do some work
 end
end

function for_ipairs(tab)
 for i,x in ipairs(tab) do
  -- do some work
 end
end

function for_inext(tab)
 for i,x in inext,tab do
  -- do some work
 end
end

function for_each(tab)
 foreach(tab, function(x)
  -- do some work
 end)
end

function while_i(tab)
 local i = 1
 while i<=#tab do
  local x = tab[i]
  -- do some work
  i += 1
 end
end

function while_isize(tab)
 local i,size = 1,#tab
 while i<=size do
  local x = tab[i]
  -- do some work
  i += 1
 end
end

-- note: issues if tab is empty
function repeat_i(tab)
 local i = 1
 repeat
  local x = tab[i]
  -- do some work
  i += 1
 until i>#tab
end

-- note: issues if tab is empty
function repeat_isize(tab)
 local i,size = 1,#tab
 repeat
  local x = tab[i]
  -- do some work
  i += 1
 until i>size
end

edit: In my analysis below I'll refer to some extra methods (mainly based on reader comments). I haven't updated the graph/chart for these methods:

I used my cycle counter to measure how long each function takes to run on arrays of various lengths -- every length from 0 to 80. The results are uninteresting after length 25, so I've truncated the table and chart below.

Here's my measurement code. It prints out a csv of cycle data to the host console. It's not too interesting to run the cart, but here it is if you want to reproduce or check my results:

loop_overhead

by pancelor

[Click to Play]

Results

I ran my measurement cart (#loop_overhead, above) on PICO-8 0.2.6b for Linux. Here's the data; higher numbers are slower/worse.

len,while_i,for_each,while_isize,repeat_i,repeat_isize,for_i,for_ipairs,for_inext,for_all
0,5,30,5,8,8,8,18,9,21
1,14,51,12,8,8,12,20,11,36
2,23,57,19,15,13,16,22,13,36
3,32,63,26,22,18,20,24,15,36
4,41,69,33,29,23,24,26,17,36
5,50,75,40,36,28,28,28,19,36
6,59,81,47,43,33,32,30,21,36
7,68,87,54,50,38,36,32,23,36
8,77,93,61,57,43,40,34,25,36
9,86,99,68,64,48,44,36,27,36
10,95,105,75,71,53,48,38,29,36
11,104,111,82,78,58,52,40,31,36
12,113,117,89,85,63,56,42,33,36
13,122,123,96,92,68,60,44,35,36
14,131,129,103,99,73,64,46,37,36
15,140,135,110,106,78,68,48,39,36
16,149,141,117,113,83,72,50,41,36
17,158,149,124,120,88,76,52,43,38
18,167,157,131,127,93,80,54,45,40
19,176,165,138,134,98,84,56,47,42
20,185,173,145,141,103,88,58,49,44
21,194,181,152,148,108,92,60,51,46
22,203,189,159,155,113,96,62,53,48
23,212,197,166,162,118,100,64,55,50
24,221,205,173,169,123,104,66,57,52
25,230,213,180,176,128,108,68,59,54

And here's a chart:

(For colorblind folks, the labels are stacked in order of their performance at length=25)

Commentary

for_inext()

The clear winner here is for_inext() -- it's the fastest in most situations, you get access to both i and x inside the body of the loop, and its token count is nearly the best as well (just 1 token more than for_each()).

Downsides: it's an unusual bit of code that might trip up other people reading it. inext() is defined by PICO-8, not Lua, if that matters to you. Compare against Lua's next(). But these downsides seem unimportant if all you want is to make one particular PICO-8 cart run as fast as it can.

for_all()

However, when looping over medium/large arrays (length>=14), for_all() is a bit faster than for_inext() -- exactly 5 cycles faster when length>=16. But for_all() is much slower than for_inext() up until that breakpoint. When length=2, for_all() takes 36 cycles versus for_inext()'s 13 cycles -- nearly 3 times as slow!

Other possible downsides: index i is not accessible inside the loop.

all() has some special tricks that let you delete while iterating (within limits), which may be considered an upside or a downside. See the conversation starting here for details.

for_all() has the strangest timing out of all the options tested. At low array lengths it performs second-worst, but at medium/high array lengths it performs best.

for_i()

Despite feeling like one of the more natural ways to write a loop, for_i() is noticeably slower than for_ipairs()/for_inext()/for_all(). Specifically, for_i() costs 4 extra cycles for each extra iteration, compared to 2 cycles for the best methods. For large arrays, the choice between for_ipairs()/for_inext()/for_all() mostly doesn't matter, but for_i() will be noticeably worse.

for_each()

for_each() has the lowest token-count but is one of the slowest options here. Its only advantage is its token-count (it beats for_inext() by a single token), but I would still generally prefer for_inext().

edit: foreach() is actually faster (!) than all() in one very specific case: when the body of the loop is a single function call. Details:

slope change in for_each() / for_all()

At length 16, the slope of the for_each() and for_all() lines change slightly. This isn't a mistake in the measurement; all() artificially adjusts its cost starting at length 16, and foreach() is a thin wrapper around all() and so it inherits this cost weirdness.

while_isize() versus while_i()

while_isize() is faster than while_i(), but for_isize() is 1 cycle slower than for_i(). This is because while-loops re-evaluate their condition every iteration, but numeric for-loops only evaluate their bounds once.

while_i() versus repeat_i()

I was surprised to see that repeat_i() is quite a bit faster than while_i(). Why are they so different? It helps to look at the generated Lua bytecode using a tool like https://www.luac.nl/ -- you can see that while_i() uses an extra JMP instruction that can be avoided with repeat_i().

As you might expect, goto-based loops perform exactly the same as while_i()/repeat_isize()/etc, since they compile to the same bytecode or similar.

for_next() / for_pairs()

for_next() and for_pairs() perform exactly the same as for_inext() and for_ipairs(), respectively. It would be a bit odd to loop over an array-style table using next()/pairs() instead of inext()/ipairs() with their guaranteed iteration order, but it's good to know there's no performance difference. (and nice to know that looping over key-value tables is quite fast)

Conclusion

I see four viable options for looping:

for_inext() is generally the fastest method:
for i,x in inext,tab do -- do some work end
With arrays of length 2 to 13, it's the fastest option, but it performs excellently at any array length. At higher lengths, it's 5 cycles slower than for_all() -- 5 cycles for the entire loop, not 5 cycles per iteration. Most other methods have additional cost per-iteration, as shown by their higher slopes in the chart. At high array-lengths the differences between for_inext(), for_ipairs(), and for_all() become less and less significant -- they each only cost 2 extra cycles for each extra iteration.
As a nice bonus, for_inext() is only 1 token worse than the most token-efficient method, for_each().
With arrays of length 14+, for_all() is slightly faster than for_inext():
for x in all(tab) do -- do some work end
However, be aware that all() is much slower on arrays of length 0 to 13. (This may not matter, since the arrays are so small.)
For carts with extreme token-limitations and no problem with much larger loop overhead (3-4x), foreach() is slightly better than the alternatives. Separately, foreach() is slightly faster (than all other options!) when the body of the loop is a single function call that you can't inline for some reason.

And finally, option 4: If you don't have any particular hard limits you're up against, loop however you like! Whatever lets you get your ideas on the page without getting distracted by unimportant timing details. You're trying to make a game here, not a pretty piece of code. This is most likely the scenario you are in!

Even if you know you want fast code, the first step is to measure your code and find out which parts are slow, and the answer probably won't be the loop overhead. Loop overhead is easy to measure, but that doesn't make it important. Don't link people to this post saying "pancelor says you have to loop THIS way instead of THAT way", it usually just doesn't matter. But if it ever does matter, or if you're curious (like I was) about how much it matters, then hey, this is the post for you. Hope it was interesting!

Web clipboard broken (0.2.6c dev8)

Mon, 10 Feb 2025 02:28:58 UTC

repro steps:

run cart bitplane_grid-3 in the web player
press ctrl-c
paste into an external text editor

expected behavior: clipboard should have poke(0x5f5e,0xff) in it
actual behavior: clipboard is unchanged (my specs: linux, firefox, 0.2.6c dev8)

(cart from here)

bitplane_grid

by pancelor

[Click to Play]

Maybe this is a known bug, which is part of why it's "0.2.6cdev8" instead of "0.2.6c"? But here's a ping just in case you don't know about it @zep. (web clipboard stuff seems like a huge pain, I don't envy you trying to fix it...)

The cart has some debug print statements -- open the browser dev tools and you can see it print out "copying str:" right before calling printh(str,'@clip'). I noticed there's no red "press c to copy" prompt that the web player used to show, maybe that's a clue.

I also noticed that a lone ctrl press is now caught by stat(31); my debug logging prints ch code ソ 218 on web, but completely misses this key press in the desktop app (linux, 0.2.6b). I think that may be a separate bug? Shift and alt are not caught in the same way, and I don't think I'd care about a bare ctrl press while reading text input

Toggle Music mod for any cart

Mon, 03 Feb 2025 08:36:48 UTC

Sometimes it'd be nice to mute the music in a game you downloaded from the BBS, but not mute the sound effects. Maybe their music isn't to your taste, maybe you've played it way too much and now you want to listen to your own music instead; there are plenty of reasons.

One easy trick is just typing music=min to kill the music completely. If you'd rather be able to toggle the music on and off, here's a quick snippet:

-- pancelor music toggle v4
-- https://www.lexaloffle.com/bbs/?tid=146963
_music_fn,_music_last=music,-1
function music(...)
	if _music_muted then
		_music_last=... --save 1st arg
	else
		_music_fn(...)
	end
end

menuitem(5,"♪music",function()
	_music_muted=not _music_muted
	if _music_muted then
		_music_fn(-1,500)
		menuitem(nil,"…music")
	else
		_music_fn(_music_last)
		menuitem(nil,"♪music")
	end
	return true
end)

It should work for most carts, just paste it onto the end of the cart's code. It might be convenient to use this as a dev as well (not just as a player) -- it remembers the last call to music() and re-calls it when the player unmutes.

pancelor's postcarts

Sat, 02 Nov 2024 12:52:43 UTC

pancelors_postcarts

by pancelor

[Click to Play]

This is a collection of my various tweetcarts and other code art, circa 2019-2023. Most of my non-interactable postcarts etc are in here, including a few that are only included as a part of this collection. 25+ fun little animations!

(I posted this on itch a while back but forgot to post it here until just now, as I was reading zep's release notes for the BBS's new postcart feature. So I'm uploading my postcart gallery now; better late than never!)

Controls

These carts are non-interactive animations for you to look at. The only interaction is opening the menu (Enter/P), where you can change the active cart.

Press left/right on the cart name to manually swap out the active cart
The carts will auto-advance to a random cart every 20~60 seconds. You can disable this by setting "Cycle: no" in the menu

An example of navigating the menu:

There are 25+ carts in this thing, be sure to check out at least one of these before you leave: system restored, adrift, wormys, weird bug, firefly spring

Hope you enjoy!

Technical details:

Search for carts={ to find the source code for each cart (inside the "script" function of each table entry). The code isn't very readable, but that's where you can find it. There are links to the canonical versions elsewhere, which you can try to pick apart using my twiddler tool, if you'd like.

For this gallery cartridge, I had to set up this whole harness that runs each cart in a sort of sandbox, letting them act as intended without messing with each other. There were lots of finicky parts to this:

resetting the draw state after each cart
using coroutines to allow carts to use goto and other unusual control flow
saving a screenshot of the initial pico-8 state, for the carts that depend on it
redefining the time() function so that carts would think they started at t=0
saving a copy of the values of special characters like 🐱, in case carts redefine those values
etc, etc

I had to make some minor changes to some carts (mainly changing flip() calls to yield() calls) but mostly I was able to wholesale copy-paste them directly into this gallery cartridge, which felt pretty neat.

music desync (0.1.1b)

Thu, 22 Aug 2024 23:26:15 UTC

@zep o/ thanks for fixing the sfx arpeggio effects! here's another audio bug for you:

The music for embedded BBS carts has a noticeable music desync in some cases (the individual tracks sound out-of-sync from each other). I noticed it on linux+firefox with my music visualizer demo cart, reproduced here for convenience:

datufbuyi

by pancelor

[Click to Play]

Individual tracks desync from each other; it consistently happens after the song switches from pattern 3 to pattern 4. The second screenshot here shows me catching it right when it happens:

That last number (the one that desyncs by 11 ticks for me) is stat(400+i,11). I believe this represents the number of ticks played on channel i for the current pattern.

This also happens locally in the linux executable, but the tracks only desync by a single tick. I can't hear it, but you can see it by pausing after pattern 4.

I think this is new as of 0.1.1, but it's possible I just didn't notice in 0.1.0h when I uploaded this cart, or the desync might be less consistent than it currently seems

sfx/music data layout

Fri, 02 Aug 2024 22:56:07 UTC

Inspired by https://www.lexaloffle.com/bbs/?tid=2341, here's a description of how sfx and music are stored in Picotron. (Well, there's not much description here yet, just some helpful code. I'll add to this over time)

The data can be in unusual custom formats. The header data is supposed to help in these cases and is accounted for in this code (with some asserts to crash if the data format is unknown). But for most people using this code, the data will be in the standard format.

Library

Code:

-- sfx/music data wrangler
-- by pancelor

-- The docs call this the "index", I call it the "header"
-- https://www.lexaloffle.com/dl/docs/picotron_synth.html#Index
function sfxheader_read()
	local num_instruments, num_tracks, num_patterns, flags = peek2(0x30000, 4)
	-- ...8 unused bytes here...
	local insts_addr, tracks_addr, patterns_addr, unused1 = peek4(0x30010, 4)
	assert(unused1==0,"bad sfx header 1")
	local tick_len, def_len, def_spd = peek2(0x30020, 3)
	local def_spd2, unused2, unused3, unused4 = peek(0x30026, 4)
	-- TODO def_spd2 v. def_spd?
	assert(unused2==0,"bad sfx header 2")
	assert(unused3==0,"bad sfx header 3")
	assert(unused4==0,"bad sfx header 4")
	return {
		num_instruments = num_instruments,
		num_tracks = num_tracks,
		num_patterns = num_patterns,
		flags = flags, --0x1 use default track indexing (base+0x20000, increments of 328 bytes)
		insts_addr = insts_addr, --relative address of instruments
		tracks_addr = tracks_addr, --relative address of track index
		patterns_addr = patterns_addr, --relative address of pattern data
		tick_len = tick_len, --in 1/16ths of a sample at 44100Hz [0 means 5880 -- 120 ticks / second]
		def_len = def_len, --used by patterns that do not have a default length specified
		def_spd = def_spd, --used by patterns that do not have a default speed specified
		def_spd2 = def_spd2, -- ??
	}
end

function pattern_read(i)
	local base = 0x30100 + sfxheader_read().patterns_addr -- normally 0x30100
	local addr = base + i*20
	local tracks = { peek(addr, 8) }
	local flow_flags, channel_mask = peek(addr+8, 2)
	local len = peek2(addr+10)
	-- ...8 unused bytes here...
	return {
		tracks = tracks, -- array with 8 track ids
		flow_flags = flow_flags, -- 0x1 loop forward, 0x2 loop backward, 0x4 stop
		channel_mask = channel_mask, -- 0x1 is tracks[1] unmuted? 0x2 is tracks[2] unmuted? 0x4 => tracks[3], 0x8 => tracks[4], ... 0x80 => tracks[8]
		len = len, --TODO: how does this interact with track length and header def_len/def_len2?
	}
end

function track_read(i)
	local header = sfxheader_read()
	assert(header.flags&1==1,"unknown track format")
	local base = 0x30000 + header.tracks_addr -- normally 0x50000
	local addr = base + i*328
	local len = peek2(addr)
	local spd, loop0, loop1, delay, flags, unused = peek(addr+2, 6)
	assert(unused==0,"bad sfx track")
	-- note: if len<64 then some of this data is irrelevant:
	local pitches = { peek(addr+8,64) }
	local instruments = { peek(addr+72,64) }
	local volumes = { peek(addr+136,64) }
	local effects = { peek(addr+200,64) }
	local effect_params = { peek(addr+264,64) }
	return {
		len = len,
		spd = spd,
		loop0 = loop0,
		loop1 = loop1,
		delay = delay,
		flags = flags, --0x1 mute
		-- 64-length arrays, 1 entry per note:
		pitches = pitches,
		instruments = instruments,
		volumes = volumes, -- a 0xFF entry means muted
		effects = effects, -- stored as their ascii code -- retrieve with ord()
		effect_params = effect_params,
	}
end

-- an alternate version of track_read that extracts a single row
-- ti: track index
-- ri: row index
function track_row_read(ti,ri)
	local header = sfxheader_read()
	assert(header.flags&1==1,"unknown track format")
	local base = 0x30000 + header.tracks_addr -- normally 0x50000
	local addr = base + ti*328 + ri
	return {
		pitch = peek(addr+8),
		instrument = peek(addr+72),
		volume = peek(addr+136),
		effect = peek(addr+200),
		effect_params = peek(addr+264),
	}
end

function instrument_read(i)
	local base = 0x30000 + sfxheader_read().tracks_addr -- normally 0x40000
	local addr = base + i*0x200
	assert(false,"not implemented")
	-- see https://www.lexaloffle.com/dl/docs/picotron_synth.html#Index
	-- or read /system/apps/sfx.p64/data.lua:clear_instrument() for info
end

-- i: channel index 0..7
function channel_current_track(i)
	return stat(464,0)>>i&1~=0 and stat(400+i,12) or -1
end
-- i: channel index 0..7
function channel_current_row(i)
	return stat(464,0)>>i&1~=0 and stat(400+i,9) or -1
end
-- number of ticks played on current pattern
function channel_ticks_played(i)
	return stat(400+i,11)
end
--currently playing pattern, or -1
function current_pattern()
	return stat(466)
end

Sources:

/system/apps/sfx.p64/data.lua
https://www.lexaloffle.com/dl/docs/picotron_synth.html#Index

Demo cart

Here's a tiny music "visualizer" that uses this library:

datufbuyi

by pancelor

[Click to Play]

License

This library is licensed as CC BY 4.0 (basically, credit me and link back to this post, and you can use this code for anything)

(This does not include the music playing in the demo cart. The music is by @iaoth and is licensed as CC BY-NC-SA 4.0 -- see https://www.lexaloffle.com/bbs/?pid=51460)

spritesheet remapping 0x5f54 crashes after reboot

Wed, 19 Jun 2024 01:38:37 UTC

@zep o/

0.2.6b / linux:

launch pico8 executable
run poke(0x5f54,0x80) (in the console)
run reboot
run poke(0x5f54,0x80) (copied from the 0.2.6 release notes)
the executable crashes

Step 2 is optional -- it still crashes in step 5 if you skip step 2
In Step 4, running poke(0x5f54,0x60) instead does not crash.

I'm not sure how to get a stacktrace on my machine, or if it's even possible. this is the best I know how to do:

> coredumpctl debug
           PID: 12604 (pico8)
           UID: 1000 (pancelor)
           GID: 1000 (pancelor)
        Signal: 11 (SEGV)
     Timestamp: Tue 2024-06-18 18:51:34 PDT (3min 17s ago)
  Command Line: /home/pancelor/.config/itch/apps/pico-8/pico-8/pico8 -root_path /run/media/pancelor/data/Users/pancelor/Documents/pancelor/src/pico8/
    Executable: /home/pancelor/.config/itch/apps/pico-8/pico-8/pico8
 Control Group: /user.slice/user-1000.slice/[email protected]/app.slice/app-pico8-b4acdb07c9cf4629b15a6b78f024fa7f.scope
          Unit: [email protected]
     User Unit: app-pico8-b4acdb07c9cf4629b15a6b78f024fa7f.scope
         Slice: user-1000.slice
     Owner UID: 1000 (pancelor)
       Boot ID: bc016245c64e47f1b3755470beec5d96
    Machine ID: 4eec57f899074b4eb49773a72b91be1c
      Hostname: pancelor-manjaro
       Storage: /var/lib/systemd/coredump/core.pico8.1000.bc016245c64e47f1b3755470beec5d96.12604.1718761894000000.zst (present)
  Size on Disk: 10.3M
       Message: Process 12604 (pico8) of user 1000 dumped core.

                Stack trace of thread 12604:
                #0  0x00000000004734e6 n/a (/home/pancelor/.config/itch/apps/pico-8/pico-8/pico8 + 0x734e6)
                ELF object binary architecture: AMD x86-64

Failed to invoke gdb: No such file or directory

tl;dr: SEGV at 0x734e6

coroutine stack pollution

Sun, 02 Jun 2024 04:59:16 UTC

wutewuwiho

by pancelor

[Click to Play]

hi @zep! This cart should not error, but it does (pico8 0.2.6b / linux)

-- wrap everything in func _init to fix it
--function _init()

--uncomment this to fix it
--poke(0,0)

--make this local to fix it
coro = cocreate(function()
  -- uncomment this to fix it
-- local x=1
  for i=0,32000 do
    -- flr() is arbitary here; it's
    -- just a func that should
    -- return only one value
    local rets = pack(flr(i))
    if #rets~=1 then
      local str="flr rvals:"
      for i,v in ipairs(rets) do
        str ..= "\n\t"..i..": "..tostr(v)
      end
      str ..="\nstat(1): "..stat(1)
      print(str.."\n")
      assert(false)
    end
    -- uncomment this to fix it
--    if flr==flr then end
  end
end)

cls()

--remove second param to fix it
assert(coresume(coro, "uh-oh"))

print"no errors"

It seems like the string "uh oh" is being popped from the stack in a completely wrong place.

See also https://www.lexaloffle.com/bbs/?tid=141267 , a picotron coroutine bug. This cart is a modified version of @jesstelford's code there. I'm unsure if the root cause is related, but the result is the same.

Notably, this cart consistently crashes every single time (unlike the picotron version), and seems directly related to stat(1) going over 1.0

I marked a bunch of things you can uncomment to make this test case pass. (there are some very weird things you can do to make it suddenly work)

I'm fuzzy on the details, but it seems like something like this is happening:

coresume(coro, "uh-oh") pushes "uh-oh" to the internal lua/C/lua_State stack, where it stays for a while (because there isn't a yield() that pops that value)
the coroutine takes a long time (stat(1)>1), and pico8 pauses my cart to do its own thing (flip, etc)
pico8 prepares to hand control back to my cart, by restoring the state my cart was in when it got forcibly paused. it restores the stack with "uh-oh" on it, but it does it wrong somehow
my code resumes running, maybe right at the point where flr() returns? (that would be quite a coincidence, but it might explain why irrelevant changes like local x=1 would squash the bug)
flr returns the correct value, but also the rest of the stack, which is "uh oh".

0x5f36 automatic character wrap + camera

Thu, 23 May 2024 21:45:57 UTC

I'm pretty sure this is a bug; I'm on pico8 0.2.6b / linux

You can turn on character wrapping with 0x5f36 / 24374, but it acts unexpectedly when you move the camera:

cls(1)
poke(0x5f36,0x80) --turn on character wrapping
msg='0123456789abcdefghijklmnopqrstuvwxyz'
?msg,0,0,12
camera(16,0)
?msg,16,12,13

Expected behavior: both prints should wrap at the edge of the screen.
Actual behavior:

There's a similar issue with p8scii "\^r" wrapping:

cls(1)
msg='\^rf0123456789abcdefghijklmnopqrstuvwxyz' --note p8scii wrap at start
?msg,0,0,13
camera(16,0)
?msg,16,18,14

menuitem never runs with P8SCII flip()

Fri, 17 May 2024 11:49:05 UTC

cart A: (broken)

msg="havent pressed test yet"
menuitem(1,"★test",function() msg="pressed test!" end)

::_::
?"\^1\^c" --https://www.lexaloffle.com/dl/docs/pico-8_manual.html#Control_Codes
print(time(),0,0,7)
print(msg)
goto _

cart B: (working)

msg="havent pressed test yet"
menuitem(1,"★test",function() msg="pressed test!" end)

::_::
flip()?"\^c" --this line is the only difference
print(time(),0,0,7)
print(msg)
goto _

These two carts should behave the same, but the menuitem function in cart A never runs -- after opening the menu and selecting the menuitem, it still says "havent pressed test yet"

cart B works as expected -- it says "pressed test!"

My system is linux / pico8 0.2.6b

Make Ten

Sat, 11 May 2024 11:27:15 UTC

OUT NOW: Make Ten Deluxe. I'll leave this page up but you should go play the updated version instead!

make_ten

by pancelor

[Click to Play]

Select numbers that add to ten, to remove them from the board. How high can you score in just 2 minutes?

An homage to Fruit Box. A FruitBox-like? There are some big differences in this version, the most obvious being the lack of music. (the music in the original is incredible)

How to play

Drag your mouse to select groups of numbers that add up to 10.
I recommend playing in fullscreen; it's easier to click on larger numbers.
In the original game, you're awarded one point per number removed,
Get the highest score you can within 2 minutes. Good luck!

This was my submission for TweetTweetJam 9, written in 490 characters of code:

z={}c=-8s=0g='⁶!5f58⁵d8"'::_::?"⁶1⁶c0⁶!5f2d3"
e=1x=stat(32)y=stat(33)if btn(5)do f=mid(16,96,y)if(p==a)p=x q=f?"⁷i6v1c1"
😐=c&min(x,p)⌂=c&min(f,q)♪=c&max(x,p)♥=c&max(f,q)else if(p)p=a if(n==c)e=0?"⁷i7f1a"
end?g,d
n=2for i=32,207do w=z[i]or rnd(9)\1+1u=i%16*8v=c&i\2if(u-😐|♪-u|v-⌂|♥-v>0)w*=e n-=w ⬅️+=➡️&~e
z[i]=w?w,u,v,w
end?"⁶jc1score "..s,-🅾️
if(btnp(6))🅾️=⬇️
if(p)rect(😐,⌂,♪+9,♥+8)
d=-t()?"⁶x2¹b█",d-5,106
if(d==-128)➡️=0g="⁶j8rtime up!"⬇️=🅾️?"⁷v3fg"
if(s<⬅️)s+=1?"⁷x5v3c0"
?"⁶.¹³⁷ᶠ³⁴\0\0",x-2,y-2,7
goto _

There's a commented version here.

Deluxe edition

Out now!

if-shorthand parser weirdness

Thu, 09 May 2024 01:02:15 UTC

@zep This maybe isn't a bug, but it feels very weird to me:

cls()
if (1)<2 print"a"
print"b"

this prints a b, but I would expect a syntax error instead -- the condition is "1<2" but the if-shorthand parens are only surrounding the 1, instead of the whole condition.

(if you change it to if (1)<0 then it only prints "b", which verifies that the condition isn't being interpreted as just if (1) or something like that)

oh, and my system is pico8 0.2.6b / linux

parser bug: shorthand if+print+comment

Tue, 07 May 2024 11:54:35 UTC

Hi @zep!

pico8 0.2.6b / linux:

cls()
if (false)?1 --hi
print(2)
print(3)

expected output: 2 3
actual output: 3

Here's an altered version that works as expected:

cls()
if (false)?1
print(2)
print(3)

(this prints 2 3, as expected)

3 things seem required to trigger this bug:

shorthand if
shorthand print on the same line
!! further text after the shorthand print (" --hi", in this example. but just a single trailing space triggers the bug too)

When these are all true, the next line seems to get scooped up into the shorthand line. This can include attaching an else to the wrong if, like in this more complicated example:

cls()
if false then
 if (false)?1 --hi
else
 print(2)
 print(3)
end
print(4)

expected output: 2 3 4
actual output: 4

photo_carousel

Sun, 07 Apr 2024 11:59:48 UTC

This is a silent tutorial video; skip to 2:10 for the juicy bit:

This is an animated wallpaper that shows your custom PNG files -- just place them in a particular folder! It also works as a screensaver. It's cpu-friendly, only drawing during transitions.

Installing

load #photo_carousel
mkdir /appdata/system/wallpapers
save /appdata/system/wallpapers/photo_carousel.p64
run the cart once, to generate the appdata folder
cd /appdata/photo_carousel
folder
using your host OS, copy any PNG files into this folder (don't put them in subfolders)
set your wallpaper to photo_carousel in System Settings

Settings

Run podtree /appdata/photo_carousel/settings.pod to edit the settings. Be sure to not press enter while editing (this crashes Picotron 0.1.0e) and you must save with the mouse, not ctrl-s (another Picotron bug(?) -- ctrl-s saves the current cart, instead of the settings file)

Set the transition time to 0 to disable transitions

Details

Converting PNGs

This cart uses importpng to convert PNG files into Picotron graphics. It does this once, in the background, and caches the results.

If you edit one of your PNGs, photo_carousel won't notice (afaik it's impossible to get last-edited time of PNGs in Picotron) Rename your file to generate a new cache entry, or delete /appdata/photo_carousel/cache.pod to regenerate the entire cache.

importpng is fast, but it's sometimes lacking in its ability to convert images into Picotron's palette. If you want better colors, you should use an external tool (like Aseprite) to convert your PNG into the base Picotron palette (you'll want the base palette, because the global palette changes to the base palette whenever you focus on some other window)

In the future I may use PNG Frame to get better colors by default, but I haven't done that work yet.

Transitions

You can add your own transitions -- you can skim through src/subdraw.lua without needing to understand anything else in the cart, and add new entries to the list of "subdraws" (transitions). Its very shadery/demosceney code

Many of the subdraws use some helper functions in src/tools.lua

Post your transition code here!

CPU usage

The cart uses about 0.002 cpu (0.2%) most of the time. During transitions, it can spike up to 25% cpu or so (depending on the transition). If you care, you can disable the transitions as a whole (by editing the settings) or individually (by editing the multi-line comments in src/subdraw.lua)

Cart

Here's the cart file. (It won't work here on the BBS, you need to download it)

photo_carousel

by pancelor

[Click to Play]

coroutine bug

Sat, 30 Mar 2024 08:35:58 UTC

hey @zep, I've found a nasty coroutine(?)/multival bug. I'm on Linux + picotron 0.1.0d.

tl;dr: sometimes select("#",tostr(i)) is 2, possibly triggered by calling coresume() with extra args.

I ran into this initially because add({},3,nil) is a runtime error now (it used to work in PICO-8, but now it throws bad argument #2 to 'add' (position out of bounds)). I had some code: add(list,quote(arg)) that was crashing as if quote() was returning a second value for some reason, even though the code for quote() definitely returned just one value. (surrounding it in parens (to only keep the first return value) fixed my bug: add(list,(quote(arg))))

Version A of the code is very short, and trips the assert inside spin maybe 50% of the time? sometimes many runs in a row don't trigger the assert, but sometimes many runs in a row all trigger the assert. (maybe that's just statistics tho). Version B is a bit more complex but always trips the assert instantly for me.

Version A: (short, inconsistent)

Version B: (longer, very consistent)

As noted in Version A, the two coresume-wrapping-functions inside cocreate_spin() act differently -- I've never been able to trip the assert with the "good" version. I've tried versions of this code with no coroutines and haven't been able to trip the assert.

idk what else to say, this bug seems baffling -- sometimes select("#",quote(i)) is 2, despite quote() being a wrapper for tostr()

import png

Wed, 27 Mar 2024 11:24:42 UTC

importpng

by pancelor

[Click to Play]

Guide

Currently (in Picotron 0.1.0e) it's hard to use a PNG image as a sprite. You can fetch("myimage.png"), but the result isn't in the right image format. So, here's a small tool to convert PNG files into picotron sprites.

Drag any .png or .qoi image into the tool to convert it into a sprite pod on your clipboard. You can paste this into the graphics editor, or into code.

Drag in a .hex file (e.g. from lospec.com) or a .pal file (e.g. from OkPal) before importing your png to change the import palette.

Details

Import speed

This tool prioritizes import speed. Images with only a few unique colors (e.g. an image already in the picotron palette) will import much faster than images with many colors.

Color quantization

You can use any colors, and the tool will try it's best to fit them to the palette. It isn't very smart about converting colors (it uses nearest euclidean distance in RGB space, and doesn't do any dithering). If you want better color conversion, use some external tool and make sure the PNG is in the correct palette before converting it with this tool.

See also PNG Frame, in "Related tools" below.

Wallpapers

If you're making a desktop wallpaper, I think you should stick to the default palette. If you use a custom palette, then your colors will change whenever you focus some window besides the desktop, I'm pretty sure.

To make a wallpaper:

make sure your wallpaper folder exists (mkdir /appdata/system/wallpapers)

save a new cart into that folder with this code:

function _draw()
    spr(1)
    _draw = function() end
end

convert your image using this tool, and copy it into your clipboard
paste your image into sprite 1 of the default sprite file

Library usage

This code is organized to make it easy to use as a library in your code. The library is self-contained in lib/importpng.lua, and you interact with it by calling myjob = job_importpng(myimg). The returned "job" is essentially a coroutine, but one that will let you limit its processing time. Call myjob:work(limit) during _update() until the job is done, or call myjob:join() a single time to finish it all at once (likely lagging the game). See the code for more details.

License: CC4-BY-NC-SA

Related tools

Cutievirus' PNG Frame -- a similar tool with much better color conversion. If your png is already in the right palette, importpng is faster than PNG Frame. But if you want better color quantization, use PNG Frame.
My Aseprite PICO-8/Picotron export extension lets you export Picotron pods directly to your clipboard from Aseprite.
My sprite importer lets you import PICO-8 spritesheets into Picotron.
My photo carousel uses this importer to show your custom PNGs as an animated wallpaper.
drakmaniso's OkPal palette editor.

changelog

p8x8: convert PICO-8 carts to Picotron

Tue, 26 Mar 2024 14:35:54 UTC

p8x8

by pancelor

[Click to Play]

p8x8: convert PICO-8 carts into Picotron carts (some assembly required)

I'm declaring p8x8 good enough for public release! It's a tool to convert pico8 carts to picotron -- it's not perfect and it requires some manual intervention in most cases, but it's magical being able to play a bunch of games on the new system without much effort.

Lots more info (instructions, compatibility notes, CC license, etc) here: https://github.com/pancelor/p8x8/

Teaser video here: https://mastodon.social/@pancelor/112162470395945383

changelog

v1.8 (#p8x8-8, unreleased)

music/sfx conversion!! just waiting on picotron 010h to add instrument effects

v1.7 (#p8x8-7)

fix secret palette
add more docs
add p8x8_symbol_visual() and p8x8_datastring() alongside p8x8_symbol() to help convert symbols. details

pancelor [Lexaloffle Blog Feed]

Open URL in browser (export plate)

Example (player perspective)

Setup

Example cart

License

Make Ten Deluxe

patches

controls

Fast loops

Setup

Results

Commentary

for_inext()

for_all()

for_i()

for_each()

slope change in for_each() / for_all()

while_isize() versus while_i()

while_i() versus repeat_i()

for_next() / for_pairs()

Conclusion

Web clipboard broken (0.2.6c dev8)

Toggle Music mod for any cart

pancelor's postcarts

Controls

Technical details:

music desync (0.1.1b)

sfx/music data layout

Library

Demo cart

License

spritesheet remapping 0x5f54 crashes after reboot

coroutine stack pollution

0x5f36 automatic character wrap + camera

menuitem never runs with P8SCII flip()

Make Ten

How to play

Deluxe edition

if-shorthand parser weirdness

parser bug: shorthand if+print+comment

photo_carousel

Installing

Settings

Details

Converting PNGs

Transitions

CPU usage

Cart

coroutine bug

import png

Guide

Details

Import speed

Color quantization

Wallpapers

Library usage

Related tools

changelog

v0.4 (#importpng-9)

v0.3 (#importpng-7)

v0.2 (#importpng-6)

v0.1 (#importpng-4)

p8x8: convert PICO-8 carts to Picotron

p8x8: convert PICO-8 carts into Picotron carts (some assembly required)

changelog

v1.8 (#p8x8-8, unreleased)

v1.7 (#p8x8-7)

v1.6 (#p8x8-6)

v1.5 (#p8x8-5)

v1.4 (#p8x8-4)

v1.3 (#p8x8-3)

v1.2 (#p8x8-2)

v1.1 (#p8x8-1)

v1.0 (#p8x8-0)