ChampionAsh5357

Provide your source of what you have already done and how far in the process you got. Saying you don't understand doesn't provide any context.

Take a look at the Forge FluidStack and its capability implementation.

Nothing has changed between those two versions. However, you should update to the latest minor. It's a snapshot mapping, not stable. Nor is it the latest. That can be found by dming forge-bot '!mcpv' which is present on the Forge discord.

Don't necro an old thread. Create your own topic with your own question and source so that users may help.

Yes, the method should be static though. You won't see any issues in a standalone, but with other mods it will bottleneck other features from generating due to how codecs are handled with unregistered objects.

You need to register the dispenser behavior using DispenserBlock::registerDispenseBehavior.

You still need to register it but yes, that's exactly how you would do it. Take a look at the Features class for the registry method to copy and use. Since it returns the object itself, you can just modify as needed.

No, that will create the ConfiguredFeature every single time the event is called, which is too many times. This is not to mention you are no longer registering the ConfiguredFeature. Create a global field and initialize it within the common setup.

This is more or less a guess, but try checking the output of ProjectileItemEntity#getItem and where the entity is initially placed. It's either due to the fact that the position of the entity spawn is too low so it dies immediately or the item is not synchronized to the client for rendering.

Initialize the variable within the method event.

That would happen if you do not register the item using your extended item class.

Pixelmon has been taken down per request as of 2017, and any remake or addon for it is of questionable intention corresponding with the copyright held by the Pokemon Company. Also, 1.12.2 is not supported on this form, please see the above banner for the currently supported versions.

Yes, I would still like to verify that you deferred initialization and registry of the ConfiguredFeature to the common setup event.

Code Style 6. OnlyIn is used as a stripper to create the forge universal and server jars from one repository. Using it is more or less declaring that you didn't make sure your logic was only available to a certain physical side. In this case, it is completely unnecessary.

No, that's not what I said. I said the feature registry is irrelevant, you're not using it. The ConfiguredFeature should be initialized and registered during common setup.