Sebi Saati
- mini-me
- mini-me
- Europe/Stockholm
- Yes
- No
Every time when a player leaves the server it outputs the message to the log with the whole T
ranslatableComponent object rather than just its Text-property, for example:
[19:23:55] [Server thread/INFO]: Notch lost connection: TextComponent{text='Disconnected', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}
This makes the log harder to read afterwards. It's only a minor annoyance though.Every time when a player leaves the server it outputs the message to the log with the whole TextComponent object rather than just its Text-property, for example:
[19:23:55] [Server thread/INFO]: Notch lost connection: TextComponent{text='Disconnected', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}
This makes the log harder to read afterwards. It's only a minor annoyance though.I'd rather expect:
[19:23:55] [Server thread/INFO]: Notch lost connection: Disconnected
Server log outputs TranslatableComponent object rather than its Text property for player lost connection/Disconnecting messageServer log outputs TextComponent object rather than its Text property for player lost connection/Disconnecting message
I experience a similar related issue. My notebook has a screen with a native resolution of 1366x768. If I connect my external monitor with a resolution of 1680x1050 and play Minecraft in a maximized window on it, I can't use all of the inventory of a double chest for instance. Any slot that is higher on the screen than 768px cannot be clicked, neither the white highlighting of the currently hovered cell passes that height.
If I set the external monitor as primary screen in the screen resolution dialog of Windows it works fine, so probably the game assumes just the primary monitor screen realm is important for mouse pointer interaction.
I just tested this with my setup in Minecraft 1.5.1 and the bug is still there. Dear Mods, please update the affected versions for me, as Mojira doesn't give me the permission to.
I tried it with the new launcher in version 0.9.5 and snapshot 13w25c and release 1.5.2 and was unable to reproduce it. With the new launcher this bug is fixed for me (Windows 8).
This is still an issue in version 1.6.1. Anyone capable, please update the affected versions.
It's just obvious that it's not intended...
What's the additional benefit to knowing the text "Disconnected" should not be underlined, italic, bold, have no color etc.?
With the introduction of more advanced text formatting and translation this changed to the pretty unreadable format, which I imagine is because it was forgotten to change the disconnect reason from a simple string object to the property of the TextComponent object. Before the change one could easily read the server's output on the commandline. Now it takes up 3 lines and one needs to search for the actual information.
It's just an oversight, and I want to help by making it aware.