QIO + Storage Bus Integration Not Working with Optifine/Sodium
RulsOfficial opened this issue · 5 comments
Description
When using QIO with a Storage Bus, the integration does not function correctly if Optifine or Sodium are present on the client. Without these performance mods, the integration works as expected.
Environment
- Minecraft: 1.21.1
- Loader: NeoForge
- Mods involved: QIO, Storage Bus, Optifine/Sodium
Steps to Reproduce
- Open a new world with only Applied Mekanistics installed.
- Connect a QIO Dashboard with a Storage Bus.
- Verify that you can access the QIO system through an ME Terminal.
- Close the game.
- Add Optifine or Sodium to the client.
- Attempt to access QIO through the Storage Bus.
- Observe that the integration no longer works.
Expected Behavior
QIO + Storage Bus integration should work regardless of whether Optifine or Sodium are installed on the client.
Actual Behavior
Integration breaks when Optifine or Sodium are present on the client.
Additional Notes
- Tested with both Optifine and Sodium separately; both cause the same issue.
- No crashes reported, just non-functional integration.
- Logs show no obvious errors related to QIO or Storage Bus during reproduction.
- Interestingly, after repeatedly loading and unloading the same world with and without Optifine/Sodium, the problem sometimes disappears “as if by magic,” making it difficult to reproduce consistently.
Optifine and sodium are two very different mods.
Optifine is known to break things on the integrated server like that, and is therefore not supported.
Also, there is no Optifine for neoforge, so I am not sure how you are even running this in the first place.
I can't reproduce it with sodium, it works on my machine.
Hi Mari, thanks for the fast response.
Just to clarify my original report:
-
I don’t usually play with Optifine — I only tested it (via an unofficial NeoForge port) to check if it caused similar issues.
-
When I mentioned “server,” I also meant single-player integrated server (i.e., creating a new world locally). The issue happens even in a clean environment with only Applied Mekanistics + Sodium.
-
After reproducing the bug once, if I load the same world without Sodium and then later re-enable Sodium, the problem seems to “fix itself” and does not break again — which makes the behavior a bit inconsistent and harder to pin down.
Do you have a world and mod-list which consistently breaks? Otherwise there is nothing I can do