ÆROSØL ✴️

Patrick's Parabox, the award-winning incredible puzzle game from @ClockworkPat, is coming to Nintendo Switch and PS5 on July 26! We're so excited to bring this amazing game about boxes inside boxes inside boxes to more players.

TEH SPACE TL;DR This was an experimental attempt to make invisible structures out of inscription relationships- using inscriptions as "you are here" maps. Teh Space all started with Das Cube, whose parent was inscribed on November 4th, 2023- shortly after Parent-Child was merged into the Ordinals protocol. Still months before reinscriptions and other such edge cases were formally to be assigned positive inscription numbers. It was one of the more exciting development periods for users of the protocol since we were still in the early phases of "what do we do with this". I'd argue we're still in that phase as we traverse galleries and the problem of on-chain collection metadata standards. But to take a break from the arguing about what everyone "should" do, I'd like to recap something we "could" do instead. Das Cube (and the other shapes in Teh Space) uses a primary parent as a map of what the pieces might look like. Each following inscription beneath that or associated somehow is a red dot map of where that inscription lives in larger shape. I laid this out such that: + child = -1 on the Y axis (one down) + sibling = +1 on the X axis (one to the right) + resincription = -1 on the Z axis (one deep, away) By using this kind of navigation, one could make shapes invisible to explorers but made out of data tree connections formed through inscription relationships. My initial hope was that making Das Cube would yield a cube when someone eventually made a 3D inscription relationship viewer. Was hoping to make someone say "wtf is this doing here" years down the road. But that task ended up gargantuan and maybe impossible due to the fact that inscription relationships don't adhere to the rules of 3D space. I've since made and found a bunch of things that break these 3D rules, so I'm not sure a comprehensive viewer logically can be built, outside of being purpose-built to show a very specific few collections. @boppleton put something like this together over a year ago (and was pretty successful- much as anyone could be). We were able to successfully model a few shapes, but very quickly found collections that broke the rules. If we adjusted to rules to fix that new edge case, we broke the previous collection views and so on. @ModalL0gic (tomorrow's writeup) actually now being one of the greatest offenders. While going through this I also remember I was trying to figure out how to patch botched parent-child relationships so there are goofy reinscriptions all over this whole series and its almost impossible to navigate form shape to shape. I wasn't actually patching any botches relationships, but in one case I was trying to find a way to back date a main parent that wasn't present (it kinda worked) and redo something that was done improperly (it didn't work as well lol). Anyway, below is a preview of the "Running" shape as I think this image best describes the concept. Sorry if this is confusing af I have no idea how to properly and concisely explain it. There is a gallery and its submitted to @lifofifo's repo, but I don't think this is properly indexed anywhere at the moment so we're stuck poking around the explorers atm due to backed up indexing tickets. Which isn't a bad thing. Links to shape parents in the following posts. If you made it here ily and good jarb.