Chris Baker

In case this does actually duplicate the bug I reported (I am not so sure it does): for me the key seemed to be that the weather mode which was naturally started doesn't respond to commands, but any player-initiated change in weather DOES respond to commands.

In any case where a player set for example "/weather rain", subsequent commands like "clear" would work properly as expected. In my testing, it only seems to be naturally-started weather that acts up.

@OcelotOnesie I do not think this is a duplicate. I saw the bug you are referencing, that is not the same problem.

The details here are not the same. As I mentioned, this can be reproduced instantly, it isn't related to desyncing, or switching apps, and it does not visually mismatch in this reported case. If I query the weather, it still accurately reports that it's raining. The key here is not a mismatch, but that the weather started naturally doesn't respond to the commands.

If I manually set it to rain, it will visually match, and if I manually clear it after that, it clears.

This isn't a duplicate.

Hello!  Yes, the issue does seem to have resolved.  Thank you!

I agree - I have confirmed that adjacency isn't a factor here. I was building a large structure and found glitch-placed blocks rather far from the area that I am currently working in. I also agree that it is incredibly annoying, FWIW.