Tier configuration (≥ 1.21)
penturt opened this issue · 15 comments
I have confirmed no other issue asks the same question
- I have searched for existing issues
Question
I feel i'm missing something, but how do i have it multi-harvest with mekanismtools hoes? i thought i added them to the config file correctly but its still not working.
Additional context
No response
yeah it works with the normal hoes... just can't seems to get it to work for mod hoes.
Yeah, that's to be expected. To make modded hoes work, you need to use the dedicated config options.
Which Minecraft version are on playing on?
just to clarify, multi-harvest works on normal MC hoes... its seems all Mod hoes can only "single" harvest
Take a look at the dedicated Wiki page for configuring multi-harvest, and let me know if you manage to reach your goal or if something is still not clear.
From a first glance, it looks like it should work (although maybe not the gobber2 ones, though).
It's late for me, so I'll check it out better tomorrow and let you know.
Yeah I don't have much faith in Goober, I just really care about mekanism. Thank I appreciate your time.
i followed the wiki, and from my understanding the tier setting should be somethin like this... but i'm having no luck
tiers = ["none", "wood", "gold", "lapis", "stone", "iron", "mekanism:bronze", "mekanism:refined_glowstone", "mekanism:steel", "mekanism:osmium", "diamond", "netherite", "gobber2:gobber2_ingot", "mekanism:refined_obsidian", "gobber2:gobber2_ingot_nether", "gobber2:gobber2_ingot_end"]
It turns out that Mekanism tools are not added directly by Mekanism, but by Mekanism Tools.
Since they are two different mods, they have two different mod IDs.
This is the correct configuration for Vanilla and Mekanism:
tiers = ["none", "wood", "gold", "mekanismtools:lapis_lazuli", "stone", "iron", "mekanismtools:bronze", "mekanismtools:refined_glowstone", "mekanismtools:steel", "mekanismtools:osmium", "diamond", "netherite", "mekanismtools:refined_obsidian"]
Gobber instead saves it's tags under the namespace c, so using the gobber2 namespace won't work.
Also, Gobber calls it's tool materials differently.
This the correct configuration for Vanilla, Mekanism, and Gobber:
tiers = ["none", "wood", "gold", "lapis", "stone", "iron", "mekanismtools:bronze", "mekanismtools:refined_glowstone", "mekanismtools:steel", "mekanismtools:osmium", "diamond", "netherite", "c:overworld_gobber", "mekanismtools:refined_obsidian", "c:nether_gobber", "c:end_gobber"]
The worked, thank you so much for your time.
Follow up question, from my understanding the you control the increment by using one of the pre-set values (NONE, SMALL, MEDIUM, LARGE) for "area increment step", and then tiers rank up that "increment" base on where the tool/material sits on the tier list.
if i could request a suggestion.
I don't think its possible with how it currently is, but is it possible to use a custom increment in my case something like "1" since i have so many tiers by the time i reach the final tier item I'll be clearing chunks worth of crops even if i keep it at "SMALL".
Or rather be able to group tiers, so rather then just one tier list which increments each step up, you can use multiple tier to group items and all item in that tier have the same increment stage...
for example: hoes in the same tier do no increment the multi range, just when you use a how from another tier. you can have it as it currently is by default and then allow for customization is the user prefers.
tier_1 = ["none", "wood"] 1x1
tier_2 = ["gold" , "lapis", "stone","mekanismtools:refined_glowstone"] 2x2
tier_3 = ["iron", "mekanismtools:bronze", "mekanismtools:steel","mekanismtools:osmium"] 4x4
tier_4 = [ "diamond", "netherite"] 5x5
tier_5 = ["c:overworld_gobber", "mekanismtools:refined_obsidian"] 6x6
tier_6 = ["c:nether_gobber"] 8x8
tier_7 = ["c:end_gobber"] 10x10
nonetheless thank you again for your help and time
It's a suggestion that definitely makes sense.
Unfortunately, due to some limitations of the configuration API I'm using, it's hard to implement and I don't have enough time at the moment.
But it's something that is likely to come in the future,
That is completely understandable, I'm happy just to have the idea up for consideration.
