Abasalt_Yar
Member
Awesome. Thanks a lotFixed in 1.5.1-b2
Awesome. Thanks a lotFixed in 1.5.1-b2
Actually, I don't know how it works. but I managed to get some info about it who was doing it. It's a TTF file and windows can't open it. One of my friends tried to see what is inside that file, It's a kinda like a word a square like the picture bellow@Abasalt_Yar If possible, I ask you to test the fix and give your comment.
Version 1.5.1-beta-2 has already been released and is available for download.
I didn't get it either, btw I'll send it to you maybe you could find out that I was put on or notHmm? Well that's definitively not related to the invalid name disconnects
IDK what the man had send you.
According to the last thing I understoodHmm? Well that's definitively not related to the invalid name disconnects
IDK what the man had send you.
I'm talking about this invalid parameter bugWell tbh I'm not sure what you're talking about.
The original thing within this topic has been resolved
It's fixed now, What are you looking for? You wanna learn the bug?I'm talking about this invalid parameter bug
I tried to understand the font or shape they use, I even connected the log server to the `discord` but even that font was unknown there.
I even tried to ban him from the server, but he did not seem to be connected to the server at all
I tested with TeaSpeak and Tea (m) Speak, but no one seemed to be connected to the server.
And was only seen in the log
This is my goalIt's fixed now, What are you looking for? You wanna learn the bug?
Uff you're making a really harsh accusation here.This is my goal
That WolverinDEV understands the bug
Because I think this is not just about the character of the name
This is a kind of sent Packet
Hello, I'm sorry and apologize.Uff you're making a really harsh accusation here.
But no in this occasion it's about the characters.
In general the "invalid parameter" disconnect can be triggered by various things.
But due to the trace log it became pretty obvious that the ascii control codes within the name of the client triggered it.