eff26386be
# Breaking changes - `VillagerPlantableRegistry` replaced with `ItemTags.VILLAGER_PLANTABLE_SEEDS` - `FabricItemGroup.builder()` no longer takes an `Identifier` - `FabricItemGroup.build()` no longer registers the ItemGroup, this now needs to go in the vanilla registry. - `ItemGroupEvents.modifyEntriesEvent` now takes a `RegistryKey<ItemGroup>` in place of an `Identifier` - `FabricLanguageProvider` now takes a `RegistryKey<ItemGroup>` in place of an `ItemGroup` - `IdentifiableItemGroup` removed, replaced with vanilla registries. - `FabricMaterialBuilder` removed, no replacement. - `HudRenderCallback.onHudRender` now passed a `DrawableHelper` in place of `MatrixStack` - `ScreenEvents.beforeRender` now passed a `DrawableHelper` in place of `MatrixStack` - `ScreenEvents.afterRender` now passed a `DrawableHelper` in place of `MatrixStack` - `Screens.getItemRenderer()` removed. Replace with `MinecraftClient.getItemRenderer()` `DrawableHelper` is likely to be renamed soon, see: https://github.com/FabricMC/yarn/pull/3548/ |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle | ||
| README.md | ||
Fabric Transfer API (v1)
This module provides common facilities for the transfer of fluids and other game resources.
Transactions
The Transaction system provides a
scope that can be used to simulate any number of transfer operations, and then cancel or validate all of them at once.
One can think of transactions as video game checkpoints. A more detailed explanation can be found in the class javadoc of Transaction.
Every transfer operation requires a Transaction parameter.
SnapshotParticipant
is the reference implementation of a "participant", that is an object participating in a transaction.
Storages
A Storage<T> is any object that can store resources of type T.
Its contents can be read, and resources can be inserted into it or extracted from it.
StorageUtil provides a few helpful functions to work with Storages,
for example to move resources between two Storages.
The storage/base package provides a few helpers to accelerate
implementation of Storage<T>.
Implementors of inventories with a fixed number of "slots" or "tanks" can use
SingleVariantStorage,
and combine them with CombinedStorage.
Fluid transfer
A Storage<FluidVariant> is any object that can store fluids. It is just a Storage<T>, where T is
FluidVariant, the immutable combination of a Fluid and additional NBT data.
Instances can be accessed through the API lookups defined in FluidStorage.
The unit for fluid transfer is 1/81000ths of a bucket, also known as droplets.
FluidConstants contains a few helpful constants
to work with droplets.
Client-side Fluid variant rendering will use regular fluid rendering by default,
ignoring the additional NBT data.
Fluids that wish to render differently depending on the stored NBT data can register a
FluidVariantRenderHandler.
Item transfer
A Storage<ItemVariant> is any object that can store items.
Instances can be accessed through the API lookup defined in ItemStorage.
The lookup already provides compatibility with vanilla inventories, however it may sometimes be interesting to use
InventoryStorage or
PlayerInventoryStorage when interaction with
Inventory-based APIs is required.
ContainerItemContext
ContainerItemContext is a context designed for ItemApiLookup queries
that allows the returned APIs to interact with the containing inventory.
Notably, it is used by the FluidStorage.ITEM lookup for fluid-containing items.