Talk:Budding Amethyst

Mining the block
I tried using silk touch on it but that didn't work. So I tried getting silk touch III wasting about 300 levels, 40 lapis blocks, and an hour of my time. I later learned there was only silk touch I. I thought I recalled once having silk touch III or even II. I was wrong. I just found out you need a piston to get budding amethyst. I'm going to do that now. 134.228.42.240 22:32, 15 June 2021 (UTC)
 * I wouldn't suggest that either. This page actually states that pistons break it without dropping anything as well. Anyways, the developers intended it to work similarly to a spawner, where the player can use it where it is located, but it can't be moved from its original location. PegasusDust (talk) 02:57, 16 June 2021 (UTC)

Amethyst Farm Warning
You can't mine budding amethyst! It's only renewable to farm many amethyst clusters! If you get lost, please dig upwards (↑ up arrow). Sometimes blocks can get a low pitch in Java Edition and low or high pitch in Bedrock Edition. This changed 0.75 when falling on a block, 0.5 when digging a block, 0.8 when placed or broken and 1 when stept! That's how sounds on minecraft work. You can also check if many sounds are with the corresponded sounds. /stopsound intended Akiro Josué López Donayre (talk) 01:21, 14 December 2021 (UTC).
 * I don't understand your point. Budding amethyst is not renewable, available only in creative inventory, and therefore cannot be farmed. Amatulic (talk) 00:33, 17 December 2021 (UTC)

Growth rate math check
Before updating the article itself (and the tutorial farming page as well), I'd like to see if folks agree with my math on how long it will take to grow an Amethyst Cluster from a Budding Amethyst. Since automatic farming produces much less output than going in manually with Fortune 3 pickaxe every so often, a method would be to visit a geode when it is all fully grown rather than snip at the clusters as they hit maximum growth. Less efficient in terms of output, but lets you do something like AFK a nearby farm or do some building in the area.

Logic: 1. Per Tick, random Ticks will update a block on average of 68.27 seconds if the chunk is loaded. 2. There is a 20% chance of an update to either add a new bud or advance the stage of an existing bud. 3. All 6 sides are considered.

(68.27 seconds) x (20% chance of growth) x (6 sides) x (4 growth stages) = 68.27 x 5 x 6 x 4 = 8192.4 seconds average, aka 2.27567 hours, aka 2 hours 16 minutes 32.4 seconds, aka 6.827 in-game days.

Also, will a chunk loader allow the amethyst to grow, or is it restricted to only chunks within 128 blocks of the player?

Clarence2001 (talk) 18:35, 29 June 2022 (UTC)
 * The faces are chosen at random 1/6 of the time, not all 6 faces. --Pneuma01 (talk) 18:41, 29 June 2022 (UTC)


 * Yes, each side is selected at random, which is why I included x6 in the calculation. To determine one side would only be (68.27 seconds) x (20% chance of growth) x (4 growth stages) = 1365.4 seconds, assuming that the same side was randomly selected each time and an even distribution of the 20% chance for growth to be 1 in 5. However, the same 1 in 6 side being selected in entirety from no bud to full amethyst cluster is purely theoretical, not a practical value, which leads in to that assuming even distribution of the 1 in 6 chance that any given side will be selected for a growth update, then the 1365.4 seconds would be applied to all 6 sides equally. The formula would be 1365.4 x 6 = 8192.4 seconds average, which is what I had listed above.


 * The Random var3 being constrained to (5), is this a < or a <= range? It clearly at least uses a minimum value of 0 since that is the True condition, but is it 0-5 or 0-4? Because 0-5 is 6 possible digits, meaning a 1 in 6, or 16.67%, chance. But 0-4 is 5 possible digits, meaning 1 in 5, or 20%, chance. If it is a 0-5 range with <= then the 1/6 chance would push the time to 9830.88 seconds average, or 2.7308 hours (2 hours 43 minutes 50.88 seconds), a difference of 27 minutes.
 * Clarence2001 (talk) 01:24, 30 June 2022 (UTC)
 * java.util.Random.nextInt returns an int value between 0 (inclusive) and n (exclusive).--Pneuma01 (talk) 12:02, 30 June 2022 (UTC)
 * Thank you! So does my explanation work with a 6-sided growth to full taking 8192.4 seconds on average? Clarence2001 (talk) 20:15, 30 June 2022 (UTC)
 * I think there's more to consider. Your calculation indicate that, on average, a growth will occur every (68.27*5) 341.35 seconds, 24 total growths are needed, and one will happen at each interval.  The code that Clarence2001 shared, it looks like the growth direction is always random.  If that is the case it will take (considerably?) longer to grow all 6 clusters.  Consider the case where only one more growth is needed to fully grow the last side. If the direction of the growth attempt is random, it only has a 1/6 chance of being successful since 5 directions are already completed.


 * The math becomes complicated statistics. For example, if the first 4 growths all happened in the same direction, the next attempt only has a 5/6 chance of being successful.  In the more likely situation where the first 4 didn't happen in the same direction, the 5th growth attempt will always be successful. --69.242.231.43 10:22, 25 August 2022 (UTC)