(1.16.5) [SOLVED] TopSolidRangeConfig blocks spawning outside parameters

[Jurassicash]

Hey there, I set up my ore generation file and the first ore I've made seems to be spawning a bit above the maximum height I set. I've been thinking in terms of the world coordinates when setting these numbers, with bedrock as 0 and everything else going up from there. 

public class OreGeneration {
	
	//the actual individual ores
	public static void generateOres(final BiomeLoadingEvent event) {
		if(!(event.getCategory().equals(Biome.Category.NETHER) || event.getCategory().equals(Biome.Category.THEEND))) {
			generateOre(event.getGeneration(), OreFeatureConfig.FillerBlockType.NATURAL_STONE, BlockInit.EGG_ORE.get().defaultBlockState(), 4, 15, 31, 15);

		}
	}
	
	//can be called at any time to make an ore
	private static void generateOre(BiomeGenerationSettingsBuilder settings, RuleTest fillerType, BlockState state, int veinSize,
			int minHeight, int maxHeight, int maxPerChunk) {
	settings.addFeature(GenerationStage.Decoration.UNDERGROUND_ORES, 
			Feature.ORE.configured(new OreFeatureConfig(fillerType, state, veinSize))
			.decorated(Placement.RANGE.configured(new TopSolidRangeConfig(minHeight, 0, maxHeight)))
			.squared().count(maxPerChunk));
	}

}

here's a picture of the ore, about 10 blocks above the number I set. https://imgur.com/a/8jflRKz

Is minecraft using a different set of numbers than the world coordinates? Or is the range just looser than I'm expecting it to be. Thank yall for help with this. 

Edited April 1, 2021 by Jurassicash

[Jurassicash]

5 hours ago, diesieben07 said:

The position given by the placement is only the starting position of the ore gen. The ore gen then generates in a patch around that position, so can end up higher (depending on your vein size).

Alright! Thank you for the answer, I was just curious how it worked.