New #pico8 tool on my website
TheFontCircle
Did you know pico8 can use a custom font? I only just found out because its deep in the manual and requires a lot of raw data encoding. So I made a gui to directly poke around in font memory and then export the changes as either a file you can load back into the app or as a snippet of pico8 code to initialise the font in your own application.
As with all my uploads pico8 devs can use the cart image to look in the code and see how it all works.
Unlike my other projects I didn't really know what I was doing when I started so the code is a MESS. Version 2 will probably be neater and have a few QoL improvements but right now I need a nap.
Okay, post nap I now see the biggest flaw in this application, the fact that I did a very simple export function for a very simple unpack code, but the problem with it is that the exported code has like 515 tokens of data, whereas if I'd packed all that into a string it would be about 3 tokens.
Obviously this will be the first change in v1. 2
Added this change to 1.1 because it struck me that it would be an easy fix.
@The4thCircle see also the appendix about P8SCII control codes in the docs + https://www.lexaloffle.com/bbs/?tid=38692 → means you can poke a font into memory with 2 tokens (? for print + string with memory poke code then binary font data) and minimum characters
@merwok thanks! I'll read up on this and put this in v1.2