d benj

Not a bug.  Both "Sorry ..." and "Sorry, ..." can be used here with equally apropos application. One implies "Sorry (that an error-state has occurred)..."  The other expresses the developer's sympathy with the user experiencing such.  Suggesting a missing comma is incorrect here is both incorrect and a waste of dev cycle resources in reporting.

Certainly, a lower-case "n" is a bug that affects core functionality of game-play and overall user experience, and should be tended-to and tracked with a software bug tracker.  😉

How is this a bug?

How in any sense does spelling "third-party" with or without hyphen affect code, function, game-play, user experience, ROI of those funding the dev. of Minecraft or those purchasing it?

This has zero impact on the final deliverable, game play experience, and is not a 'bug' nor should any reputable dev cycle or ITSQA bug tracker consider it one.  This is cruft.

This isn't a dupe of MC-209432 , btw.  None of the steps-to-repro and resolve that bug apply here.

gornemant is 100% correct – This is a bug exactly as described after Mojang --> Microsoft account migration and attempting to use "/t" for in-game Minecraft chat.

All Microsoft / "xBox Live" settings are correct for enabled chat.  No one has made a client-side or server-side change.  I've played Minecraft for seven years, done ITSQA for eight, and been in general IT Ops wrangling things from pseudo-code to server switches for 25 years.  This error happens after the account migration.