-
Recently Browsing
- No registered users viewing this page.
-
Posts
-
So what is the code for enchanting and where is the #accept? -
By CassAsmolith · Posted
Okay managed to track down which mod was causing the problem and works flawlessly without it. It was Environmental from Team Abnormals. -
I have completed everything you mentioned, and here is an example from GitHub: https://github.com/Tutorials-By-Kaupenjoe/Forge-Tutorial-1.19.3/blob/7-treeGeneration I would like you to look at the two main classes as follows: ModConfiguredFeatures, located in the package net.kaupenjoe.tutorialmod.worldgen ModWorldGenProvider, located in the package net.kaupenjoe.tutorialmod.datagen If you're using version 1.19.4-45.0.39 without updating to 45.0.40, the mentioned code works fine. However, if you switch to version 45.0.40 and try to add the method ModConfiguredFeatures::bootstrap, there will be an immediate issue. It seems like it cannot accept a method with a parameter as an instance, but it can still work properly with an instance that doesn't have an instant parameter, such as BootstapContext<PlacedFeature>. -
By ChampionAsh5357 · Posted
Ignoring the mismatched format, this doesn't really explain anything about what is needed. First, you have a bunch of random classes which you don't define: ExampleEntityModel, the layer location, model layers, etc. Even if they are not relevant, you should just hide them behind a `//...` so they don't detract from your main point. For example, what about registering the layer definitions? the entity renderer? Anything that is not explained should be mentioned to use the same method as usual. You should also explain why adding those two layers would do what you needed. Additionally, you need to explain when a different model layer should be used, since not all mobs will have the exact same dimensions as the player (e.g., piglin). This will crash, it needs a semicolon. This is already added for HumanoidMobRenderer, so it is redundant. This will crash, you need to pass in a ModelManager from the context. Additionally, the type parameter for HumanoidModel should be inferred and not just removed. -
By ChampionAsh5357 · Posted
I just look in the errors for the name of a mod and my first instinct is to remove it. There are a few other cases, but that's usually the most common one if you are using a modpack.
-
-
Topics
-
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now