Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I tried several different mods that pull out of the Dim Chest which is set to a player on channel 1 and sometimes for no reason the dim chest wont let other mods interact with the chest -> need to mine and and re-place the chest and it works again

How can I reproduce this bug or crash?

1. No Idea what causes it and when this happens but I tried with AE2, Mekanism, Pipez, Vanilla Hoppers

Configuration

- Mod version: 1.21-9.0.2
- Forge version: Neoforge 21.1.73
- Minecraft version: 1.21.1

Relevant log output

No response

Anything else?

No response

Currently playing through ATM10 and can confirm this is an issue. Doesn't just happen on Channel 1. Tanks/Chests will randomly stop working and breaking either the pipe trying to interact with the chest/tank or the chest/tank itself is the only way to fix it

I need more information. I currently play a pack and have never had any experience with this bug

I need more information. I currently play a pack and have never had any experience with this bug

Hello,

I encountered the same issue on several servers I played on, and the common factor seems to be the presence of the Hyperbox mod. Specifically:

• Every time a Hyperbox is placed and entered for the first time, all Dim Storage units stop being accessible for extraction.
• To resolve this, you need to either redo the pipes or break and replace the Dim Storage, which restores extraction functionality.
• Once the issue is fixed, it becomes possible to enter and exit the Hyperbox without any problems. However, the issue reappears with every newly created Hyperbox.

I hope this helps identify the source of the problem.

I just had my chest disconnect from my AE2 import bus. Removed the bus and replaced and it worked as normal.
I doubt that this is AE2 misbehaving as I have been having other issues with this mod also. When changing the channel of a storage, it somehow keeps sending items to that dim on my AE2 storage. Breaking and re-placing the storage corrects the issue.

This is all on ATM10 - V2.34