excluding ores from the gravel sieve

[kam789]

is there a way I can easily exclude ores from being able to be sieved?

[joe7575]

Yes, this is possible without modifying the gravelsieve code! The mod exposes a public API for this.

From your own mod (which should list gravelsieve as a dependency in mod.conf), call:

gravelsieve.set_probabilities({
    ["default:gravel"] = {
        ["mymod:ore_i_want_excluded"] = 0,
        -- add more ores to exclude here
    }
})

Setting an ore's probability to 0 effectively excludes it from sieving results. The remaining probabilities are automatically normalized.

This works because gravelsieve.set_probabilities() collects all overrides and merges them after all mods have loaded, so load order doesn't matter as long as the dependency is declared.

[kam789]

Yes, this is possible without modifying the gravelsieve code! The mod exposes a public API for this.

From your own mod (which should list gravelsieve as a dependency in mod.conf), call:

gravelsieve.set_probabilities({
["default:gravel"] = {
["mymod:ore_i_want_excluded"] = 0,
-- add more ores to exclude here
}
})

Setting an ore's probability to 0 effectively excludes it from sieving results. The remaining probabilities are automatically normalized.

This works because gravelsieve.set_probabilities() collects all overrides and merges them after all mods have loaded, so load order doesn't matter as long as the dependency is declared.

I am actually using your old stand alone sieve mod - https://github.com/joe7575/Minetest-Gravelsieve - because our server that we are upgrading already has technics and pipeworks. Would this fix work the same way on that?

[joe7575]

No, the standalone Minetest-Gravelsieve does not have the set_probabilities() API — that was added later in the techpack version.

However, the gravelsieve.ore_probability table is global, so you can still remove ores from another mod. You just need to do it after the ore table is populated (which happens via minetest.after(2, ...)):

-- In your own mod's init.lua (with gravelsieve as dependency):
minetest.after(2, function()
    gravelsieve.ore_probability["default:gold_lump"] = nil
    gravelsieve.ore_probability["default:diamond"] = nil
    -- remove any other ores you want to exclude
end)

Setting the entry to nil removes the ore entirely from possible sieve results.

[kam789]

No, the standalone Minetest-Gravelsieve does not have the set_probabilities() API — that was added later in the techpack version.

However, the gravelsieve.ore_probability table is global, so you can still remove ores from another mod. You just need to do it after the ore table is populated (which happens via minetest.after(2, ...)):

-- In your own mod's init.lua (with gravelsieve as dependency):
minetest.after(2, function()
gravelsieve.ore_probability["default:gold_lump"] = nil
gravelsieve.ore_probability["default:diamond"] = nil
-- remove any other ores you want to exclude
end)

Setting the entry to nil removes the ore entirely from possible sieve results.

awesome, thank you. You have to be the most responsive developer. It is amazing on this and also some of the issues we have had with techage on another server how fast you were to offer a solution.

[kam789]

No, the standalone Minetest-Gravelsieve does not have the set_probabilities() API — that was added later in the techpack version.

However, the gravelsieve.ore_probability table is global, so you can still remove ores from another mod. You just need to do it after the ore table is populated (which happens via minetest.after(2, ...)):

-- In your own mod's init.lua (with gravelsieve as dependency):
minetest.after(2, function()
gravelsieve.ore_probability["default:gold_lump"] = nil
gravelsieve.ore_probability["default:diamond"] = nil
-- remove any other ores you want to exclude
end)

Setting the entry to nil removes the ore entirely from possible sieve results.

****Nevermind, this worked perfectly and allowed me to change the probability on some other ores as well. Thank you so much for the help.

I did that in the init.lua, but on bootup the table looks the same as before. Would it be better if I pull the current sieve out of the techpack mod and use it?

[gravelsieve] moreores:mithril_lump 40
[gravelsieve] default:diamond 375
[gravelsieve] atium:atium_lump 731
[gravelsieve] technic:lead_lump 24
[gravelsieve] default:sand 83
[gravelsieve] technic:uranium_lump 56
[gravelsieve] default:iron_lump 38
[gravelsieve] default:mese_crystal 304
[gravelsieve] default:copper_lump 81
[gravelsieve] technic:chromium_lump 24
[gravelsieve] technic:zinc_lump 24
[gravelsieve] default:gold_lump 244
[gravelsieve] default:tin_lump 111
[gravelsieve] moreores:silver_lump 40
[gravelsieve] legendary_armor:ingot 3658
[gravelsieve] default:coal_lump 56
[gravelsieve] ethereal:etherium_dust 121
[gravelsieve] Overall probability 0.290393