Mekanism QIO Storage Change?

[rumblefrog]

Tried to use Mekanism QIO input adapter, but backplane.collection.metrics contained only drive status and none of the items as individual metric.

Looked a bit, and it's possible that Mekanism has changed its qioItemMap structure? Haven't dug too deep, but here's what the new NBT looks like

Drive 0 stores 64 iron ingots and 64 redstone.

{
    data: [],
    palette: [],
    mekData: {
        qioItemMap: [L; 2979942897336207294L, -5177127105384248702L, 64L, -5250843741295851232L, -4635356434065122024L, 64L],
        qioMetaCount: 128L,
        qioMetaTypes: 2
    }
}

Maybe relevant commit: mekanism/Mekanism@778a4f7#diff-dbfa4c71a8cdbad86b4666f7288c23828b76cd66c45d390e4c0e11c5ac3d5e27

Looking for more knowledgeable folks to chime in

[cyberbit]

Oh wow, that layout is drastically different than I remember. What are your mod/game versions?

Edit: Release of commit mentioned - https://github.com/mekanism/Mekanism/releases/tag/v1.20.4-10.5.0.22, but this would be for the wrong MC version (1.20.4, issue is on 1.20.1)

[rumblefrog]

I'm playing Valhesia 6 modpack: https://www.curseforge.com/minecraft/modpacks/valhelsia-6 which is on Minecraft 1.20.1, which I believe should be 1.20.1's Mekanism mod.

[cyberbit]

Hmm, this change may be a lot older than it seemed originally. The adapter was based on the 1.18 version of the mod (10.2.5), I'm not sure I tested QIO on 1.19/1.20 (10.3 - 10.4).

I will have to take a deeper look. Hopefully it can still be supported. Apologies!

[cyberbit]

After some testing, it seems that the first-party QIO peripheral the adapter depends on no longer works past 1.18. However, I did find a workaround that may help you.

If you have Applied Energistics, Applied Mekanistics, and Advanced Peripherals, and you are on 1.18+, you can use an ME Storage Bus attached to the back of a configured QIO Dashboard to read the items in its selected frequency as part of an ME network (see AppliedEnergistics/Applied-Mekanistics#1).

(edit: screenshot from Applied Mekanistics mod page)

Adding an ME Bridge to the ME network would let you gather the storage metrics from an ME Bridge adapter, while still gathering drive stats from the QIO adapter.

If you go this route, and you already have an existing ME network(s), I would recommend an isolated ME network just for this purpose, as the ME Bridge aggregates across all sources.

I will use this issue to track changes to Telem documentation describing the problem and its workaround.

Thank you for the report! I just wish I had better news for you. :/

[rumblefrog]

Hm, perhaps I'm doing this wrong, but I'm getting a Fluent error

:addInput('mineral_array', telem.input.advancedPeripherals.meBridge('right', '*'))

[cyberbit]

Seems like an error getting repeated from one of the mods. Would you be able to share the versions of Mekanism, Applied Energistics, Applied Mekanistics, and Advanced Peripherals you are running? You can find these in the mod list in game or in your launcher.

[cyberbit]

Your setup appears to be working for me with these versions:

• Minecraft 1.20.1
• Forge 47.3.33
• Advanced Peripherals 0.7.41r
• Applied Energistics 2 15.3.4
• Applied Mekanistics 1.4.2
• Mekanism 10.4.15

[rumblefrog]

Seems like an error getting repeated from one of the mods. Would you be able to share the versions of Mekanism, Applied Energistics, Applied Mekanistics, and Advanced Peripherals you are running? You can find these in the mod list in game or in your launcher.

• Minecraft 1.20.1
• Forge 47.3.5
• Advanced Peripherals 0.7.40r
• Applied Energistics 15.2.9
• Applied Mekanistics 1.4.2
• Mekanism 10.4.8

[cyberbit]

After further testing with your versions, and some discussion with the developer, the error is coming from Advanced Peripherals 0.7.40r. The next release, 0.7.41r, works as intended.

Is this a certain modpack you are playing?

[rumblefrog]

Indeed, it's Valhelsia 6. Unfortunately it's a shared server, so I'll see if 0.7.41r is compatible without forcing others to upgrade.

[cyberbit]

I was able to identify the exact metric causing the problem with the ME Bridge. Disabling cell_count allows the adapter to work as intended on the AP version you have.

I just released 0.9.1 that includes this fix. This means you will lose out on cell_count but all the storage metrics appear to be working for me.

Let me know if the new release works for you!

[rumblefrog]

Thanks! New release works as a workaround!