Open [2.5.5] OreExcavator does not recognize similar log blocks as same

  • This section is closed. Please do bug reports over at the FTB GitHub repos.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Uberfuzzy

New Member
Jul 29, 2019
8
0
0
Summary of the problem [2.5.5] OreExcavator does not recognize similar log blocks as same

Pack Version 2.5.4

What is the bug? Some trees have similar (by metadata) log blocks in the world to form trees (sideways, or different edges), and OE does not see those as connected when chain harvesting.

Veinminer did this correctly, but I think the VM configs had a few lines to tell that certain similar blocks were "the same". Not sure if OE has a similar connection override method.


The main one I found this with was on Natura's bloodwood (red upside down trees, natura:bloodwood), as each of the edges is a different block with meta data 0-3.

This means the 2x2 trunk is requires 4 separate connected harvests. Plus another for the "root" blocks (which are meta 15), but those were always a different vein anyways.

This will likely also cause items with different "states" such as redstone ore to also fail being connected mined.

Mod & Version OreExcavation 1.1.23

Link to log file

Is it repeatable? Yes

Known Fix If OE supports some sort of override of which blocks are "the same", some items need to be exacted from the old 2.5.4 veinminer config, and added to the OE config.
 
S

Sorbe

Guest
Confirmed, I was just mining some 2x2 Bloodwood trees myself recently and had to hit them 4 times (4 slices).
 

Funwayguy

New Member
Jul 29, 2019
9
0
0
Considering this doesn't happen on vanilla logs I'm going to assume those trees have specific item representations for those orientations/variants which is why Ore Excavation is detecting them as different blocks. I will see about adding in a block grouping override for this in future.