Information

Minecraft version: 1.20.1 (and 1.21.1 pls)
Modloader: Forge

Mod name: Mineral Chance

Feature description

Short: Give some way to use "partial gems" instead of full ones when provided by other mods.

Problem

Dropping whole gems seems a little much, especially when I'm struggling along early game and get three diamonds before I get an iron pick. At least for game-play that emphasizes "getting sidetracked" from the main Minecraft progression to do another mods content.

Proposed Solution

Whole gems are dropped presumably because there's no such thing as a gem nugget?
Some mods add shards - representing partial gems the way nuggets are partial ingots. Typically either from mods that recycle/break down things and give partial returns, as side bonuses as part of refining something, or from "poor" ores. (Some of the "poor" ore mods might have another way of handling gems, IDK)

If a mod has registered their shards in (forge side) forge:gems/diamond/shard, forge:gems/emerald/shard, or forge:gems/quartz/shard can we have an option to dispense the first one from that tag instead? Possibly making the tag customizable - IDK what the tag is on Fabric side but I doubt it's in the forge namespace 😆

Another Proposed Solution

Can the list of minerals being dropped be in the config file, or be tag driven? These would allow more customization by mod-pack developers (or advanced users) but won't have the same drop-in effect that automatically pulling from the tags gives.

Probably A Very Inconvenient Solution That Requires A Mod Rework

Change the drop table to be proportionate to ore generation in that chunk's biome.

Hey!

I appreciate the suggestion! While I'd love to add all features submitted on the issue-tracker, I've got to prioritize working on them due to having limited time. In order to see which features users would like to see most, I've created https://serilum.com/mods/requests, which shows a table with all feature request submitted.

I'm aware that this is not the reaction you were looking for, but the reality is that I can't keep up with the demand. I try to do as much as I can.

Users are able to upvote requests by reacting to the first issue comment on this GitHub page with one of the 👍 😀 🎉 ❤️ 🚀 👀 emoji's. The request with the most unique reactions, will be shown at the top. You can of course add the reactions yourself too, but don't have to :). The author of the feature is already counted as +1.

I won't only focus on popular features in the upcoming years, but it does help with prioritizing. I'll probably work on a combination of popular and interesting/needed/fun submissions.

I'll close this issue with "not planned" as a way to separate an open feature request from an actual completed issue. This does not actually mean it's not planned! Incompatibilities and bug reports will still remain open.

When the feature is implemented, I'll again post a comment and close it as "completed".

Thank you for taking the time to submit the suggestion! ❤️