cyberbit / cyberbit/telem-modules
Mekanism QIO Storage Change?
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
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: https://github.com/mekanism/Mekanism/commit/778a4f7e749951c9228877dc936126516c1f47e1#diff-dbfa4c71a8cdbad86b4666f7288c23828b76cd66c45d390e4c0e11c5ac3d5e27
Looking for more knowledgeable folks to chime in
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Mekanism QIO input adapter and inspect how backplane.collection.metrics is built from qioItemMap. Compare the shown NBT structure with the linked Mekanism commit and determine whether item entries can still be extracted. Done means QIO metrics expose individual stored items as well as drive status, with a test or reproduction confirming the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100