mojira.dev
MC-249308

The "randomTickSpeed" gamerule does not affect the speed at which tadpoles hatch from frogspawn

The Bug:

The "randomTickSpeed" gamerule does not affect the speed at which tadpoles hatch from frogspawn.

The speed at which turtles hatch from turtle eggs is affected by the "randomTickSpeed" gamerule, so it seems rather strange that this concept doesn't apply to tadpoles hatching from frogspawn.

Steps to Reproduce:

  1. Place down some frogspawn.

  2. Set the "randomTickSpeed" gamerule to a high value in an attempt to increase the speed of the frogspawn hatching by using the command provided.

    /gamerule randomTickSpeed 3000
  3. Wait around thirty seconds and watch the frogspawn closely.

  4. Take note as to whether or not the "randomTickSpeed" gamerule affects the speed at which tadpoles hatch from frogspawn.

Observed Behavior:

The speed at which tadpoles hatch from frogspawn is not affected by the "randomTickSpeed" gamerule.

Expected Behavior:

The speed at which tadpoles hatch from frogspawn would be affected by the "randomTickSpeed" gamerule.

Linked issues

Attachments

Comments

migrated

This is a feature request.

[Mod] EVGENSYPERPRO

@unknown: Please consider this issue as a parity issue and not a feature request, as in bedrock version of "randomTickSpeed" affects tadpole hatching.

[Mod] EVGENSYPERPRO
migrated

This "fix" is backwards, random tick speed SHOULD affect frogspawn to be consistent with other game mechanics but instead now both platforms are broken.

Sniper1.1

randomTickSpeed should absolutely affect the hatch speed to be consistent with other blocks. It should be that way on both Java and Bedrock. I was just making a map and wanted to have them be there as decoration, but they just hatch. That's different behavior compared to so many other blocks.

Avoma

(Unassigned)

Confirmed

Gameplay

Normal

Parity

randomTickSpeed, vanilla-parity

22w11a, 22w15a, 22w17a, 1.19, 1.19.1, ..., 1.20.4, 23w51b, 1.21, 24w45a, 1.21.4

Retrieved