Mekanism 1.12.2 Community Edition

Mekanism 1.12.2 Community Edition

1.9k Downloads

[BUG]: Atomic Disassembler breaks thermal dynamic ducts incorrectly

Magesticles opened this issue · 4 comments

commented

Describe the bug

Original report:
xJon/The-1.12.2-Pack#858 (comment)
Basically the Atomic disassembler breaks more and gives less of thermal dynamic ducts.

To Reproduce

  1. Have atomic disassembler from Mekanism
  2. Set it to "extended vein mining"
  3. Break any row of Thermal dynamic fluid, flux, item duct, and it will only give you a single one duct despite breaking more.

Expected behavior

You should get every duct broken back, not just the one.

Mekanism Version

Mekanism-1.12.2-9.8.3.390

Minecraft Version is this regarding?

1.12.2

What OS are you seeing the problem on?

Windows

Name of modpack if applicable

1.12.2 pack

Version of said modpack if applicable

1.5.2

Screenshots

No response

The crash report in folder ./crash-reports (both server and client logs)

no crash

Please provide the following other files

https://mclo.gs/JwYWtee

commented

i'm quite busy so i'll just gonna disable vein on thermal dynamic ducts.

commented

Thats unfortunate, its nice to destroy a snaking system of power ducts when replacing a power system, or modifying.
I understand though.

commented

it depends, i can understand why you want it to do that, but i believe that would involve a rewrite of some code. im quite busy so i dont have time to fix everything. but it will marked as temp fix so others can fix it properly if they want to. we do accept pr's

commented

Hello @maggi373 thank you for maintaining Mekanism 1.7.10/1.12.2 at all. I found this project through sorting popular forks of the Mekanism repo.

On this issue though, the atomic disassembler has a tough time with some multiblock structures other than this. Breaking a digital miner with the disassembler deletes the item entirely.

Mekanism maintainers have vehemently maintained that they will never fix bugs in old versions. It would be great if this was also fixed.