The Paxel does not mine TC gravel ores, which require a shovel
iLLHunter opened this issue ยท 5 comments
Not sure if anything can be done.
Tinkers Construct gravel ores require a shovel.
The Paxel is part shovel but does not mine the block.
I carry around a shovel in a backpack for when I encounter the gravel ores.
There are a lot of tools that don't work as they should on those gravel ores. It may be an issue on TiCon's end...
TC requires a shovel to mine gravel ore. The paxel is not presenting itself as a shovel to TC.
TC is not blocking other mods and/or only allowing vanilla shovels. I can use an obsidian shovel, from Mekanism, to mine the ore.
The paxel, although part shovel, is not presenting itself as a shovel to TC.
If you are not interesting in fixing this issue that is alright. Just say so. The last issue I opened here was closed unresolved because you were not interesting in fixing it, and that was ok. You do this for basically free, I, nor anyone else expects you to work on anything you don't choose to work on. It is discouraging however to have an issue marked closed, left unresolved, blamed on "the other mod", when clearly it seems the issue is not with "the other mod", and there is no explanation given as to why it is "the other mod"'s issue.
Without explanation, looking at the facts in front of me, the issue is not with TC. It is the mods that attempt to interact with it, not meeting TC requirements of a 'shovel'
If some insight was provided, I could take that information to TC development and attempt to resolve the issue there. Feel free to be as technical as you wish. The more technical the insight, the more help it should be to the development team at "the other mod"
The thing is, I've just tested this with our development version (the 1.8 branch) and TiCon 1.6.0d35 and I can dig gravel ores with our Obsidian shovel, paxel and Atomic Disassembler. It might be the case that a change in TiCon recently has stopped this issue (I'm not sure if you're using the same version or not), or we might have accidentally fixed it in the normal course of development. In any case, it's either already solved, or it will be soon, when we merge our development branch in.