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

Let's Plays and other Videos!


313 topics in this forum

    • 0 replies
    • 57 views
    • 0 replies
    • 149 views
    • 0 replies
    • 169 views
    • 0 replies
    • 280 views
    • 0 replies
    • 774 views
    • 0 replies
    • 495 views
    • 0 replies
    • 256 views
    • 0 replies
    • 581 views
    • 0 replies
    • 350 views
    • 0 replies
    • 250 views
    • 0 replies
    • 509 views
    • 0 replies
    • 386 views
    • 0 replies
    • 481 views
    • 0 replies
    • 406 views
    • 0 replies
    • 1.3k views
    • 0 replies
    • 303 views
    • 0 replies
    • 381 views
    • 0 replies
    • 375 views
    • 0 replies
    • 337 views
    • 0 replies
    • 326 views
    • 0 replies
    • 346 views
    • 0 replies
    • 299 views
    • 0 replies
    • 397 views
    • 0 replies
    • 270 views
    • 0 replies
    • 246 views


  • Posts

    • show the code of your Structure, if possible via a git repo¬†
    • 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.
    • 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:
  • Topics

  • Who's Online (See full list)

×
×
  • Create New...

Important Information

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