Hello! Any help would be appreciated. Thanks!

 

I was updating my mod to forge 1.16.3 when I noticed it no longer works because the CountRangeConfig class is missing from the Minecraft files.

 

Is this a bug? Did the name change? Is it something else entirely?

2 hours ago, XenonIX said:

I was updating my mod to forge 1.16.3 when I noticed it no longer works because the CountRangeConfig class is missing from the Minecraft files.

I think CountRangeConfig no longer exists. You could look for a suitable replacement by looking at which classes implements IPlacementConfig. Perhaps TopSolidRangeConfig?

Placements are broken up into multiple parts. If you wanted to do use an old placement, you'll probably need a combination of at least two placements to be able to do that. Which ones you choose are up to you.

9 hours ago, vemerion said:

I think CountRangeConfig no longer exists. You could look for a suitable replacement by looking at which classes implements IPlacementConfig. Perhaps TopSolidRangeConfig?

I tried that before I posted this already. I thought that would work, but to no avail. I'll try Ash's idea next.

1 hour ago, XenonIX said:

I tried that before I posted this already. I thought that would work, but to no avail. I'll try Ash's idea next.

So what can I combine with TopSolidRangeConfig to fix these errors?

 

First, that is not how you do generation first of all, see Problematic Code 11.

Second, you can't create a configured placement without specifying a placement. What are you configurating?

Third, there is some placement called "count" and some placement called "range" and a combination of those two will get your ore generating correctly.

Fourth, you could've just looked in Features and looked at how ores do it.

Fifth, there is no fifth point, fix the generation again (first point is important).

Sixth, use upper camel case for class names.

Seventh, use lower camel case or snake case for non-static final fields.

Eighth, don't reconstruct a list many times when the information is static. Make it a global field.