3 ms·

What part of gameplay will you use it for?

• MrLeap 2y ago
  I'm thinking that bare minimum it would be a good way to handle persistence. It's a simple way to do a KV store that's easy to write to a file. I think the same thing about sqlite. The fact it comes with baked in graph traversal means I could offload pathfinding to it for certain kinds of projects (thinking like turn based strategy games on a hex grid, multiplayer board games). I'm a big fan of isomorphism in anything multiplayer. There's some more esoteric things I want to think about, I just don't know datalog enough yet to know how much magic this will bring to these ideas. I need to learn enough to answer questions like "how hard is it to solve a game of clue (the boardgame, with the rooms and the murder by candlestick) with a query in cozo?" -- If it's no sweat, like I think it might be, then that opens up a lot of possibilities for deductive AI systems. Constraint based solving / deduction is what I'm really interested in. Once I get a sense of what I can do, the ideas will come. State machines, graphs and trees are data structures I use _constantly_. I want to love cozo enough to promote it to handling those almost every time I use one that might benefit from persistence or have any chance of enjoying emergent mechanics from being able to create cross system relations. I saw the api had dijkstra's but I didn't see A* which seemed interesting. Lots to learn.