Have you tried substituting in some dummy values to see if they work? If not, try that. If it works with dummy values it must be the values you are setting. Also try printing the values to make sure they aren’t empty.
Doesn’t seem to have something to do with empty values.
Error sometimes does not appear wiht lower values for some reason but unsure, sometimes it’s random, but none of the values are nil for sure.
It does seem to appear sometimes at big positions I think.
But again, not sure.
Also I don’t see why it would error at huge positions because I’ve made infinite terrain generators that still work fine at positions beyond 5 million.
X and Z is the current position the terrain is being generated at. It’s like a starting position for where to start generating or where it currently is at.
When you make terrain through the means of position, it is very important that the values of the first vector are lower than the second’s. It’s a little known fact about terrain and I also ran into a similar issue for a game I was making.
I recently encounter this bug, and it appears to be a float point issue. One of my wedges position was extremely far away like math.huge far away, and it had this problem. You will need to check for parts that is extremely faraway from the origin and remove them before fill block.