This module provides common facilities for the transfer of fluids and other game resources.
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.
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 Storage
s,
for example to move resources between two Storage
s.
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
.
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 components.
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 components.
Fluid
s that wish to render differently depending on the stored components can register a
FluidVariantRenderHandler
.
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
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.