TIC-80 VS PixelVision8

Or the more free TIC-80. I have paid for both, but never used either enough to be able to say one or the other has any significant advantages.

https://tic80.com/

I wish the community moved to an open source option like TIC-80[0].

0. https://tic80.com/

Main differences are: 16:9 aspect ratio, no cpu limits and many languages to tinker with: lua, js, squirrel, wren, janet, wasm, ... and just recently - a Python support was added.

https://tic80.com

Included native builds for windows, mac, linux, html, and also TIC-80's .PNG, .TIC and .LUA formats. Try out the web version here - https://tic80.com/play?cart=3424 See the TIC-80 wiki for instructions on exporting https://github.com/nesbox/TIC-80/wiki

https://github.com/nesbox/TIC-80/ - TIC-80 website (for running .lua .png or .tic files) as well as TIC-80 documentation.

Try https://tic80.com/ instead of PICO-8, it's a free open-source alternative and still fun.

Tho personally I've come to prefer making my games in https://love2d.org and https://tic80.com

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?