All Classes and Interfaces
Class
Description
AbstractBlockStateSmith<T extends net.minecraft.world.level.block.Block>
AbstractBlockStateSmith.StateFunction<T extends net.minecraft.world.level.block.Block>
AbstractWorldParticleBuilder<T extends AbstractWorldParticleBuilder<T,Y>,Y extends AbstractWorldParticleOptions>
A collection of various helper methods related to all your blocky needs.
BlockStateSmith<T extends net.minecraft.world.level.block.Block>
BlockStateSmith.SmithStateSupplier<T extends net.minecraft.world.level.block.Block>
A collection of helper methods for data manipulation
The Easing class holds a set of general-purpose motion
tweening functions by Robert Penner.
A base class for Back easings.
Back easing in - backtracking slightly, then reversing direction and moving to target.
Back easing in/out - backtracking slightly, then reversing direction and moving to target,
then overshooting target, reversing, and finally coming back to target.
Back easing out - moving towards target, overshooting it slightly, then reversing and coming back to target.
A base class for elastic easings.
An Elastic easing used for ElasticIn functions.
An Elastic easing used for ElasticInOut functions.
An Elastic easing used for ElasticOut functions.
An ExtendedSoundType is a simple extension of ForgeSoundType, also providing hooks for when each individual sound is played.
A FireEffectInstance is a custom instance of a fire effect, functioning pretty much exactly as a normal fire effect would do
You must register a type and can manage a players fire effect through the
FireEffectHandlerAn interface containing various methods which are triggered on various forge events.
Blocks that implement this interface will automatically be valid targets for the
LodestoneBlockEntityRegistry.MULTIBLOCK_COMPONENT block entity.The core of a multiblock structure, tracks the positions of all the components in the structure.
A placement assistant is a helpful client-sided system which allows you to do custom things when a player places something.
A handler for firing
IEventResponderItem eventsA simple block entity which holds a single ItemStack
An ItemStack tied inventory
A handler for common attributes I use in my mods.
The attribute registry,
LodestoneAttributeRegistry.UUIDS contains randomly generated uuids for each attribute registered, allowing you to have a constant uuid you may apply to attribute values.A simple block entity with various frequently used methods called from
LodestoneEntityBlockA powerful ItemStackHandler designed to work with block entities
It's the exact same thing as BlockModelProvider, except with a different factory and by extension, a different model builder.
An extension of Block Properties, allowing you to add
LodestoneThrowawayBlockData
Some of these values are optional; they only get added during datagen.A simple capability, that's it.
LodestoneCapabilityProvider<C extends net.minecraftforge.common.util.INBTSerializable<net.minecraft.nbt.CompoundTag>>
A basic provider for your lodestone capability
A config system allowing for static initialization of config values.
Various throwaway data stored in
ThrowawayBlockDataHandler.THROWAWAY_DATA_CACHE, which is only ever instantiated during the data-generation process.A SimpleBlock is an implementation of EntityBlock that allows most frequently used logic to be handled in a SimpleBlockEntity
It's important to still utilize generic, T extends YourBlockEntity, in order to allow for other mods to extend your block and use a different block entity
Register renderers in FMLClientSetupEvent.
Various throwaway data stored in
ThrowawayBlockDataHandler.THROWAWAY_DATA_CACHE, which is cleared after the game is finished loading.Register renderers in FMLClientSetupEvent.
A simple copy of a sword, without actually being a sword.
ModularBlockStateSmith<T extends net.minecraft.world.level.block.Block>
ModularBlockStateSmith.ModularSmithStateSupplier<T extends net.minecraft.world.level.block.Block>
A basic Multiblock component block.
A basic Multiblock component block entity.
Handles world-space post-processing.
Abstract world space post-process pass.
A handler responsible for all the backend rendering processes.
Stores all relevant data from a RenderType.
Runs on the server when a player initially right-clicks an empty space.
A handler for screen particles.
A collection of methods designed to simplify and unify the use of vectors
World events are tickable instanced objects which are saved in a level capability, which means they are unique per dimension.