Registry for custom behaviour with external storage for specific blocks

[lucasser]

Implements #976

[Nodrance]

based

[lucasser]

Will let us integrate with QIO and AE2 very easily.

[Nodrance]

"is rs2 or ae2 better" we're doing both now keep up

[raoulvdberge]

I'm not sure that this will work properly. The external storage API is designed to just be active for all providers all the time, regardless of block type. We can't be block type dependant. The reason for this is: if we are block type dependant, that means you need to reload the storage if the connected block changes (this currently doesn't happen, by design). If you reload when the connected block changes, this causes 2 problems:

• Items are flickering in the Grid
• Server strain

Listening to connected block changes isn't bad per se, but some blocks constantly send block updates. See #886
And yes, indeed, interfaces get an exception for the neighbor changed event and do cause a reload.

Regarding possible AE integration:

Refined Storage shouldn't have integration with Applied Energistics, there is no use case for it and encourages people to create weird setups for no reason that create problems.

[raoulvdberge]

If we were to merge this, only for QIO integration, ExternalStorageBlock#neighborChanged needs to be updated as well for block change detection.

[lucasser]

I have two solutions. I changed the neighbourChanged method to re initialize if the changed block is in the registry. This might cause problems if the special block always sends updates. The other option is we store the block the storage is currently sitting on, and if it changes:

if (savedBlock.getLootTable().registry() != newBlock.getLootTable().registry()) {
    blockEntity.loadStorage(serverLevel);
} else...

then we change the provider.

[lucasser]

I am trying to prevent hardcoded blocks/values so that if there is something else that need a custom provider, it'll be easy to integrate (for example create storage system)

[raoulvdberge]

I have two solutions. I changed the neighbourChanged method to re initialize if the changed block is in the registry. This might cause problems if the special block always sends updates.

Yes, but that is less of a problem since we explicitly whitelist these blocks and can check them.

The other option is we store the block the storage is currently sitting on, and if it changes:

That is bound to cause issues: you have to deal with syncing world state & cache invalidation.

[raoulvdberge]

brokeSpecialBlock should probably check isPresent instead? Please thoroughly test these changes!

I do not want to create more instability in a phase of development where we already have so many bugs.

[lucasser]

Also, this doesn't have to be an urgent thing, I'm just submitting PRs as I finish working on them for you to review whenever you can.

[lucasser]

Is there a reason for updating external storage provider when an interface/special block is broken as opposed to just update when something is placed