Modular Routers

Modular Routers

33M Downloads

Feature Request: Breaker Module Config Blacklist or Mining Level

Freedbot opened this issue ยท 7 comments

commented

I know you're not working on 1.12 anymore, but this probably applies to all versions... So I'm working on a 1.12 pack using Tool Progression to force more tiers of pickaxes. I was going through the various tools/blocks that can mine blocks without respect to their mining levels. Almost every mod with a block breaker is a culprit.

Simply having a blacklist config option would be enough, but ideally I'd like to see a mining level applied to the Item Router or Breaker Module and have them respected when breaking blocks as this would be most compatible with Tool Progression. It's fine if the default is something like =pickaxe=shovel=axe=2147483647.

commented

Thought: what if the crafting recipe for the Breaker Module was smart: the harvest level of the pickaxe used in crafting the module was transferred to the module itself?

E.g. use an iron pickaxe (the default recipe), and you get a module which can break things that an iron pickaxe can. If you want to break Obsidian, use a diamond pick to craft the module. Thoughts?

I would probably not limit the harvest tool (i.e. not prevent breaking of wood, even though the module is crafted with a pickaxe rather than an axe) but I can see the balance potential in limiting the harvest level...

commented

Yeah I can see why this would be useful. Let me have a think and I'll see if there's some nice way to do this.

Not quite sure what you mean by "=pickaxe=shovel=axe=2147483647" - can you explain a bit further?

commented

So, simply put, if you opt to give the router and/or breaker module a default harvest level and make it respect it, the Tool Progression mod allows me to configure that. If you set the router so that it counts as all tools and a ridiculously high level (the number is just a random high number), it's the same as current behavior of breaking anything, but more compatible with other mods and packs because it can be overwritten.

Hmm, I like your idea, and it's honestly more effort than I was expecting on your part, so thank you. I haven't heard of people messing with shovel and axe levels in packs before, so just controlling the overall mining level with a pick is good. Doing it that way would solve my issue, though depending on implementation I might end up still having to edit something.

I'll go ahead and explain what I'm doing a bit better so you know the use-case. In my pack I do the typical gimmick of nerfing all vanilla tools to 1 durability and -1 mining level to force Tinker's tools. Yes, I know people are tired of it, but I still like it and I don't force it for the whole pack. Anyway, here's a couple examples of mining levels I set for tinker materials:
iron=2, mines obsidian, netherrack
steel=3, mines redstone, glowstone, silver, gold, lapis
enderium=5 mines diamonds, certus, uranium

So if you made the recipe apply the vanilla mining level of 3 if crafted with a diamond pick, I would change the mining level to 5 instead... and possibly tweak the recipe to require certus or something since I haven't yet managed to remove the ability to villager trade for diamond picks... whatever.
If you somehow managed to make the module actually read and apply the mining level of the used tool or tool part... that would be perfect and amazing, but it would require a tooltip saying "has the mining level of the tool it's crafted with" so people are less likely to get confused if they craft with a vanilla diamond pick and end up being unable to break cobble with it.

... Thank you for the response and sorry for the text wall.

commented

I'm thankful that you added the feature to the latest version... Any chance on a backport though?

commented

Yeah I do plan to, just really busy on getting the 1.15.2 PneumaticCraft stable right now...

commented

This is now in the 3.3.0 release for 1.12.2

commented

Of course I didn't see this until right AFTER I finished uploading my modpack to curse for the first time for release. XD Anyway, thank you so much. I'll update it after I have my first wave of bugs to address.