I've been experimenting with exposing the whole World Builder API to an MCP toolkit that AI can interface with. My thoughts were, I could ask it to generate the rough outline of maps based on a storyline I've written, or a few prompts, and be able to iterate on it quickly.

The first time, it struggled a bit as it hadn't checked the context of the tiles and how they fit together:



Every tile in a tileset can have an optional metadata record (that the AI itself filled in).



Which produced this:



Much closer, but it still doesn't understand edges properly. After some tweaking to the shape schema, and reducing mask to 3x3, we get this:

Nowadays, you're supposed to be uncontrollably angry that anything uses AI, but as a developer I already know it's about as ubiquitous and irreplaceable as a pocket calculator at this point. Nobody is going to sit and refactor hundreds of files by hand any more, just like nobody is going to sit and do long division on paper.

I can see this stuff being really good for game content. I haven't exercised it properly yet, but in theory it can do everything from making maps to making new quests, filling in item specs, sorting out treasure lists, etc.

It needs constraints to stop it going wild, but frankly I'm amazing by what it's achieved already. I'm hoping it can make new tileset images as well, because those are a nightmare to make