PaperMC
Port mspt command to brigadier
I only deprecated the old MSPT command since I thought there might be plugins out there that access the eval or getColor methods or check for the class name existence or other ~~intelligent~~ stuff
I wonder, couldn't we actually just fallback to spark's /spark tps command? That one displays far more useful information, which makes the classic Bukkit-style /tps command basically obsolete. Or is there actually a good use case for the Bukkit one?
EDIT: I re-read what this actually changes. This is for MSPT, mb lol. But my point basically still stands as long as we are touching these statistic-style commands
I totally agree but iirc there was a reason for the TPS command not being replaced with the spark TPS command, but that's better off being answered by a staff member.
The information conveyed by the spark TPS command is not only more detailed but also much more readable, so I would be in favor of replacing TPS and MSPT completely.
I don't feel there's any need to keep the old MSPT command... its not in the API at all.
replacing the output of the tps command was a concern due to various things reading the output of that, I've long also generally considered tps to be a useless metric and would defer to the mspt values instead; For as worthless as the tps is, it made little sense to care about randomly changing the format of the command and dealing with the consequences of that
