Differences

This shows you the differences between two versions of the page.

--- tutorial:transfer-api [2022/10/07 16:57] – nexus-dino
+++ tutorial:transfer-api [2025/03/30 22:05] (current) – [Fluid, Item and Energy Transfer] technici4n
@@ Line 1: / Line 1: @@
 ====== Fluid, Item and Energy Transfer ======
-This series of tutorials is meant to explain how the Fabric Transfer API works, and how you can use it for your own mods.
-**Please make sure that you read all of these tutorials in order, even if you are only interested by item or energy transfer.**
-For any question, please go to the ''#transfer-api-debating'' channel on the official Fabric Discord server.
-All Transfer API classes are marked as ''@ApiStatus.Experimental''. This is temporary, and it means that there may be occasional breaking changes if a design flaw is encountered in the API, but we will try not to break the API to avoid disrupting the large amount of mods that are using it already. In practice, this means that you can mostly ignore this warning, and disable it in your IDE if it's too annoying.
+==== Transactions ====
+The Fabric Transfer API relies heavily on the concept of transactions.
+  - [[tutorial:transfer-api/transactions|The Transaction system]]. Before looking at the details of how transfer works, we take a detour to discuss transactions.
 ==== The Fluid Transfer API ====
 The Fabric Fluid Transfer API is how fluid-containing blocks such as machines, pipes, and tanks communicate with each other. It's what allows all mods to be compatible with each other as far as fluid transfer is concerned. (If you are coming from Forge, it serves a purpose similar to ''IFluidHandler'').