mekanism / Mekanism

A mod for Minecraft
MIT License
1.36k stars 522 forks source link

Induction Matrix doesnt form when internal components are below the input and output ports #8163

Open v-tron opened 1 month ago

v-tron commented 1 month ago

Issue description

When building the induction matrix, the wiki says that internal components can be placed anywhere in the matrix, along with air blocks. However, if components are placed below the port level, the matrix doesnt form for some reason. I have not tested this extensively, however, if any internal components were placed below the ports (i had air blocks in between the components, i.e. induction providers on bottom layer and induction cells on top or vice versa) the matrix wouldn't form.

Steps to reproduce

  1. Build Induction Matrix shell
  2. Put ports somewhere higher than the lowest level
  3. Put internal components below ports and air above
  4. Matrix doesn't form

Minecraft version

1.20.x or earlier (No longer being developed)

NeoForge version

Forge 47.2.20

Mekanism version

Older

Other relevant versions

Mekanism 10.4.8.43

If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)

No response

v-tron commented 1 month ago

I have now tried testing this a little further and the behaviour is pretty much random it feels like. The matrix sometimes forms and sometimes doesn't. Debug logs say nothing. I will see if I can somehow make sense of this behaviour but I guess the issue can be closed for now.

thiakil commented 1 month ago

sounds like you have another mod placing not-actually-air blocks. Try right clicking an edge using a configurator in configure mode. It should show where an invalid block is, provided the frame is complete

UnknownSerhan commented 1 month ago

Does it fix itself when you break any block and place it back? Because that's a know bug in the mod.

v-tron commented 1 month ago

Yes it does, it seems to form as soon as I break a block and replace it

UnknownSerhan commented 1 month ago

Okay then this has to be the same issue as https://github.com/mekanism/Mekanism/issues/7621