| Type: | Bug | ||
| Reporter: | Ryan S | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 32 |
| Labels: | bed, chat, chat-history | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| CHK: | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Confirmation Status: | Confirmed | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Category: |
Commands
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
The bugWhen in a bed, typing and submitting a message and/or command will be forgotten if you try to access that with the arrow keys while out of bed. Code analysisCode analysis by marcono1234 can be found in this comment. |
| Comments |
| Comment by [Mod] Greymagic27 [ 12/Mar/20 ] |
|
1.15.2 is already in the affected versions list, please make sure you check there before confirming. |
| Comment by [Helper] ZeNico13 [ 17/May/19 ] |
|
Still in 1.14.2 Pre-Release 1 and 1.14.2 Pre-Release 2 |
| Comment by [Helper] ZeNico13 [ 13/May/19 ] |
|
Still in 1.14.1 Release |
| Comment by [Helper] ZeNico13 [ 23/Apr/19 ] |
|
Still in 1.14 Release |
| Comment by [Helper] ZeNico13 [ 19/Apr/19 ] |
|
Still in 1.14 pre-3, 1.14 pre-4 and 1.14 pre-5 |
| Comment by [Helper] ZeNico13 [ 12/Apr/19 ] |
|
Still in 1.14 Pre-Release 2 |
| Comment by [Helper] ZeNico13 [ 12/Apr/19 ] |
|
Confirmed for all Minecraft 1.14 snapshots, especially in 19w14a, 19w14b and 1.14 Pre-Release 1 Messages and commands sent while in a bed won't be remembered in sent history.mp4 |
| Comment by Kraif [ 29/Aug/18 ] |
|
Confirmed for 1.13.1. |
| Comment by user-2a4c8 (Inactive) [ 26/Jul/18 ] |
|
Confirmed 1.13 |
| Comment by [Mod] tryashtar [ 19/Nov/16 ] |
|
Still here up through 1.11, by the way. |
| Comment by Marcono1234 [ 13/Jul/16 ] |
|
Good catch! It is now MC-105303. I hope the title fits well And sorry for stealing you the chance for a code analysis |
| Comment by null (Inactive) [ 13/Jul/16 ] |
|
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? |
| Comment by Immaterialise [ 17/Feb/16 ] |
|
Confirmed for 1.9-pre1 |
| Comment by Marcono1234 [ 12/Dec/15 ] |
|
Confirmed for
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) */ protected void keyTyped(char typedChar, int keyCode) throws IOException { if (keyCode == 1) { this.wakeFromSleep(); } else if (keyCode != 28 && keyCode != 156) { super.keyTyped(typedChar, keyCode); } else { String var3 = this.inputField.getText().trim(); if (!var3.isEmpty()) { // Changed this this.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). |
| Comment by ZuzuTyp [ 19/Aug/15 ] |
|
confirmed for 15w34a |
| Comment by C_moneySmith [ 08/Nov/14 ] |
|
confirmed for 1.8 official release |
| Comment by Eric [ 24/Aug/14 ] |
|
Confirmed for 1.8pre1 and before. This is a little annoying, but not game breaking, but I think the fix shouldn't take much. |
| Comment by Marcono1234 [ 01/Jun/14 ] |
|
Confirmed for 14w21b |
| Comment by [Mod] Ezekiel (ezfe) [ 24/Feb/14 ] |
|
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. |
| Comment by Lucas Jed [ 07/Aug/13 ] |
|
I'll just say I can also confirm this! |
| Comment by Tails [ 16/Mar/13 ] |
|
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. |
| Comment by [Mod] CubeTheThird [ 15/Dec/12 ] |
|
Can confirm. |