picolove VS PixelVision8

Picolove, written in lua for love2d: a very good starting point, especially if the engine you're using has support for lua. Has been used for "expanded" versions of games, because it's very easy to modify the resolution of the display and things like that. Works for simpler carts like Celeste, but is not memory accurate!

You should check out picolove (https://github.com/picolove/picolove). It’s the PICO-8 API implemented in Löve. It can run PICO-8 games, but it doesn’t have support for the PICO-8 dev tools (code editor, sprite editor, etc…)

PicoLove also see love2d below

I've never used it, but you could try picolove. It's a reimplementation of the PICO-8 API in Love2D. So, only the code part is there and you don't get the music/sprite/map editor, and all the other stuff that makes PICO-8 PICO-8. If you plan on buying PICO-8 later though, this could be a good primer to learn the API for free

Sprites in Power Vision 8 are all 8x8 pixels in size, when your game starts up the file "sprites.png" is loaded and chopped up in to 8x8 images. Each of these images is then loaded into the memory of the sprite chip until it runs out of space. Each sprite is given an index number at load time (starting from 0) and you can use that index to fetch a particular sprite.

We don't talk enough about how much it "costs" to work on large open-source projects by yourself. I summed up my experiences building Pixel Vision 8 for the past 6 years in "The Dark Side of Supporting an Open-Source Project" on u/hashnode - https://jessefreeman.hashnode.dev/the-dark-side-of-supporting-an-open-source-project

Space Station 8 is a Micro Platformer created in 72 hours for Ludum Dare 49 based on a game I used to play on my original Macintosh called Spacestation Pheta. Space Station 8 is also heavily inspired by Bitsy and my Fantasy Console, Pixel Vision 8, which I used to create the game.

I have been working on my game engine, Pixel Vision 8, for the better part of 6 years now. One of the challenges of working on any sizeable open source project is writing all the documentation and tutorials. I've always been fascinated with designing automated build systems, and it occurred to me that I could create a tool to help me streamline this entire process. The idea was straightforward, could I analyze a code file and break it down into individual steps?