This is a simple fork of Sokoblox that saves your progress.
Continue
Once you have beaten some levels, the first option on the title screen will change to continue, taking you to the last level you were playing.
Reset Level / Clear Progress
I disabled ❎ to reset levels, as it didn't work properly (even on the original cart).
Instead, use the option I added to the pause menu.
I also added an option to clear your progress.
Again, this is a very simple mod.
I only added less than 20 lines of code to the original cartridge.
Everything else still works, including loading from passwords.
Did you know you can find top ranked carts by searching for t:?
Carts are ranked by stars, as you would expect...
Categories
This works not just for carts, but in all forum categories: Releases, WIP, Blogs, Tutorials, you name it.
Filters
Doesn't work with Lucky Draw, naturally.
- But it works with all other filters (New, Featured and Favorites).
SPLORE
Also works in SPLORE's search tab.
Even in handhelds, it's quick to "type" with arrow keys.
- Note that
:is the first character when you press ⬇️.
Latest
If you want to limit the search to the latest carts / threads, you can specify that.
- Named durations like
t:week,t:month,t:halfyearandt:yearwork. - You can also specify a number of days. For example, for the last 5 days, use
t:5.
Range
You can also specify inclusive time ranges with tr:, like tr:2022 or tr:202210-202305.
Since when?
This was introduced by @zep last year, but he only mentioned it in this comment and in version 0.2.7's changelog.
This is a simple fork of Pico Factory that lets you pause time.
Of course, items will not be produced or sold while time is paused.
Controls
You can pause / unpause time in two ways:
- press ❎ on player 2 controller (Q or A on the keyboard);
- select
toggle pausein the menu.
The latter is your only option if you are playing on mobile or handheld.
Disclaimer
This fork writes pause edition on the top of the board.
This will be visible in any screenshots (even while the graph is being displayed), so it will be clear that the score was not obtained on the original cart.
Bugfix

muOS screenshots
I'm currently using muOS on my RG CubeXX.
On muOS version 2508.3 (Golden Goose) the shortcut for screenshots is L2 + R2 + X. Screenshots are saved as 720x720 PNGs in the MUOS/screenshot folder.
This works in native PICO-8. The handheld rumbles to confirm a screenshot was taken.
Sometimes, though, I want to take a screenshot without triggering the ❎ button...
CTRL-6 screenshots
I edited MUOS/save/pico8/config.txt and added 29=224,27=35, at the end of the map_scancodes line.
This maps L1 and R1 (the only buttons that trigger key scancodes) to LCTRL and 6, respectively.
Desktop path
I also had to add /mnt/sdcard/MUOS/screenshot/ at the end of the desktop_path line in config.txt so that CTRL-6 screenshots are saved on the screenshot folder.
Note: use mmc instead of sdcard if you want your screenshots to be saved in SD1.
It works!
I recently upgraded my handheld. Out goes the original RG 35XX, in comes the RG CubeXX.
The stock OS (mine came with version 1.0.3) is actually pretty good and supports native PICO-8.
But I've decided to flash muOS on a separate SD card... And I don't reget it one bit! Experience is definitely superior, IMHO.
I could even enable the performance monitor. The steps are simple...
-
Make sure you run a cart and shutdown from the pause menu (do not press SELECT+START), so PICO-8 saves a default
config.txt. By the way, I prefer to always shutdown from the pause menu. SELECT+START is my last resource when a cart crashes to the prompt. - Open
config.txtin/MUOS/save/pico8. Change the line
map_scancodes |
to
map_scancodes 29=224, |
This will remap the L1 button to the left CTRL key. As the START button is already mapped to the P key, just press L1+START to open / close the performance monitor.
About
Neath is a game by @binaryeye.
This cart loads Neath's cartdata (read only, don't worry) and shows your progress on a map.
You can choose how undiscovered stuff will (or will not) be displayed.
Here are some spoiler-free screenshots...

Second screen
I suggest you run Neath Map on a separate PICO-8 window / browser tab.
Whenever you activate a new save point in Neath, press ❎ on Neath Map to reload your cartdata and update your map.
It feels like playing a DS game!
This is a simple fork of Hollow Seeker that saves your hiscore (and prints it on the screen, obviously).
How to play
Go forward in right direction.
Seek a hollow as refuge not to be crushed.
[Z][X]: start/retry game
Implementation Notes
Changes were kept to a minimum, only 10 lines of code added.
Enjoy!

Warning
This tool overwrites saves from other carts. Make sure you know what you are doing.
Controls
Instructions on which keys or buttons to press are displayed on screen at all times.
Note: pause menu is supressed in keyboard mode, hold ENTER or P for a second to display it.
Context
- PICO-8 executables save cartdata as text files in the cdata folder.
- BBS javascript, on the other hand, is limited to your browser's internal storage, which is a lot less convenient for users to access directly.
Purpose
This tool allows you to easily transfer your progress between PICO-8 installations, particularly from/to the BBS. It also allows you to edit your saves on the fly.
Link example
Here is a link to Google in a standard paragraph.
- Here is a link to Google in a bullet list item.
- Here is a link to Google in a numbered list item.
Mention example
This post was created by @andrejtrindade.
- This post was created by @andrejtrindade.
- This post was created by @andrejtrindade.
Bug
Why are links white when they appear in a bullet or numbered list item?
This looks like a bug on the BBS...
This is a simple fork of Caroline that saves your progress.
- Saving happens when you enter a new room
- Time tracking, collectibles and deaths are also saved
- You can
reset save datain the pause menu
This fork aims to help those who prefer to play in short bursts, like myself.
Caroline is a "Portal demake disguised as a Celeste Classic mod", according to @Meep (one of the authors).
Play using the ESDF keys and a mouse.
Enjoy!
Implementation Notes
500 Featured Carts
Yes, we have just crossed that milestone! Have you ever wondered what kinds of carts don't make it into the featured section of the BBS? Call me crazy, but I have.
So I looked at the 500 top-starred carts (searching for t:) and checked which ones aren't featured. It happens there are only 30! Here they are (with links, in case you want to go check any of them):

This cart is a fork of the original Seinfeld Simulator 1.0 by @Rangee27.
Quality of life improvements
- You will only see jokes that are not in your "Joke-iary" yet (until you complete it), works both in kid mode and 18+
- You can disable mouse in the pause menu - in case you enabled it by mistake on a device with no mouse
- Better contrast on the "Joke-iary" and some other text (title screen / button prompts)
- Same cartdata ID, so you can switch from the original to this cart and vice versa as you please
I had to do some tweaking to stay below the token and compressed limits, but I tried to keep changes to a minimum. Using a diff tool I only counted about 30 lines of code changed.
As the title says, I'd like to know what are the consequences of setting carts as forks.
Here's an example... I submitted STAR SPLORE last month. This week, I got a reply asking for some changes. I wanted to accommodate the request without changing the main cart, so I submitted an alternative version of the cart.
I didn't want to start a new thread for this alternative cart, though. So I just embedded it in a reply on the original thread. I guess that's why the cart doesn't show up in "New Carts", nor does it appear in my profile under "Cartridges".
And that's fine! It's an alternativo cart, I don't want anyone to find it before the main one...
But I noticed that, when I click "Edit" on a cart, there is a "Forks" section. I know what a fork is in GitHub, but what does it mean here?
Should I set this alternative cart as a fork of the original STAR SPLORE? What are the consequences of doing that in the BBS?

While troubleshooting why unwanted shortcuts were triggering on my handheld, I noticed that map_scancodes does not suppress the original scancode if it corresponds to a modifier key.
For example, you can add the following line to your config.txt:
map_scancodes 4=5,224=6, |
This will remap:
- the A key (scancode 4) to B (scancode 5)
- the LEFT CTRL key (scancode 224) to C (scancode 6)
Then, download this test cart and run it in PICO-8.
- when you press the A key, it will detect only scan code 5 (key B)
- when you press the LEFT CTRL key, it will detect both scancode 6 (key C) and scancode 224 (LEFT CTRL, not supressed).
You can test this with left and right CTRL, ALT and SHIFT.
Keep this in mind when mapping your handheld buttons, especially if they are originally assigned to modifier keys... So you don't end up accidentally triggering unwanted shortcuts.
Note: this cart was mostly based on New Raw Key Reader, from dw817.
This is a very simple tool to show scancodes (and SDL key names) for keys pressed on a keyboard.
This can be useful when remapping handheld buttons. For example, I have an original RG35XX and I'm using the MyMinUI custom firmare. I wasn't satisfied with the default button mappings, so I decided to remap everything from scratch.
First, I commented the map_scancodes line in config.txt and ran this cart.
- The A button was mapped to scancode 44 (spacebar).
While releasing STAR SPLORE, my second cart, I realized that it's nice to change the default title of you carts and its threads.
Here's what happens when you search for "star_splore" in "New Carts", for example.
You get a nice cart title, "STAR SPLORE 2025-08-16". If you click on it, you go to STAR SPLORE's thread.
- The thread will have a nice title, "STAR SPLORE", which is independent of the cart's version.
- The cart will have the same nice title as before.
- Note that both titles are different from the cart's ID (star_splore).
I didn't pay attention to that when I released Tiny Tactics, my first cart.
You can see how it didn't look so nice.
Maybe those titles weren't exactly BAD, but I could do better.
It's like browsing and launching "Featured Carts" in SPLORE...
But they are ranked by STARs! And you can filter by GAME GENRE!
Controls
- ⬅️➡️: previous / next page
- ⬆️⬇️: previous / next cart
- 🅾️: filter by game genre or by year
- ❎: run cart
After you are done with the cart, enter the pause menu and select the last option:
back to ★SPLORE
About
STAR SPLORE aims to help you discover some of the best PICO-8 carts ever made.
- That's why filters are provided.
- That's why this is a "featured carts only" browser / launcher.

MyMinUI
I've just discovered MyMinUI, a custom firmware for my original RG 35XX... that has native PICO-8!
Note: MyMinUI is a fork of MinUI, a custom firmware much more people know about. MyMinUI is also available for some other handhelds: Miyoo Mini (and Plus), SJGAM M21 and GameConsole R36s.
Instalation
If you want to install MyMinUI on a SD card and try it for yourself, I have some tips for you. First, grab the latest release and unzip it (don't delete the zip file, you will need it).
The instalation is pretty standard custom firmware stuff, and is well documented in the README.txt file. If you have any doubts, leave a comment below and I will try to help.
Now, for my tips... We will change a few files in your SD card - same card and partition where you copied some files from PICO-8 (Raspberry Pi's version) during the instalation process.

In this post I'll try to answer some questions regarding the ❎ and 🅾️ buttons. This is a design decision that came up early when I started making my first PICO-8 game.
I'll consider some well-received PICO-8 games from Nerdy Teachers' 200 Best PICO-8 Games when trying to address these questions. When I do that, I will provide the game's ranking in that list in parethesis, e.g., Celeste (#1).
Glyphs or Letters
- Question 1: Should I use the ❎ and 🅾️ button glyphs when displaying commands on screen, or should I print letters for the key mappings?
In theory, you should use button glyphs, right? I mean, if you were making a NES game, you would prompt the player to press A or B. You wouldn't try to guess key bindings used by the emulator, even though a NES game released in 2025 has very slim chances of being played on original hardware.
Often, though, reality kicks in. If you upload your game to itch.io, for example, people are playing a browser game. Most may not even know what PICO-8 is or even suspect they need to consider key bindings. They may see "press 🅾️", reach for the O key, nothing happens.
.jpg)
I am currently developing my second PICO-8 game. I'm considering adding an option to load my first game directly from the new cart, if the player wants to give it a try.
Both games are single carts, and there is no sort of communication between them. It's a simple load call with a breadcrumb parameter.
I was concerned about cartdata though. Both games use cartdata to store progress, each using its own ID. And the PICO-8 User Manual states, in section 6.11, that "CARTDATA can be called once per cartridge execution".
The wording on the manual indicates that my approach was OK, but I decided to test it anyway, just to make sure.
Only once
First, I simply called cartdata twice to see how PICO-8 would enforce the single call.
cartdata("test_load_1")
cartdata("test_load_2") |
This is the error message:
Simulating carts





1 comment