"Advance in-game time" doesn't set time to noon when world is generated on Java Edition, but does on Bedrock Edition

"doDaylightCycle" (when false) stops the game-time at it's current point. This is an intentional feature.

Even if it's intentional for Java, this is still a valid parity issue.

I guess you could make additional settings for this, allowing the player to select what time for the world to start at.

We only accept bug reports about a parity issue as long as it fulfils the following criteria:

• The feature is present in both Bedrock Edition and Java Edition as of Buzzy Bees (Bedrock Edition 1.14 / Java Edition 1.15) or later (this is not the case here, "Always Day" or the /daylock command have never been a Java Edition feature)

• The feature behaves differently in one Edition than in the other (I guess this could be argued as a positive)

• The parity issue was not present prior to Buzzy Bees (The /daylock command as well as the "Always Day" button were introduced in Bedrock 1.2, long before Bedrock 1.14)

Therefore, this is not a valid parity bug report and should be posted on the feedback site instead.

I just looked on my phone and found out that doDaylightCycle does already exist on Bedrock, and does the exact same thing as on Java, so there's actually no parity issue at all. Always Day is a different setting, and therefore didn't get ported over to Java.