end_of_eden VS prime-intersection-grid

The source code is now open and can be found here: https://github.com/BigJk/end_of_eden

I have an overworld solution of my own that's proprietary right now. it's based on 2 intersecting graphs with random origins and places where the values intersect in certain ways. More detail here. The proprietary bit is biome related and lives above this library. It also uses seeds the way I've modified this lib to do.

This approach works well, even if the layout is overly grid-like. I built a couple of libs to assist: the first computes values for the grid, the second is a biome system for the engine to map properties to biomes and select the biome for any given coord. The first is already open: https://github.com/khrome/prime-intersection-grid the second is not currently open

After building a simple prototype for a generative world, I took a few weeks and formalized my code in some foundational libraries (things got crazy internally) and am now tying that back together in a client/server architecture (to then be wrapped in electron). While the game is still in progress (my rough plan is an unbounded diablo-like, quest driven adventure game, but with more of an ikari warriors style pacing and some elements of Myth and classic Ultima era RPGs), I'm very happy with how the foundational stuff I've built is going so far. I can't post everything (not all open source), but here are a couple of the relevant libs: https://www.npmjs.com/package/submesh-treadmill https://github.com/khrome/prime-intersection-grid (no docs currently, but this is how I layout features in the game world without needing to compute things outside the calculated cell)