{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreihdd2nwmw7xyadn7k3si45oh3coniccsiyexn7w2ytfgz3dxuvjl4",
"uri": "at://did:plc:pvz7ox4x2ehjiezsahttqyyz/app.bsky.feed.post/3mkiwioeoeno2"
},
"path": "/viewtopic.php?p=450780#p450780",
"publishedAt": "2026-04-27T18:49:35.000Z",
"site": "https://forum.luanti.org",
"tags": [
"meggs413"
],
"textContent": "Hi All! My apologies if this isn't the right place to post such a question, but I had trouble finding answers online. So, I have been working on a custom mapgen mod that completely overhauls terrain generation and the biome system. It's a mineclonia mod because I like the item set. The mapgen has been working great for terrain and simple deco, but I have a problem with placing schematics.\n\nAs far as I can tell, I'm not able to use the inbuilt register_decoration function, because my terrain uses single node and I coded my own biome system that is substantially different from the standard. However, placing the schematics manually using place_schematic_on_vmanip has been causing a large issue: my schematics get cut off at chunk borders! I've seen this be an issue discussed before but not generally in the context of using singlenode mapgen. I'm wondering, is there a standard way to place schematics when using singlenode mapgen that doesn't result in this issue? Either a way to rig up the register_decoration function to my own biome system or a way to code around the failure at chunk boundaries when using place_schematic_on_vmanip, or is there another function I should be using? I'm still pretty new to this.\n\nSome notes: I tried installing a chunk visualiser mod and was able to confirm that the cutoffs are at chunk boundaries. They don't only happen with large schematics, sometimes even small trees are cut off, so I don't think its a size issue but rather an issue innate to the way I am coding.\n\nStatistics: Posted by meggs413 — Mon Apr 27, 2026 18:49\n\n* * *",
"title": "Modding Discussion • How to use Schematics with singlenode mapgen",
"updatedAt": "2026-04-27T18:49:35.000Z"
}