Tick command doesn't affect world border

The world border command takes 'seconds' as an argument for the measurement of time to shrink the world border, instead of ticks. The /tick subset commands shouldn't be affecting it since /tick doesn't speed up time, just the tick rate of the game (and mechanics tied to ticking).

Yes but every other command that has a time parameter uses units in relation to ticks. I see no reason for the world border to be the exception and to be inconsistent with all other commands, the world border ** is ** a game mechanic that should be tied to ticking, in fact the game does indeed tick the world border, but it updates it in realtime (ms).

I understand that by default it takes seconds as an argument, and changing it to be consistent with the other commands would change behaviours, but I think that just making seconds the default unit and allowing the user to specify ticks, days, etc. would still be preferable. Also the fact that the argument states that it is in seconds doesn't necessarily mean it will be, with the current time arguments you can specify seconds by appending a 's', however this does not mean it will actually take that amount of seconds instead that amount of seconds in ticks.

Duplicate of MC-53491.

Thank you for your report!
We're tracking this issue in MC-53491, so this ticket is being resolved and linked as a duplicate.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
_{-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.}