Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Is this still a concern in the latest Minecraft version 14w08a? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
The reason for that is that currently the method keyTyped(char typedChar, int keyCode) in the class /Client/src/net/minecraft/client/gui/GuiSleepMP.java (MCP 1.8 names) calls this.mc.thePlayer.sendChatMessage(var3); which directly sends the message to the server, however it should call instead the method func_175275_f(String p_175275_1_).
/**
* Fired when a key is typed (except F11 who toggle full screen). This is the equivalent of
* KeyListener.keyTyped(KeyEvent e). Args : character (character on the key), keyCode (lwjgl Keyboard key code)
*/protectedvoid keyTyped(char typedChar, int keyCode) throws IOException
{
if (keyCode == 1)
{
this.wakeFromSleep();
}
elseif (keyCode != 28 && keyCode != 156)
{
super.keyTyped(typedChar, keyCode);
}
else
{
String var3 = this.inputField.getText().trim();
if (!var3.isEmpty())
{
// Changed thisthis.func_175275_f(var3);
//this.mc.thePlayer.sendChatMessage(var3);
}
this.inputField.setText("");
this.mc.ingameGUI.getChatGUI().resetScroll();
}
}
Note: For Minecraft 1.10 decompiled using MCP 9.30 the method that should be called is net.minecraft.client.gui.GuiScreen.sendChatMessage(String).
I can definitely confirm for 1.10.2. I've also noticed a second (related) bug:
Send the messages "#1", "#2", and "#3" in that order. Hop onto a bed and press the up arrow key twice, then Enter, to resend the "#2" message. Now, when you press the up arrow key again, "#1" will be displayed instead of "#3".
Can anyone summarize the above in one sentence? 😛
Can confirm.