Jump to content

Luis_ST

Members
  • Posts

    5704
  • Joined

  • Last visited

  • Days Won

    72

Everything posted by Luis_ST

  1. you don't need it if your mod only runs on the client, this method would always return true you still haven't understood Dist and DistExecutor, if your mod only runs on the client, the physical and logical side is the client
  2. again what exactly do you want to do, show your code, because I can't find a solution for your problem with:
  3. what exactly should your mod do if you want to write a client only mod you should use DistExecutor, if you only have one method, class, code part that is only executed on the client, the logical side is the better choice, therefore the question what you want to do
  4. https://mcforge.readthedocs.io/en/latest/concepts/sides/#writing-one-sided-mods
  5. overwrite the method canApplyAtEnchantingTable in your item class
  6. create a new ItemEntity and and it to the world
  7. you need to create a item for the block
  8. your code looks okay this will set the max height to 64, im not 100% sure but it can be that this overwrite your TopSolidRangeConfig if(!(event.getCategory().equals(Biome.Category.NETHER) || !(event.getCategory().equals(Biome.Category.THEEND)))) { This line is completely wrong, if you want to generate your ore in the overworld, because here it is checked whether it is not the end or not the nether, so minecraft will try to generate the ore in all dimensions replace || with && (is not absolutely necessary) you also need to register your ConfigureFeature use this to register your ore private static <FC extends IFeatureConfig> ConfiguredFeature<FC, ?> register(String name, ConfiguredFeature<FC, ?> configuredFeature) { return Registry.register(WorldGenRegistries.CONFIGURED_FEATURE, new ResourceLocation(MOD_ID, name), configuredFeature); } -> Edit: fix the two errors I have described above and register your feature, this should fix your problem
  9. create your own thread you should look again, at the first post from the author of this thread
  10. 1.12.2 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  11. please create your own thread
  12. please update your git repo, as this version of the mod (on github) seems is outdated, or is not complet...
  13. this is because biomes are registered before world features (carvers, features, surfacebuilders), the solution for this is simple either you move the biome to json or you use the BiomeLoadingEvent to add world features to your biome
  14. use a git client, look in the internet the are a lot of good github tutorial
  15. please post a git repo of your mod so i can use debugger
  16. no, do this in one class, if you have a class for server event and one for client events then create one for both (ModCommonEvent)
  17. the packet handler must be registered on both sides (server and client), there must be no dist in the EventBusSubscriber
  18. you only register your packet handler on the client side, move the FMLCommonSetup event to a class without Dist#CLIENT
  19. please post this class "com.Cake.usm.events.ModClientEvent" because a NullPointerException was thrown in this class
  20. the structure works almost perfectly there are a few small things that i have to change, only optically one more little thing, I'm currently trying to understand the world generating, here I tried to generate a custom cave, but I have again the problem that chunks not or not complete load. looks like this: this is the code: https://github.com/Luis-st/Forge-1.16.5-Industry/blob/main/src/main/java/net/luis/industry/common/world/carver/ocean/OceanWorldCarver.java I hope you can help me again
  21. Please post the log because I think the log should show something
  22. run the init method of the packet handler in the FMLCommonSetupEvent
  23. yes😀 looks okay, do you register the packet handler?
  24. please post your code use the code feature or use github or something similar like that
×
×
  • Create New...

Important Information

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