Skip to content
Game Development on the PICO-8 with Johan Peitz episode artwork

Nov 27, 2025 47 min

Game Development on the PICO-8 with Johan Peitz

from Software Engineering Daily Hosted by softwareengineeringdaily.com

PICO-8 is a software-based gaming console for making, sharing, and playing small games with a retro aesthetic. It emulates the look and feel of 8-bit consoles, providing limited color palettes, screen resolutions, and memory constraints. The PICO-8 dev environment uses Lua and is focused on being accessible to developers while offering depth for complex projects. Johan Peitz is a games industry veteran and developer extraordinaire, having created dozens of games across many platforms. He's an expert in PICO-8 development, and joins the podcast to talk about creating games for the console. Joe Nash is a developer, educator, and award-winning community builder, who has worked at companies including GitHub, Twilio, Unity, and PayPal. Joe got his start in software development by creating mods and running servers for Garry’s Mod, and game development remains his favorite way to experience and explore new technologies and concepts. Please click here to see the transcript of this episode. Sponsorship inquiries: [email protected]

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Game Development on the PICO-8 with Johan Peitz

0:00 47:27
of matches

Transcript Auto-generated, may contain errors

Pico 8 is a software-based gaming console for making, sharing, and playing small games with a retro aesthetic. It emulates the look and feel of 8-bit consoles, providing limited color palettes, screen resolutions, and memory constraints. The Pico 8 dev environment uses Lua and is focused on being accessible to developers while offering depth for complex projects. Johan Peitz is a games industry veteran and developer extraordinaire, having created dozens of games across many platforms. He's an expert in Pico 8 development and joins the podcast to talk about creating games for the console.

Joe Nash is a developer, educator, and award-winning community builder who has worked at companies including GitHub, Twilio, Unity, and PayPal. Joe got his start in software development by creating mods and running servers for Gary's Mod. And game development remains his favorite way to experience and explore new technologies and concepts. Welcome to the show, Johan. How are you doing? Thanks, Joe. I'm really good. So happy to be here. I've followed your work for a long time as a big Pico8 fan. And as we'll cover, you are one of the more prolific Pico8 devs. I think I counted yesterday, and I think it was seven or eight of the 30 Pico8 games on Steam are yours. So I'm very excited to have you on the show. But before we start talking about Pico8 and Pico8 development, I wanted to tell you one thing I didn't know is what was your journey into game development and how did you come to become like a Pico8 dev in particular? Well, I think that's two very different things. I started out with board games when I was a kid, a huge fan of everything that had dice in it, basically.

And then one summer, I guess I was 10 or something, a friend of mine had a Commodore 128 at home. shut off all the lights, closed the windows, closed the doors, and we spent an entire summer just learning everything about it, how it worked. And I guess we weren't too good at it. He had a cousin who knew way more than we did, but definitely my first intro into computers. And from then, I just realized all the things that I wanted to do with board games, I could now do, or I couldn't do it, but I could at least attempt to do it inside a computer instead. And basically, I've been stuck since. So that was, I don't know, 35 years ago or something. So it's been a while. That's awesome. But I think what I actually liked with Pico 8 was that it harkens back to that day, right? You just launched it.

There's a prompt. You can just start typing. Everything is testable from the get-go. You don't need any specific setups or plugins or everything. It's just there. And for me, it's also similar. I think if I think back, I also used Amos quite a lot, which was a game programming package for the Amiga. I think it was for the SGE as well, maybe. Also, this integrated package where you could just do everything without touching anything else. I think Flash was really close to that as well with ActionScript. And I think all those environments are things I really, really, really enjoyed when I was using it. And Pico 8 was just the best of both worlds. It's the old stuff. And then also this really...

nice environment where you have all the tools that you're supposed to without having to do build steps or convert things back and forth. You can just jump in and build stuff. Yeah, that makes a lot of sense. And especially, I guess, one of the elements of nostalgia that you hear people talk about with the retro consoles and with the Commodore and the Amigas is the experience of booting up into it, being able to get going with making stuff straight away and there being nothing in between. So that drawing about the PicoA makes a lot of sense. So, you know, you mentioned that intro to the Commodore being 45 years ago. I know you've been in the game industry a long time. When did you come to find PicoA and start using PicoA? And I imagine you were still working in the industry before that? I think that must have been...

oh, I don't know, six, seven years ago or something. I think I wasn't one of the early adopters by any means. I like to jump in when things are a bit more stable and I don't need to be the first test person for that stuff. But I was still working in the industry, huge issues, not issues, but there were always, you know, these non-compete clauses when I was, if I had a proper job, so to speak, could I actually do this, could I do a game jam, who owned the code I wrote, et cetera, and all that stuff. But I was so fun to work with, so I ignored that stuff most of the time and nobody came knocking on the door, so I guess it was fine.

Nice. Awesome. So we've spoken about PicoA a bit and alluded to what it is, but just for listeners who aren't aware, can you explain briefly what PicoA is? I think it's best described as, it's not a game engine either, right? It's a console. It's the Commodore 64, basically, that you can boot up straight at the prompt. It has all the tools you need to make a nice looking game. What makes it different from similar packages, I think, is the restrictions, right? It's very harsh on what you can display, how much CPU time you have, how much code you can put it in, how much graphics you have. There's only 128 times 128 in terms of sprite space, et cetera. So very often you run into these.

restrictions and i guess to a newcomer that can seem as a turn off to some extent okay but i want to do these big things and now i can't do my portraits or write my long procedural code or whatever it is but i always thought of picoate as almost like a game-like experience when you develop for it because as you learn more about the program you also know about how to kind of bend the rules slightly and it turns out those seemingly super harsh restrictions they aren't really that harsh because you can kind of okay i can use the sprite memory for my music instead or if i write this piece of code i can start compressing my tile map or something right and so it becomes a much much bigger environment than you first thought but it's only available once you kind of have that epiphany that how it actually works on the inside and constantly making these trade-offs between should i use this space for graphics should i use this space for code or whatever that almost becomes like a puzzle game in itself and just making these trade-offs back and forth it's super rewarding when you actually get to fit your ideas into this extremely confined space I don't know if that actually explained what it is, but I think it's bits of the philosophy. I mean, it's a nice ecosystem, super friendly community. Most of the games are, you can just download them through a BBS tool and check out how they are made, which is also a great learning tool. Yeah, the choice of BBS is like the distribution mechanism. The native distribution mechanism is also, you know, I guess part of the retro nostalgia part of it. So you mentioned a lot of interesting things that I want to follow up on. So I guess like, first of all, talking about the constraints, I guess it's, I've always taken it as like a prime example of constraints breed creativity or whatever. But I think I'm wondering this particular case for you, because I said, my perception is that you ship a lot of games very fast. Is that, especially when you're starting out,

the limitations really help you avoid scope creep, right? Like you're forced to not scope creep and to finish the game as you originally, like a slicer game as you intended. Do you find that to be accurate? To some extent. I think I am a lot less structured as a developer than what people might think. I usually have a seed of an idea. And I see it more like, I don't know what the English word is, but you know, stone masons or something? Yeah, yeah, yeah. Where they have this big block of marble or something and they start chopping away and they go, oh, it's supposed to be a dog or whatever. Right. Then it turns off, whoops, I broke the tail. I can't really put that stone back on, right? And you have to kind of, oops, it didn't really fit inside PicoA. I'm going to change the design on my model or sculpture.

to actually work with what works in it then it's kind of okay didn't really turn out the way i wanted but what changes do i make to the design so it actually fits and still makes a lot of fun to play right so you have to let the stone tell you what it wants to be to some extent i'm more of a following a very vague vision when i develop games more than that i have a very specific idea from the beginning cool so when you're following that process i guess at the point where you're at that idea stage how much are you already thinking about the constraints of pico 8 or is it you know you come up with grand visions and then they get pared down to size or i guess by this point you've been doing it for so long you're already like you're thinking in terms of what you can do more often than not yeah definitely usually i try to make things that you're kind of like half of the space or scope that pico 8 can offer and then it kind of grows a bit from there and then i can use the last 25 to push it a bit extra right because it's i find it extremely rewarding when you can fit that type of gameplay or technical solution into the game that people didn't really think was possible. And then once that works, then you can remove all the other fluff because nobody cares about that. The technical achievement is big enough to be the main driver of the game. It's still seen as a complete package, but other things can be downprioritized very much once you have that core that really works.

interesting yeah the technical achievement within the limited environment being a selling point i guess is another advantage of you know these ecosystems where everyone's dealing with the same constraints and i definitely think that's true of picocad like i often cite picocad which we will talk about more in detail at the moment but just for a brief summary for listeners is a cad tool built in picoy and it's 3d i always mention picocad as like an example of like here is something that you would first of all think shouldn't be possible in this but obviously it is and yeah well definitely i've got a bunch of questions in a minute but i guess to get into more concrete terms so you mentioned some of the tools available i think it'd be cool to go over what is actually available and what it's actually like to be a PicoAte dev. So I guess, first of all, you mentioned briefly the idea of messing with the memory and fitting music in so-and-so place and your maps in another place. Can you run through the tool suite, I guess, on PicoAte that you use? So some developers, I know they sit in other environments, for instance, maybe they use visual code. I'm Swedish, so I'm not going to promote a specific tool now. There are other tools available, you always have to say. But I've more and more found that staying inside the little box that is PicoAte.

128 times 128 that really helps me not running away with my ideas right you keep variable name short you keep the scope short keep the functions short and it has to be very readable and understandable in order to be able to work in that environment and that really helps me moving forward so i mean the code writing box whatever it is editor i guess yeah the editor exactly that's one thing right and then there's the sprite editor again 128 times 128 16 colors not sure i mentioned that that are predefined as well right so it's very set which gives all pico 8 games a very specific look right you can almost instantly see that it's a Pico 8 game. Now we're making another game in another engine, but I'm so colored by my Pico 8 work, right? So it looks like a Pico 8 game. Oh, that's Pico 8, people tell me. But no, it's not. It's actually something else, but it still has so many things in common. The sprite editor, and then there's the tile map. So I don't know how big it is. Probably 128 by 128 as well. But that actually shares memory with the sprites. So if you want to use half of the sprite bank, you lose half of your tile map, right? Or vice versa. And there's obviously ways around that once you get to know the system. But that, in turn, then forces you to do some other things. For instance, if you want to use the whole tile map, then you have to move it to somewhere else in the memory.

and then you can't use the actual tool that is built in to place your tiles which forces you then to write your own tile editor and things kind of escalate from there right so lots of tooling and the custom built stuff to get it working once you start pushing the limits there's sound editor for sound effects not my forte same with music editor a classic tracker that was really popular in the amiga days that's it i think so all the basic things to get stuff up and moving yeah well i should also say it's all in lua which is if people aren't familiar with that it's a super friendly or easy to use language that leaves you open to all the mistakes you can ever make with no type checking or anything else. You have to keep everything in your head. Yeah. Not an uncommon choice in game dev land, but I know countless people who immediately, despite all of its advantages and pleasantries, who bounce off of it because of indexing starting at one and not zero. Yeah. Cool. Yeah. Thank you for some minutes. So, you know, you mentioned various like hacky ways to get around the memory constraints and stuff. One of the ones that I think is really interesting that I've not really done with, but I know that you've used it a couple of times and that you've used on...

I think, I believe you used it for the arcade distributor you gave versus EMF, but it is multi-carting. Can you tell us a bit about multi-carting and how it works? I guess, first of all, we'll start with what is a cart in the context of being going on and how it gets distributed. So once you're happy with your game, the main idea is that it's kind of, I guess, Joseph White has built the whole system. He likes things to have physical representation, or at least as close as you can come right. So you can save all the code, all the graphics, everything. It can be saved both into a text file, but you can also export it into a little PNG file that actually looks like a memory card or something with a little image on and everything. It's very cute. And he uses lots of little...

i don't know compression techniques and special layers of the png files so it doesn't actually get garbled but the image actually stores all the code all the memory stuff you made and the whole thing which is a technical achievement in itself yeah yeah just to make that explicit for anyone who didn't catch that that is png the image format is being used to store all of the games it's incredible it's so cool which makes it super easy to store right you just send it on discord or upload it somewhere or wherever people can just load that and play it look at the code or the graphics or whatever or upload it to this bbs function right where there's tons and tons of great games but for that to work you're kind of limited to the space that peak weight gives you and i think it's about not totally sure about these limits but it has to be able to compress under 60k i think there's a top limit of 32k characters or something like that and then there's a token limit in terms of how you structure code etc and all that has to kind of be possible to cram together to fit into this cart and that's the cart right it looks like a cartridge but if you think oh i wrote this code and it doesn't really fit for instance in my game golf monday the two golf games golf sunday and golf monday where golf monday is the sequel there i wanted to have a much better course generation right so i wrote an editor to make the golf course and then that is loaded into a special format

which has to reside in its own cart because it doesn't fit in the actual game cart. So there's a title cart, which loads the main menu, and you can customize for the player, et cetera. And then when you actually press start, then it also has a bit of code to generate the course, which then stays in RAM. And then the other cart is loaded. Everything about the last cart is forgotten, but since I could load the map into RAM, I can start playing with that as if it was in my original cart, but it wasn't right then. People are, of course, chaining this into craziness, some people. I mean, I know the guys who made Doom and other world ports and things like that. They have like 64 carts, and it's just...

massive right so there's huge build steps to make everything work yeah i only made double carts so to speak i think that's enough for me but it's very convenient if you have for instance a dungeon crawler and you need a separate car to do all your generation and you just load that cart to the calculations put that in ram and then swap back to the original cart it's very cool but then you kind of lose some of the distribution methods that are available and you need to kind of package it up a bit differently yeah which i guess brings me on to my next question so and we'll talk about this more in a bit but you make pico games commercially you're not just distributing them within the bbs you sell them on platforms and you provide them cross-platform as well what is the So I know there's export tools, but does PicoA natively support building executables for the platforms? Yes, is the short answer. And it's just super easy. Just write export, and then it gives you the Windows build, the Mac build, the Linux build, and the Raspberry Pi build straight off. And that's it. It's horribly easy. It's so easy. I think I released six or seven games on Steam. I developed them on a Mac. I've never tested the Windows builds. I just uploaded them. And they're like 90% of my players use Windows, obviously. But it just works so well, so I don't even need to test it.

Nice. The advantage of your whole game engine being a little virtual machine, I guess. Yeah, definitely. It's very cool. So you mentioned, you know, along the way, building your own map editors, building various tools, and some of these tools, you know, are commercial releases, PicoCAD and PicoSynth. Again, this is one of the things my perception of you as a Pico 8 developer is quite unique, because I think you build an unusual amount of tools in Pico 8. What led to you, you know, was that just a natural emergence of your own game development practice? Like, what made you start wanting to build tools in the editor? I think it's a necessity sometimes to make the games I want to make. And also lots of times, like you mentioned, PicoSynth and PicoCAD, they're all, they started as something else, right? And then it turned into something, PicoSynth, which is...

How should I summarize that? It's a modular synth experience, I guess, where you can kind of, you create different boxes of equipment and you connect them with springy cables and sound is made. Usually, the same with PicoCAD, I don't know anything about 3D with PicoThings. I know nothing about synth or how they work. So that actually started with me playing around with Verlet physics. What should I do with all these springy cables? There should be something fun I could make with them. And then it started as, maybe I can just send electricity through them and have some sort of light puzzle where you're supposed to get certain inputs or outputs.

And then I just stumble onto the audio stuff. And suddenly I built out a full range of various things that you could connect with cables. I mean, for me, it's very much, I prototype stuff. If I find something that's fun, like this cable, it was just a nice feeling to move them around and kind of stick them into little holes. Then the actual application doesn't matter so much to me. Cool. Yeah, that makes sense. But I guess with PicoCAD, that has really grown into something special. There's like a huge community around it. People use it to make games in other engines. People are exporting the tools. So I guess for an intro, can you tell us about PicoCAD and the kind of capabilities it has? Yeah, so PicoCAD is...

a time trip back to the 90s where cad programs consisted of four viewpoints and it was very much looked like an old technical drawing or something right where you need to see it from three different angles and i have a 3d view of it and that's how i learned doing cad back in the 90s right in school and i've never been a fan of these more natural mesh like things where you very dynamically move things i'm too old for that i guess but back to picocad so it has these three views it's super limited but you can add like primitives like cubes prisms and various volumes and then can extrude certain faces which is super basic right but that's basically the tools you have you can build stuff you can extrude stuff and you can then move vertices around of course and then you can also texture it you can load it as a simple texture and that's basically it and it's super simple there's a few things more to it of course you can have lights there's some sort of lighting and shading model on it so you can have flat shading if you just want to use colors and textures and things like that but it's super simple but the same way peak weight kind of breeds this creativity through you can't even go further right there's been people who's just been building amazing things in it

really learning the ins and outs of it much more than i could ever have imagined right so i mean there's hashtags all over the place and it's to some extent to the restrictions and how it actually looks i mean there's lots of the sort there's no c buffer in it so the faces can get all jumbled if you don't do it properly things like that they have a very distinct look the same way you can say this is a pico 8 game i think you can say for sure this is a picocad model because how the kind of software encourages you to work right right you know when you say it's that aesthetic of writers because how software encourages you to work was there intentional design in that you where you were like you know i want these things to look a certain way and this is kind of how the tool set is developing or was that purely organic it just came out of the constraints situation when i started making pocad again i just i there was some talk about oh you can do 3d in pico 8 so nice and people were doing some various experiments and so did i and i started with cubes etc and it would be nice to have a car and i could still write the specification i could just write that in text right this made sense and i could edit the uv coordinates and things like that then how it would be nice to do a muscle car with some sort of exhaust on the hood or air intake and things like that

quickly it became very difficult to do this on graph paper right so then i just started trying out what if it looks like this blah blah and i quickly find a way that worked really really well right and then as things happened that project became much more interesting than actually using the models for anything but in that step since i worked on graph paper it kind of became very natural with snapping for instance so the game or the software doesn't allow you to put vertices wherever you want it snaps to 0.25 or a quarter of units and that also makes it really it promotes a certain chunkiness or roughness of the models you can hold a key and do freehand movement but that's for the pros right And also, it makes it much easier to connect certain volumes because you can't merge meshes as we have to kind of put them really close to each other. And thanks to the snapping, then it becomes really kind of lines up. Yeah, exactly. And that then stops stuff from bleeding through and things like that. So lots of technical decisions also led to how it looks right. And then the Pico 8 palette is very specific. And when I had to put the light model on that, if I want to fade, for instance, red, there's no dark red, right? So it has to fade into brown or pink has to fade into red and orange, et cetera. So it gives also a very certain look to the shading depending on what color you use in your model. Right. Instead of just fading.

into a darker shade, it actually fades into different colors, which gives a nice vibe to it. Awesome. OK, so I do want to come back to the shading and the lighting engine. But I guess first, a fundamental question. And this might be an uninteresting question, depending on how much you know about 3D rendering. What does it take to do 3D in PicoCAD? Because to me, that's still mind-blowing. This might be my ignorance that finds that. It's part of the reason I find it so interesting. Yeah, so Pico 8 actually comes with an example called Dots 3D. It's like an old 80s demo with spheres circling around. It's like booting up some sort of cracky intro to whatever game you want to play.

And I think most of PicoCat still uses that for its base code, right? And then it's just packed with layers on top of that. But that's the core. It's still rotation around it, or it go, or the center of the scene. And I mean, if you have one dot with x, y, z coordinates and another, then you can draw a line between those two, right? Right. And then you arrange your dots into cube, and there's your wireframe.

Then Pico8 has this specific thing, which makes the texturing work, which is called T-line. So it draws a line, but instead of you just specifying a color, you specify two coordinates basically in the tile map. And then it colors the line according to those colors in the tile map. So you first draw your texture in the sprite map, and then you use those sprites to place them as tiles on the tile map. And then you can start using that as a texture for your draws. Right, cool. That's really useful. Because that was part of where I think my mental model was struggling. So when you first come to Pico8 2D, you're like, okay, I'm drawing a sprite, and that sprite is living on the tile. Like, you know, that's going on the map. And it's very...

The model of what you're interacting with is very straightforward. I'm hearing how those parts interact with the 3D is really useful. Okay, cool. Then you also get perspective correctness, right? Usually when you draw a texture in 3D, you have to kind of think, okay, it's supposed to actually get smaller. The shape gets smaller because that I can easily calculate, but the texture should also be drawn differently depending on where it is in the depth. But there's nothing of that, right? So you also get this PlayStation 1 aesthetic where it's kind of a bit jittery and things are kind of moving a bit janky, which I think a lot of people like as well, right? Because the same way pixel art is my childhood, the PlayStation 1 art is a lot of other people's childhood.

Yes, people invest a lot of time in recreating aesthetics with the engine. That's great. Yeah, so onto the, I guess, the lighting and the shading. So, as we said, for various geometry reasons, the Pico CAD models look very distinctive, but you have a really nice, different shading approach as well. Can you talk briefly about that? So Pico 8 comes with a dithering functionality when you draw basic drawing primitives, basically. So if you want to draw a square, you can apply a...

four by four pattern to it, I think it is, which can then be a checkboard or an art or a square or whatever, right? And it's quite useful when I do particle effects in games, for instance, if I want things to fade out, they can at least, you can't do transparency, but they can at least be more sparse in terms of their pixel density to some extent. But then you can also set, I think this is how you do it, you can set color. Whenever you draw something in Picoate, you say, okay, I want to do it with color seven, for instance, but there's actually more, and you have 60 colors, but that's just the first, I don't know, four bits, I guess, of the color space, but you can send a whole byte. So that means you have four bits at the bottom for the actual color, and then the higher part of the byte, you can use for another color.

So then you can tell peak weight, okay, use this pattern that I specified and all the lit bits are with one color and all the unlit bits are with the other color. And then it's just a matter of calculating which angle the face is facing and then deciding, okay, if it's this color, then it should do this darker shade instead on every other pixel. Very cool. If that makes sense. And then while I was developing that, I usually am very open with my progress on social media. It gives me a lot of good feedback. And of course, Zep, Joseph, who's making peak weight, was following that as well to some extent. So he actually started implementing stuff that I needed for PicoCAD.

So previously it wasn't possible to apply these dithering effects to textured, so sprites or T-line, this texturing thing you can use. So that's, you kind of slipped into a new Pico 8 version so I could get even the textured, so I could lit. So I can use the dithered lighting module even on textured faces. That's really cool. That's awesome, Fim. And I guess that kind of leads into something that I didn't ask but was meant to ask earlier, which is in terms of the, so we mentioned the code, obviously written in Lua, but in terms of the API, is how much is the Pico 8 API doing, you know, providing for you in terms of utilities when you're developing a game? Like what is the kind of tool set it gives you?

i mean you get an api to kind of access all these things like sound style map sprites there's a lot of syntactic sugar in pico 8 lua version that it doesn't exist in the real one so to speak that i miss a lot for instance with the tables i mean there's lots of shorter words it's just so much easier to express yourself in code than having to write i don't know table dot remove something something and things like that it's just just a horror for me once it gets used to just dell and add and that works in pico 8 because there's the api is so compact so it doesn't collide with anything else right Also, when I started writing PicoAid, there was no split functionality. So you can take a string and then split it up on some delimit, right? That didn't exist. So it then uses my own version of how to write my own version of that. But also due to the format, I mean, the same format in PicoAid is basically a JSON file. Not exactly. It's more like a Lua representation of a table. So there also had to be kind of a special split that could handle all the nested tables in that. So there's quite a lot of special stuff, right? I mean, there's no UI functionality in PicoAid as well. So all that is also built custom.

Yes, again, this is somewhat of a silly question, but when you're talking about writing your own split implementation or even your own tools, how are those used? Because there's no package management situation, right? You're not importing modules. So is it just a case of copying and pasting your implementation into your new cart? You can actually import like that. There's a little include statement you can say, in case I had, let's say, a Verlet engine, and then I could just do import Verlet.lua or something. That's totally doable. The challenge with that is that if you have your special Verlet engine, then it's likely to be very generic.

And if you actually want to use it for a proper game project, it needs to be more specific. And to get there, you have to rewrite it and work inside the code, and then it won't be reusable for anything else anyway. So it very quickly doesn't really work. You can use it to kind of structure your project, but it doesn't, at least for me, it doesn't help to reuse things. But for PicoCAD, for instance, one of the key things to do was, usually in PicoA, you get three functions that are called automatically. So there's the init, which kind of sets everything up. There's update, which is called 30 or 60 times per second. And then there's the draw, which just draws everything. And usually, in all the programming books and what you learn in school, you're supposed to have the...

model work in the update and then you just draw whatever the model is right but for pqa to work everything happens in the updates including the drawing and i draw an update very intertwined and mixed so there's no there's probably something happening in the draw function but most of it happens in the update function because one thing that is or at least turned out to be very difficult for me if i want to use the mouse to click on a vertex for instance how do i know where that is and i mean there's lots of ways to do that you can do rays and things in 3d that i don't know so much about but the way i saw it was that if i draw it first the 3D model. And then every time I draw a vertex, I can save that vertex to screen position inside the vertex, right? And then I kind of blend into the next step, which is the update. And I can just run through all the vertices, look at their screen positions, is any one of them close to the mouse? And get all that weird stuff, where am I in 3D, in my 2D interface, that's just solved through that step, right? Yeah, that's really neat. The same way when I draw a polygon or a face, and I can really quickly check, is the mouse inside this face? So it's very mixed up, and it's probably not how I would do it if I had another type of engine to write it. But this is what I had, right? And what I chose to do, and it works surprisingly well, right?

Yeah, absolutely. And again, a good example of the constraints. Like you said, without those constraints, someone might go to implementing ray tracing, but you found a really elegant way of doing it because that's what you had, which is really cool. So aside from the commercial tools, you know, we spoke about PicoCAD. I know, and we've spoken, you know, you mentioned your mappers and stuff, but like you've done some tools for your personal use that like, so you were the first person I ever saw do like Pico8 for slideshows when you came to the workshop at EMF Cab this year. And I know this is a tendency of everyone. You get familiar with a tool and you're like, I'm going to build all my tools in this and start doing really silly things. Do you have a favorite unintended use of Pico8 that you've done personally or that you've seen? I wasn't by any means. That's what I said. I wasn't the first to make a Pico8 presentation. The first I saw. Yeah, yeah, yeah. I know Joseph White who did the Pico8. I've seen there's a YouTube video where he does something similar. I thought I was just retraced that. I don't have any good examples for this. I once thought that I was going to make my website in Pico8 to use Pico8 to generate the HTML code, right? Because as you say, once you have a good hammer, everything looks like a nail.

or whatever the saying is, I don't know. Yeah, that's, yeah. But part of Pico8 being so sandboxed, right? You can, of course, use it to kind of send stuff into it and back and forth, but it makes it a bit hard to move out of that. Yeah, absolutely. Making your website in Pico8 would be truly like connecting it to the Flash legacy. That would be great. That'd be awesome. Would be great, though, right? To not only build the website, but have the website, a full-screen Pico8 app. That would be great. That would be nice. Yeah, it'd be lovely.

So, you know, in the intro, we mentioned, you know, your indie studio, UBSCABET, whose pronunciation I probably just butchered. And you spoke about the BBS and the model, the normal model of distributing games in the PicoA ecosystem, which obviously as a commercial studio, you know, trying to survive on this, you have to be slightly different about. Can you talk about how you approach being a commercial studio whilst interacting with the PicoA ecosystem, like how that works? on a philosophical level it's kind of difficult because as soon as i mean i've done lots of free pico 8 games as well right but as soon as i stepped out from that it felt like i stopped paying back to the community so to speak and that was a bit difficult on a mental level just okay i'm now i'm using this but have i done enough for the community etc that's that was a bit of a i wouldn't say it was a struggle but it was a very significant change in how i had to think and approach it but when i launched pico cad the first time then it was free and basically people could donate on each and people were very generous so i kind of knew that it was possible that people were I wouldn't say they were interested in paying for it, but they were at least able to pay for things, right? Even if it came from such a limited tool. Well, not limited, but at least restricted tool. So I had some ideas that it will probably work to sustain a single person if I get a nice cadence of games out. And as you said, last year, I think I released five or six games this year doing half of that. Maybe I'm trying to do a little bit bigger things and also need to kind of slow down. It wasn't really sustainable, but it was fun and it worked. So I made a modest, very modest profit last year on the first year just doing Pico 8 games. So at least it's doable.

kind of stay in the game jam mode for an extended amount of time that was hard yeah yeah because you were doing lots of experiments you know actually you share it on social media you do lots of really interesting experiments like that looked like they were taking a lot of your time whilst also shipped like i think the main one i was very excited about your submarine building experiments because i love that genre of game and then you know you were doing that and that looked like what you're focusing on and then you shipped helgineers and i was just like where did that come from i didn't see that being made at all so i guess like even you know when you're in that permanent game jam mode and you're getting a game ready to ship how much during the process of making one game are you also already thinking about working on the next one in the series or were in that in that frantic year i imagine it's changing It's very different. I mean, I did Shadow King, a Metroidvania platform game that took calendar time, I don't know, three to four months to make. And within that time, when I was kind of bored of it or a bit burnt out on level design, I guess, then I made Cosmic Collapse, which is this merging game where you merge planets into bigger planets. Which is a beautiful strategic move. Your timing with that was amazing. And that's been my best game, actually. And I made that in two weeks by just being frustrated on my main project. I try to catch when I get silly ideas that I feel that when I can kind of, for me, can I see the path from where I am now too?

it being done and to see how everything kind of falls into place then it's very easy for me to just put on the in swedish the blinkers exactly and i just go there in a day or so right and that it makes it possible to very quickly i'm in the submarine game for instance where you build your own submarine auto modules code is crap but it works it works to tell somebody an idea of what the experience could be like and it always looks like there's lots of things going on in the background that usually it's just smoke and mirrors to get that working but you can at least get the feeling of what it could be so you know actually made a proposal which is great to hear you use lots of platforms you know you use you sell across itch and steam you also have a patreon how you find is there a particular one that's like more successful for pico 8 i kind of imagine just from like vibes that like pico 8 games would sell better on itch than steam i don't know if that works out in reality how do you find them i found it uh absolutely so it also comes down to that i've had six years to build an audience on itch while on steam it's been kind of a struggle to build it up but i think on itch i've managed to sustain the titles a lot better i had a longer tail on those titles where on the steam it more becomes like a blip and then it kind of goes into into nothingness

And Patreon is nice to have. Super grateful for those people who want to give me some money without knowing what the game is like. It always makes it possible to at least I know I will have something back for the game that could pay for a musician or special art or whatever it could be. One of the interesting things about your Patreon is your upper tier. I think you released the source code as well, which I think is, you know, going back to what you said, you know, your philosophical struggles with giving back to the Pico8 community. I think it's a really great way of reconciling that, that people still get the source code. Do you find, what's your tier distribution like? Do you find lots of people are excited about getting hold of that source code? Or is that for like a niche, your niche like Pico8 community member followers?

I have four tiers. And one is like $2, get the games, that's it. And then it's five, I think, which is some sort of early access. You get to play the game way before. Then it's a source code thing. And then it's a number one fan, which is just throw your money at me and I'll be eternally grateful. But I think the lowest performing tier, or not performing, but the tier that most people are not interested in is the early access thing. Interesting. And then there's a handful of these top contributors. But I think 50-50 or 45-45 are just in the game or source code, right? And I guess that tells me that it's a very developer-centric following.

in my case on patreon right and i haven't think that's been the major struggle with making pico 8 games commercially how do i kind of break out of the community yeah that totally makes sense yeah as we were talking earlier with the fact that the technical achievements are a large part of the marketing i think there's a lot of i mean it's nice that the pico 8 developers support each other and make that viable right but yeah the breakout's important because i'm now that i'm so pico has been on itch for a couple years and i'm launching it on steam hoping to reach a bigger audience right and it's part of my worry there is right people won't have this acceptance of what pico 8 is i mean it comes with the key binds are totally different it kind of starts to lag when you build two big things even if you run it on your 16 core mega flop computer right yeah yeah so i'm trying to do a lot of expectation management so people actually know what they get god yeah that's fascinating i hadn't thought about the well i mean the constraints being part of the selling point part of the interest of any game made in pico 8 if you know pico 8 but then just being read as bad software if you're not that's how are you doing that expectation management is it like part of your pitch for these games as you reach a wide audience having to also sell pico 8 in some way i don't think pico 8 is going to be sellable through that right i mean i can't explain it just

I just have to tell people this is made on a computer from the 80s. Right, right, right. And you have to live with that. And if it starts to slow down, you're doing it wrong. Right. That makes sense. So, you know, you've got PKK coming on Steam, which I think was November 28th, which is very exciting. You've also been talking a lot, and it's also on Steam, about your upcoming game, which is Coco's Delivery Service. Is that the game that's on a different engine? That's on a different engine. What is the engine? So it's built, it's not a built-on engine, it's built on a framework called Love2D. I'm familiar with it. Yeah, cool. Which also has, as we spoke about, action scripts. And it has, the way it's built up is very similar.

And the way I stumbled into that was Cosmic Collapse, the game where you merge planets, which was somewhat of a hit. I decided to put that on iOS. And to do that, I didn't want to rewrite the code because that's boring. So instead, I wrote a layer so I could just load my Pico8 file into Love2D. And then all the function calls that Pico8s want to make instead went to my abstraction layer. And then that sorted out all the stuff with Love2D. That worked really well. And then doing all the Apple things to get it out, of course. But I guess I put it in a day or two. So it was a very small effort.

I got my eyes open to Love 2D then, of course. And also the possibility of actually having a custom-made, for me, PicoAte-like API without the restrictions, right? Which is a blessing and a curse. Definitely a lot of a curse sometimes because it's so easy to just start making stuff instead of reining in. But Cocos Livery Service is then made in. I made the prototype in PicoAte and it felt fun. So then I moved that over to my API in Love 2D. Was Cocos Livery Service needing more than you could build in PicoAte, born of the fact that you'd had this experience with Love 2D and you wanted to use that? Or was it you found a game that you could then use that facility for?

it rose from a different perspective so one thing i felt that okay i can have this game i can make it in pico 8 but then it will be a very quick arcade thing and i'm kind of want to have a break from quick things try to slightly bigger things and then i also have so the submarine game for instance that's definitely not going to work on pico 8 so there's a version of that as well in the pipe i'm very excited to hear that years away maybe but it's at least on the table but then there's another game i want to make that i hope to reveal in a few months or so that definitely not going to work on pico 8 and it's i hope that's going to be a big thing so i want to do some tech proofs before i get there i want to know can i actually release a game written in love 2d got it on steam without it exploding on a million computers as it doesn't use a virtual machine so it also solves that step right can i actually do this and then for this specific game it can be a bit bigger have a little bit more graphics and have a bit more power you know you've mentioned the upcoming game this next one in the future so i guess one of my questions about your studio as an entity is like is this a vehicle for you as an indie developer occasionally hiring out music or do you hope to grow this as a studio and bring on more people

Well, that's the question. I mean, I've run studios before and some of them grew, some didn't. It is a vehicle for me to do whatever I want. And if I feel the urge of growing and taking on some other people, then maybe. If it doesn't, I mean, the main thing is I wanted to get out of the, I wouldn't call it the rat race, but I retired of VC, I retired of founders, I retired of politics and big companies and all that. Just go back to hammering on that Commodore 64 in my friend's basement and try to get it to work, right? And just following my passions, basically. And I've been super fortunate that it's...

actually is sustainable at the moment. So we'll see what happens. I can definitely feel at times that it would be nice to have some people who were as invested into whatever I'm making as I was. I mean, you contract people to do art and music and things, and they are nice and they like what they're doing, but they're still just getting paid, so to speak. And then I can just have that daily back and forth with people who want the same thing. But we'll see in the future. Final question, which may just, you know, the answer may be no. There's a lot of excitement about Picotron, ZEP's next project, kind of like Pico 8, take into a...

mock os level and being such a prolific builder of tools and as we found out influencer of the api i'm very intrigued to know if you played with it at all have you got any designs or things you're thinking about for picotron i did meddle a bit with it but for me when i go up to that level then i might as well do everything myself i think that's where i ended up and still early in development right and there's i don't like to make things that might break because of someone else and i'm also thinking that the same with peak weight i came in fairly late people have sold most of the problems and just use them right and i think picotron will probably have a similar journey And where I am now with moving my own PicoAid API into Lab2D, that solves a lot of the problems that I hoped Picotron would solve as well. And I mean, Picotron looks amazing and people are doing super cool things in it, of course, because people are always super creative. But I'm not sure yet whether I should or how I should approach it. I mean, now a deal breaker for me is that it can't export to native binaries at the moment, right? And I need to be able to do that to make a living. So maybe when that is, we can go back and see if it solves something. Cool. Awesome. Well, Johan, thank you so much for joining me today. This has been wonderful. I'm so glad you finally got to cover PicoAid and your work. Thank you. Yeah, thank you. Happy to be here.

Frequently asked questions

How long is this episode of Software Engineering Daily?

This episode is 47 minutes long.

When was this Software Engineering Daily episode published?

This episode was published on November 27, 2025.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this Software Engineering Daily episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.