Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


Forum Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


diesieben07 last won the day on June 15

diesieben07 had the most liked content!

Community Reputation

7895 Excellent

About diesieben07


  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This. The reason for this is that DeferredRegister relies on static initializers. If you put your RegistryObjects in some random class it is not guaranteed that that class is actually initialized by the time your DeferredRegister is. Hence: Put the DeferredRegister and its entries in the same class. @ObjectHolder is explained here: https://mcforge.readthedocs.io/en/latest/concepts/registries/#using-objectholder
  2. First of all the BLOCKS and ITEMS fields (i.e. your DeferredRegister instances) should not be in a separate class. Put them in the same class or you will have issues. No, you cannot, because then you defeat the entire purpose of DeferredRegister. You must create your registry objects (blocks, items, etc.) in the registry event. DeferredRegister manages this for you. If you don't want this, you can also manually subscribe to RegistryEvent and create and register your things there. You can then use @ObjectHolder to obtain the instances for your registry entries. You can also mix and matc
  3. Java 16 is not yet supported.
  4. No. And this thread is 7 years old.
  5. Really old Minecraft versions are no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  6. You need your own IRecipeSerializer and ICraftingRecipe implementations. Then in getRemainingItems you can do whatever logic you need.
  7. No no no. You have to subscribe to the event.
  8. There is none that I know of. But I will be working on a patch to Forge to work around this problem.
  9. Bug with "Create". Make sure it is up to date, talk to the mod author if it already is.
  10. You installed Optifine for 1.16.4 on 1.16.5. Refer to the Optifine downloads page regarding compability.
  11. You have to use BiomeLoadingEvent for this in 1.16.3+.
  12. Override getHighlightTip in your Item class.
  13. Which map do you mean? I am not sure what you mean here. I meant you should have a Map<ServerWorld, WorldSavedData> which holds your WorldSavedData instance. You cannot use the normal way of getting it, because that uses a non-thread-safe map. These are basic Java concepts. Objects in Java are passed by reference. Yes, you can have issues. Multiple threads require synchronization as long as at least one of them is writing. He's joking. Don't use Unsafe. Capabilities is the same. Mixins has nothing at all to do with this.
  14. Java 16 is not yet supported.
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.