Data-Oriented Conduits, Network-Wide Context and Energy Conduit Tiers

[Rover656]

Description

This is a substantial addition to the conduit API. Here's a general rundown.

This entire rundown is now out of date due to the datapack-related changes. I will write formal documentation on our website once this PR nears completion.

~~Instead of defining a ConduitType which dictates the behaviour of a conduit, a ConduitType now declares it's Network Type and it's Options.

Options are like the previous TieredConduit implementation but a bit more comprehensive - options allow you to influence the behaviours of the ticker and the network based on any arbitrary data you want to have for each instance of your conduit types.

The ConduitNetworkType is the new ConduitType (confusing, right?). This determines how ConduitNetworkContext and ConduitData is created, as well as: filter + upgrade compatibility, conduit events, ticker that will be used, menu data and capability proxies. This has been done to group all of this logic together as it's all fairly locked-in. In order for your conduit network to support a certain upgrade, the ticker must be able to handle it and so on. These may change location again, but I'm happy with them at the minute.

ConduitNetworkContext is the new kid on the block - this allows a network to have arbitrary data stored with the entire network instead of within each node. This has been used to create a network-wide energy buffer and round robin information for the energy network. This could find other utilities in future.

Using all of these new features, Energy conduits have now been reworked to support tiers and only allow energy to be pushed into them (no more extracting from blocks). This has resulted in the creation of a buffer on the conduit network to be able to hold the energy being moved through the network.~~

These changes will NOT be backported to 1.20.1

TODO

• [x] Add serialization for graph contexts
• [x] Actually add the energy conduit tiers, currently we only have support for it.
• [x] Look into the place/break sync bug?
• [x] Fix right click not opening the correct connection. Appears to be resolved but imo right clicking the center shouldn't magically pick one connection over another. Maybe worth creating an issue.
• [x] Port AE2 and Mekanism conduits
• [x] Agree the buffer size logic for energy conduits
• [x] Investigate flattening the conduit items into a single item using data components
• [x] Submit GraphLib pull request with the improved information used for splitting graph contexts Reverted version and have accounted for the differences.
• [x] Swap from custom texture manager to using a convention of textures/gui/sprites/conduit_type/<name> namespaced to the type's namespace.
• [x] Conduits JEI plugin to separate conduit item variants.
• [x] Check on weirdness with block updates when placing next to Mekanism pipe.
• [x] Proper lang keys for the conduit item.
• [x] Make conduits into a datapack registry to allow modpack makers to create custom tiers.
• [x] Find a way to ensure safety if a datapack conduit changes type and is used to load an existing save.
• [x] Clean up after all of these changes
• [x] Move canConnectTo and hasConnectionDelay out of ConduitTicker to Conduit.
• [ ] Change from strongly typed contexts and conduit data to a data component map to reduce typing issues?

Breaking Changes

All conduit API has been broken, and due to the change to energy conduits, old 1.21 worlds will not load after this PR.

Checklist

• [x] My code follows the style guidelines of this project (.editorconfig, most IDEs will use this for you).
• [x] I have made corresponding changes to the documentation.
• [x] My changes are ready for review from a contributor.

[Rover656]

I am going to defer the changes to how conduit data and context are stored until a future PR - these must be completed before releasing a 1.21 build as they will cause breaking changes.

I'll finish setup of the energy conduit tiers and energy scaling and then merge this PR - creating issues for any outstanding items as I do.

[Rover656]

Oh - and one of those issues will be recipe datagen for AE2 and Mekanism, as that is pending a PR to NeoForge.

[Rover656]

AE2 and Mekanism conduits will return after project restructure