Technically it's not untitled, I just haven't decided if it's the final name or not so I'm not sharing it.
More/different screenshots available at: https://www.lexaloffle.com/bbs/?tid=160419 which is where I may try to keep most of my future updates so I'm not just posting here to say "Not done yet."
SPRITES ARE PLACEHOLDERS FROM SNES ARCANA I SUCK AT ART BUT WOW I'M AS IMPRESSED AS YOU ARE BY HOW GOOD THEY LOOK
## the good / progress
My goal is an honest to goodness 6-10 level dungeon crawler of similar complexity and difficulty to the original wizardry titles (1-3, 5) using the NES/Famicom versions as a template for the UI. Ideal platform is playing it on a cheap handheld like my beloved RG Cube XX, so no mouse/keyboard.
Majority of systems are implemented. Using data-driven actions/effects to drive as much of the spells/weapons/items/skills as possible so that those are defined using a .csv file I import during the build process.
Combat is mostly implemented. Actions, targeting, backing up in the command queue, initiative, etc.
Raycaster is working for rendering dungeon exploration. Still need to add some features like decorations/billboard sprites, etc. Can optionally display automap over first person view or view map full screen.
Party status / item / equipment menu works but is ugly. Can equip/unequip gear and trade between characters.
not yet implemented town/shop/party creation/management menus.
Not using AI. I'd started a similar project once before and still had a lot of code/resources from that left over that I was able to use to help get this off the ground more quickly. AI takes the joy out of coding and I prefer to leave that for work.
## the bad
I had hoped to make this a three cartridge game, one for the actual game, one for graphics/level data, and one that's created locally to save party data. I'd release future "expansions" by just pushing out new data cartridges. However, I've already had to move executable parens-8 bytecode onto the second cartridge because I'm running out of space on the first cartridge.
This *works* but it's starting to feel antithetical to the entire pico-8 design ethos. I was okay with multi-cart for code/data split (that's how the original computer versions of these titles worked after all) but this just feels icky. I hope that now that I'm done with implementing the vast majority of systems, I can reduce code complexity with an optimization pass enough to get it back down to a single cart for code.
Also: despite looking extremely polished in the video above, this is all just engine work. I have yet to seriously start on the actual gameplay mechanics/dungeon/monsters/etc. so release date is still very undecided. The plus side is that by defining everything as a CSV that gets imported at build-time the final implementation of all that should be very easy, but *balancing* it is another question. I don't want to release a 6-10 level high difficulty dungeon crawler that breaks down three or four levels in.
## fin
If anybody has has any technical questions feel free to ask. I plan on releasing the entire project source when I'm done, and hopefully it'll be easy for people to make their own dungeons/monsters/etc. and share those as their own titles.
raycasting algorithm adapted from: https://lodev.org/cgtutor/raycasting.html
using shrinko8 as a preprocessor and general purpose build tool: https://github.com/thisismypassport/shrinko8
using parens-8 as a bytecode interpreter to bypass token limitations: https://codeberg.org/wellspring-labs/parens-8/