Leaderboard

I'd take a look at EntityRenderer#renderName.

About Suppliers: https://thejavacult.com/supplier-interface-java-util-function/

The colors are.. odd.. they need to be updated to look better on the Mojang background. However, Honestly I think that someone should come along and make a function to render strings with an outline. Because white text, with black outline looks great on all colors. But ya, as Dies said, as it sits the new early loading screen is a complete re-write, so it doesn't have the splash.properties that used to exist. Feel free to work on making it better.

Actually, if you really need to send entire capability with network package, you may write your capability into CompoundNBT tag and then write this tag into PacketBuffer. But as poopoodice said, avoid excess synchronization.

I have resolved. I just had to insert the following code in my block. @Override public boolean allowsMovement(BlockState state, IBlockReader worldIn, BlockPos pos, PathType type) { return false; }

As I said, this has NOTHING to do with Forge's code or how we build the classpath. We could technically put the jar whever the hell we want. This is wholy issues with SERVER HOSTS and other users. And the drama/bitching that will come from it. This is just a case of... don't be dumb and run the vanilla server... Unfortunately there isn't anything we can do to mark the world as not loadable by the vanilla jar. As it's not code we control so there isn't any way to add protections into it. Many Many external things can corrupt your world.

As the title says, 1.16 introduces a new data generator that creates block/item models for the game. I am wondering if forge is going to continue developing the system they already have or adopt and merge with the new generator implemented.

The 1.16 mappings are being made manually, hence the old date. Once MMMS lands, we'll be in a much better position. For the mean time, Kashike is working on updating as many of the common mappings as possible.

Capabilities are a better way of achieving the same thing as Interfaces. Interface way: if (tileEntity instanceof IThing) Capability way if (tileEntity.hasCapability(ThingCapability)) Interface way: ((IThing)tileEntity).doThing(); Capability way tileEntity.getCapability(ThingCapability).doThing(); Interfaces make your tile be something while Capabilities let your tile provide something. Capabilities follow the OOP concept of "Composition over Inheritance".