J
jianmingyong
Guest
Describe the bug you experienced here.
What I expected to happen:
Being normal.
What actually happened:
The players in the server are shocked and think that someone is hacking or something because it has no name on the chat.
My screen look fine and can chat while the other says I am a ghost that doesn't have a name in the server.
Steps to reproduce:
1. Randomly.
2. Happen after this appear faintly on the Debug Logger.
]Chat.vb: Warning (22:24:23): Server misidentification: The server tried to destroy your player connection
3. Afk in official server for a few minutes. ( It should kick you, but instead of kicking... You became a ghost in the server. )
After that happen which has no visible notification... only Logger (F3 + L) can see this error, you became a ghost in the server and you can still chat in server no matter what...
This is my screen. No problem but what people will see is...
[SERVER]: Glitchy text... can someone screenshot this ghost bug so there is some proof to it.
Well those who manage to screenshot this will have the proof to this bug.
What I expected to happen:
Being normal.
What actually happened:
The players in the server are shocked and think that someone is hacking or something because it has no name on the chat.
My screen look fine and can chat while the other says I am a ghost that doesn't have a name in the server.
Steps to reproduce:
1. Randomly.
2. Happen after this appear faintly on the Debug Logger.
]Chat.vb: Warning (22:24:23): Server misidentification: The server tried to destroy your player connection
3. Afk in official server for a few minutes. ( It should kick you, but instead of kicking... You became a ghost in the server. )
After that happen which has no visible notification... only Logger (F3 + L) can see this error, you became a ghost in the server and you can still chat in server no matter what...
This is my screen. No problem but what people will see is...
[SERVER]: Glitchy text... can someone screenshot this ghost bug so there is some proof to it.
Well those who manage to screenshot this will have the proof to this bug.
Last edited by a moderator:
