Jump to content

[1.16.5] ExceptionInInitializerError when registering custom Biome with custom SurfaceBuilder


Recommended Posts

Posted (edited)

I am currently creating a custom dimension with custom biome.
Since the dimension has no real surface that has to be created, i have used the default surfacebuilder (from vanilla), until now.
but now i have created my own surfacebuilder for the biome. but now i get an error when registering the biome.

this is the log:

latest.log

this is the registration class of my biome
this is my biome
and this my surfacebuilder

 

 

Edited by Luis_ST
Posted

There's a little error that sneaks by here that explains the issue: 'Caused by: java.lang.NullPointerException: Registry Object not present: industry:default_deepslate'.

You statically held an instance of a registry object and classloaded the associated object before registry events have passed. Surface builders are registered after biomes after all. Instead, wrap the instance in a supplier. This should be done for all registry objects including the Features. Just make sure to remember to register the configured data during common setup.

At some point, I suggest moving to JSON as your biome could be fully declared within there.

Posted
8 hours ago, ChampionAsh5357 said:

Instead, wrap the instance in a supplier.

like that:?

	public static final RegistryObject<SurfaceBuilder<SurfaceBuilderConfig>> DEFAULT_DEEPSLATE = SURFACE_BUILDERS.register("default_deepslate", 
			DefaultDeepslateSurfaceBuilder::new);

 

8 hours ago, ChampionAsh5357 said:

Just make sure to remember to register the configured data during common setup.

how exactly, is there a class/method i have to use.
I currently use the vanilla registry because I have not found anything from forge for the registration
 

8 hours ago, ChampionAsh5357 said:

At some point, I suggest moving to JSON as your biome could be fully declared within there.

I will think about this, but I will probably not move the biome to json because I hate json

Posted
7 hours ago, Luis_ST said:

like that:?

The ConfiguredSurfaceBuilder when being passed into the biome.

7 hours ago, Luis_ST said:

I currently use the vanilla registry because I have not found anything from forge for the registration

Call the vanilla registry event within common setup. That's when these objects should be registered anyways.

Posted
52 minutes ago, ChampionAsh5357 said:

The ConfiguredSurfaceBuilder when being passed into the biome.

thanks that fixed the problem

53 minutes ago, ChampionAsh5357 said:

Call the vanilla registry event within common setup. That's when these objects should be registered anyways.

I'll change that later, but thanks for your help

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Well, when I log in to the server, sometimes within an hour, sometimes within a minute, the server closes and informs me that there was a Ticking entity error. Below is the crash report
    • Try switching to Windowed or Borderless Window mode in Minecraft. These modes make it easier for the recorder to capture gameplay, as it still has access to the display without the game taking up all of the graphics resources.
    • This forum is for Forge, not NeoForge. Please go to them for support.
    • Forge version: 55.0.0 Minecraft version: 1.21.5 Downloads: As this is the start of a new version, it is recommended that you check the downloads page and use the latest version to receive any bug fixes. Downloads page Intro: Good evening! Today, we have released our initial build of Forge 55.0 for Minecraft 1.21.5. 1.21.5 is the newest member of the 1.21 family of versions, which was released yesterday on March 25, 2025. As a reminder, the first minor (X.0) of a Forge version is a beta. Forge betas are marked as such on the bottom left of the title screen and are candidates for any breaking changes. Additionally, there are a couple of important things to note about this update, which I've made sure to mention in this post as well. Feel free to chat with us about bugs or these implementation changes on GitHub and in our Discord server. As always, we will continue to keep all versions of 1.21 and 1.20 in active support as covered by our tiered support policy. Cheers, happy modding, and good luck porting! Rendering Refactor For those who tuned in to Minecraft Live on March 22, 2025, you may already know that Mojang have announced their intention to bring their new Vibrant Visuals overhaul to Java in the future. They've taken the first steps toward this by refactoring how rendering pipelines and render types are handled internally. This has, in turn, made many of Forge's rendering APIs that have existed for years obsolete, as they (for the most part) can be done directly in vanilla. If there was a rendering API that was provided by Forge which you believe should be re-implemented, we're happy to discuss on GitHub through an issue or a pull request. Deprecation of weapon-like ToolActions In 1.21.5, Minecraft added new data components for defining the characteristics of weapons in data. This includes attack speed, block tags which define efficient blocks, and more. As such, we will begin marking our ToolActions solution for this as deprecated. ToolActions were originally added to address the problem of creating modded tools that needed to perform the same actions as vanilla tools. There are still a few tool actions that will continue to be used, such as the shears tool action for example. There are some existing Forge tool actions that are currently obsolete and have no effect given the way the new data components are implemented. We will continue to work on these deprecations and invite you to chat with us on GitHub or Discord if you have any questions.
    • In summary, a full mod to adjust mining progress in such a specific way does not yet exist in its exact form, but it is possible to find mods that change certain aspects of progression (e.g. "Harder Ores").
  • Topics

  • Who's Online (See full list)

    • There are no registered users currently online
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.