Copied text can include spaces, line breaks or substituted punctuation that the login field treats as different characters.
Why this happens
A login field does not necessarily interpret text the way it looks in a message. A leading or trailing space, a line break inserted during copying or a different punctuation character can change the value submitted. A server address can also lose a port or part of its path when only the visible portion is selected. These are field-content problems rather than proof that the player or account has been replaced. The useful comparison is between the privately issued value and what the field actually contains.
Inspect the beginning and end of each field without exposing it in a public screenshot. Where practical, clear the affected field and enter the original value through a supported private route, preserving deliberate punctuation and letter case. RFC 3986 explains why URL components and characters matter; credentials can have their own case and character rules as well. Do not normalize every symbol or remove internal characters simply because an online example uses a simpler password. If manual entry works, keep that result with the affected field so repeated password resets do not become the default response to a copying problem.
A useful way to work through it
Inspect each field’s first and last character for an accidental space or line break.
Re-enter only the affected value from the original private instructions.
Keep deliberate case and punctuation rather than simplifying the login to match an example.