Jump to content

Recommended Posts

Posted

I am trying to implement a model for a mob into Minecraft and am running into trouble with the ModModelLayer file and the downloaded model Java file from blockbench. Both attempt to create a new ResourceLocation instance however after browsing the code I can't find a public constructor for Resource Location within the game files and can't instantiate it. Am I missing something here? 

Posted

Use one of the static methods on the class to create a new instance.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Posted (edited)

In the Forge docs stands the following:

Quote

The ResourceLocation is final and its constructor is private. There are alternatives depending on your usecase:

  • new ResourceLocation(String, String) -> fromNamespaceAndPath(String, String)
  • new ResourceLocation(String) -> parse(String)
  • new ResourceLocation("minecraft", String) -> withDefaultNamespace(String)
  • of -> bySeparator
  • isValidResourceLocation is removed

Here is the Link for the whole Changes from 1.20.6 to 1.21: https://gist.github.com/ChampionAsh5357/d895a7b1a34341e19c80870720f9880f

I experimented around in my mods and they work

Edited by Pale Mannie

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



×
×
  • Create New...

Important Information

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