I've been building a game via the API, and in my quest to figure out what savegame systems I can use (if any) I wrote a little script to dump the contents of _ENV. This seems to list the API, both documented and otherwise, so I thought folks might find it useful.
So far the only undocumented feature I've found and successfully used is clip3d, which you can use to set a clipping volume for subsequent voxel rendering operations. It doesn't seem to get reset every time you run a game, so be sure to clean up after yourself :)
Parameters seem to be x0, y0, z0, x1, y1, z1
Anyway, here's the rest of the dump:
This works in pico-8 too. I wouldn't recommend using ones that start with an underscore though. That's a pretty universal way of indicating that something is meant to be under the hood, which means it's more likely to change in future versions.
for comparison, the functions that are the official API are documented here: https://www.lexaloffle.com/vox_api.txt
I suspect that many here (pal sget etc) are added to run pico-8 carts, and there’s no separation between vox mode and p8 mode, for better or for worse ;)
Yep, I was mucking about with pal() the other day and found you can use it to remap the first 16 voxatron colours to anything in the pico8 palette. Nothing else seemed to be affected by it.
[Please log in to post a comment]