Mekanism Ores and Others Cannot be Ore Excavated

[rybplayer]

Certain Mekanism Ores as well as other blocks appear to be immune to ore excavation, regardless of the tool used. Examples include copper and tin ore.

[wideblaze]

I've attempted to fix this a couple of times -- so if anyone has a fix please let me know.

Other than allowing everything to be excavated (which I do not want to enable)

ore excavation has a whitelist functionality but I can't seem to get it to work. I believe if I'm able to get that to work I have to add every block I want to allow -- seems like an error-prone chore.

I'll try again -- and open an issue with the mod if still unable to get working

[rybplayer]

The only fast (and dirty) solution I can see is to replace the mod with similar alternatives, such as VeinMiner, but even that does not guarantee a sucess...

[wideblaze]

worked on this a little today -- seems related to tool requirement -- need to do more testing to confirm

[wideblaze]

https://github.com/Funwayguy/OreExcavation/issues/102

[Xaymar]

I managed to get Ore Excavation to work with the following two config files: oreexcavation_groups.txt oreexcavation_overrides.txt. The "Groups" file defines what types of blocks are the same (and thus excavated together), while the overrides file allows to specify tool overrides - the latter is necessary as some tools do not register as a pickaxe, axe or similar, but there's no way to give them default values.

[wideblaze]

I will test this out today! Kudos in advance if it works.

[wideblaze]

@Xaymar

Testing failed. :(

Not sure if your fix was for my problem: When B:"Ignore Tool"=false Ores excavate correctly except mekanism ores, they do not excavate Mekanism ores excavate correctly when B:"Ignore Tool"=true

[Xaymar]

I have B:"Ignore Tool" also set to false. What does your oreexacation_groups.txt in /config/ look like? At minimum the blockGroups array should contain this for Mekanism:

{
    "blockGroups": [
        [
            "mekanism:oreblock"
        ]
    ],
    "strictSubtypes": [
        "cropWheat",
        "cropPotato",
        "cropCarrot",
        "cropNetherWart"
    ],
    "gamestages": {
        "examplemod:example_block1": "example_stage1",
        "examplemod:example_block2": "example_stage2"
    }
}

Note the placement of commas. The JSON parser refuses to load the JSON file if there is an extra , at the end of a list. Edit: Oh and I'm not sure, but the parser might also require all listed blockGroups to be a valid list of blocks.

[wideblaze]

ok great, wanted to make sure we were working on the same issue ;). I'll redo the config and test again, I had edited your original files to remove items from mods not included in the pack. It's possible a forked the syntax when I did.

[wideblaze]

no joy

There was an issue with one of the files. I left out a close bracket. Fixed it but it didn't work. So I simply replaced both files ith your contents above without modification and it still didn't work. I even just use the trimmed down version in your latest post.

Not seeing any errors in logs so a little stumped. It is likely something on my end and I will have to look closer tomorrow.