Deprecated API
Contents
-
ClassDescription
-
FieldDescription
-
MethodDescriptionConsider calling
AbstractBlock.AbstractBlockState.canBucketPlace(net.minecraft.fluid.Fluid)
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.canReplace(net.minecraft.item.ItemPlacementContext)
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.emitsRedstonePower()
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.getCollisionShape(BlockView, BlockPos, ShapeContext)
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.getFluidState()
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.getOutlineShape(BlockView, BlockPos, ShapeContext)
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.getPistonBehavior()
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.getRenderingSeed(net.minecraft.util.math.BlockPos)
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.getRenderType()
instead. See why these methods are deprecated.net.minecraft.block.AbstractBlock.getStrongRedstonePower(BlockState, BlockView, BlockPos, Direction) Consider callingAbstractBlock.AbstractBlockState.hasComparatorOutput()
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.hasSidedTransparency
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.mirror(net.minecraft.util.BlockMirror)
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.prepare(WorldAccess, BlockPos, int, int)
instead. See why these methods are deprecated.Consider callingAbstractBlock.AbstractBlockState.rotate(net.minecraft.util.BlockRotation)
instead. See why these methods are deprecated.Please useBlock.asItem()
Intrusive holders exist for legacy reasons only.This one is hard to ensure deterministic behavior compared to the non-thread-safe one.
Suppliers.memoize(com.google.common.base.Supplier<T>)
instead.