Modder Support
This is the support section for those modding with Forge. Help with modding goes in here, however, please keep in mind that this is not a Java school. You are expected to have basic knowledge of Java before posting here.
Subforums
-
- 5.4k
- posts
42648 topics in this forum
-
- 3 replies
- 72.4k views
-
- 1 reply
- 99 views
-
- 3 replies
- 173 views
-
- 2 replies
- 288 views
-
- 1 reply
- 127 views
-
- 0 replies
- 93 views
-
- 5 replies
- 155 views
-
- 1 reply
- 102 views
-
- 4 replies
- 163 views
-
- 2 replies
- 100 views
-
- 4 replies
- 175 views
-
- 2 replies
- 144 views
-
- 4 replies
- 224 views
-
- 12 replies
- 324 views
-
- 2 replies
- 195 views
-
- 10 replies
- 227 views
-
- 7 replies
- 171 views
-
- 2 replies
- 206 views
-
- 7 replies
- 215 views
-
- 2 replies
- 194 views
-
- 1 reply
- 114 views
-
- 2 replies
- 171 views
-
- 6 replies
- 189 views
-
- 4 replies
- 183 views
-
- 2 replies
- 110 views
-
Posts
-
show the code of your Structure, if possible via a git repo -
By diesieben07 · Posted
Is this the client or the server not starting? Show the debug.log. -
Hello, I am trying to play Minecraft with a friend on a server but I need forge for it and it isn't starting. It just says this mesage: Memory Heap: 64 / 2048 MB (3,1%) OffHeap: 36 MB It also doesn't tell me any bug reports. Please tell me how to fix it. -
By Cratthorax · Posted
Don't be silly. A script kiddie is capable of basic copy pasting. I can't even do that. However, one more thing to add. How do you connect the registered FlowingFluidBlock, to your actual FluidBlock.class? I wasn't aware that you can actually customize the FlowingFluidBlock RegistryObject(or any other RegistryObject in that regard). Do it like that, and take info from the vanilla FluidBlocks how to build your FluidBlock.class accordingly: Change that... public static final RegistryObject<FlowingFluidBlock> OIL_BLOCK = MatLibRegister.BLOCKS.register("crudeoil", () -> new FlowingFluidBlock(() -> MatLibFluidOil.OIL_FLUID.get(), AbstractBlock.Properties.create(MATOIL) .doesNotBlockMovement().hardnessAndResistance(100f).noDrops())); ...to that... public static final RegistryObject<MyCustomFluidBlock> OIL_BLOCK = MatLibRegister.BLOCKS.register("crudeoil", () -> new MyCustomFluidBlock(() -> MatLibFluidOil.OIL_FLUID.get(), AbstractBlock.Properties.create(MATOIL) .doesNotBlockMovement().hardnessAndResistance(100f).noDrops())); ...and name your FluidBlock MyCustomFluidBlock.class. As far as I understand you do not want to extend to FlowableFluidBlock, but to FlowableFluid. I've yet to understand why, because in the past a fluid block, was still a block. It seems like it is now an "in between" thingy, or no longer a block at all. I hope someone of the wizards can spread some wisdom on that? And if it's just to ease the tinkering...👍 Edit: If someone wants more learning material, I'd recommend the TechReborn FlowableFluid.class, and their actual Fluid.class(Fabric only, so lots of adaptions needed, but good for getting an idea of structure), or PneumaticCraft(Forge). Notice they seem to be on 1.16.5 or even 1.17.1, but the code is compiling fine and dandy with minor adaptions(for 1.17.1 only?). You'd quickly find traces on how to "adapt" by highlighting methods/fields/etc., and open the declaration. Trouble starts really if references aren't public, because then you have to @Override in a custom.class. Which is something I've yet to learn as well. In the past, for 1.7(yes, that's 2013), it looked something like that: -
By RVOtakuMike · Posted
I figured out what was causing it... Advanced Rocketry's Datapacks...
-
-
Topics
-
-
Who's Online (See full list)
