/tick unfreeze and freeze both return their positive outputs even if the game was previously in that state

If you run /tick freeze multiple times in a row, "The game is frozen" outputs each time.

Similarly, /tick unfreeze outputs "The game runs normally" each time.

I would expect these outputs only if the previous game state was the opposite, and a different message if not.

For instance, /tick freeze should only say "The game is frozen" if the game was not frozen right before running it. Any further runs while frozen should give an output related to already being frozen.

The outputs of these right now are technically not incorrect, but having a different message show up if the game is already frozen and you try freezing it (and vice versa) would provide more clarity I feel.