fabric/fabric-transfer-api-v1
modmuss d48ec150ba
Some checks failed
Build / build (21-ubuntu) (push) Has been cancelled
Build / client_test (push) Has been cancelled
Build / server_test (push) Has been cancelled
Build / check_resources (push) Has been cancelled
24w36a (#4068)
* 24w36a

* Some fixes

* More work

* Fixes

* Update yarn

* Update fabric loader

* Bump versions
2024-09-05 11:42:30 +01:00
..
src 24w36a (#4068) 2024-09-05 11:42:30 +01:00
build.gradle Update to loom 1.3 and use Mod Publish Plugin (#3158) 2023-08-02 18:51:21 +01:00
README.md Fix links in transfer-api README.md (#3694) 2024-04-10 22:17:45 +01:00

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 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. Fluids that wish to render differently depending on the stored components 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.