[MC-8141] Chat Macro Error Created: 23/Jan/13 Updated: 14/Feb/17 Resolved: 14/Feb/17 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Minecraft 1.4.6, Minecraft 1.4.7, Snapshot 13w03a, Snapshot 13w07a, Snapshot 13w09a, Minecraft 1.5, Snapshot 13w11a, Minecraft 1.5.1, Minecraft 1.5.2, Snapshot 13w23b, Minecraft 1.7.2, Minecraft 1.7.4, Minecraft 14w28b |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jack Wilkie | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 3 |
| Labels: | chatbox, delay, lost, text | ||
| Environment: |
java 7 Update 11, windows 7 x64 SP1 |
||
| Issue Links: |
|
||||||||
| Confirmation Status: | Unconfirmed | ||||||||
| Description |
|
specifically this issue occurs when i use chat macros (typing very-fast/instantly) Expected behavior: minecraft detects 't' has been pushed then immediately puts whatever text is in the input buffer(i assume this is how it works) into the chat/command line Actual behavior: minecraft detects 't' has been press and opens chat, but fails to input other pressed keys into the chat Possible reason for bug: minecraft detects 't' has been pressed and opens chat, but does not start inputting text until next frame/tick, discarding all text entered before that point. To reproduce: 1. Get some macro software or a macro supporting gaming keyboard (Workaround - add delay into macro of about 50ms between pressing 't' and typing text, may not be supported by all software, and is annoying to do instead of 'quick macros' which are recorded on-the-fly in-game) |
| Comments |
| Comment by user-f2760 (Inactive) [ 14/Feb/17 ] |
|
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket. |
| Comment by Kumasasa [ 18/Nov/15 ] |
|
Is this still an issue in the current Minecraft Snapshot 15w47a or later? 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 Jack Wilkie [ 14/Jul/14 ] |
|
ok, sorry if i was a bit hostile, im just a bit annoyed with having to update this issue even when i dont play the game anymore I will add this, the issue seems to be somewhat improved in recent versions, sometimes only loosing a few letters, and occasionally working properly, however it is clearly not completly fixed |
| Comment by [Mod] Torabi [ 14/Jul/14 ] |
|
Many parts of the game have gone through massive rewrites over the last few major revisions, and it's expected that many bugs will have been fixed as a result, without the developers having set out to specifically fix those bugs. Thus, we ask the people most familiar with the bug and how to reproduce it to check if it still exists when the game has been updated. There have been cases where we didn't quite understand the reproduction steps (or accurate ones weren't provided), tested for the bug, and believed it had been fixed when we could not reproduce it. Since dinnerbone's rewrite of the chat system apparently didn't catch this, I'll bring it to his attention. |
| Comment by Jack Wilkie [ 12/Jul/14 ] |
|
It is still an issue with the latest snapshot Me not replying in a reasonable time is complete bullshit, this is 1 and a half years old, i have updated it several times due to being requested to, absolutely no action has been taken, it wont be fixed unless someone fixes it. I even fixed it myself some time ago with mcp. I haven't even actively played minecraft in over a year. If you keep treating issues like this then quite a few will never be resolved due to people getting annoyed with your bullshit, just fix the issue already. this isnt exactly a critical bug, but its still annoying, i almost gave up on it, and probably will next time. |
| Comment by [Mod] Ezekiel (ezfe) [ 26/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 Jack Wilkie [ 04/Jan/14 ] |
|
yes, it is still valid(updated), please just fix this now/soon, otherwise the version will have to be updated again, which i will forget, resulting in yet another message like this one, and the issue not being resolved |
| Comment by Talven81 [ 26/Nov/13 ] |
|
Is this still a concern in the current Minecraft version 1.7.2 / Launcher version 1.3.4 ? 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 Jack Wilkie [ 27/May/13 ] |
|
can someone comment, or do anything to this, it has been months since the last activity, and i would like this bug fixed in vanilla |
| Comment by Jack Wilkie [ 18/Mar/13 ] |
|
renamed to chat macro error |
| Comment by Jack Wilkie [ 18/Mar/13 ] |
|
yes it is, updated with steps to reproduce |
| Comment by Jack Wilkie [ 23/Jan/13 ] |
|
i have found a fix using MCP, so it wont look exactly the same to the source code at mojang, but it should be similar enough to showcase what has been changed in Minecraft.java, where keyboard events are handled, just before the handling of mouse events, change this: Minecraft.java } var8 = this.gameSettings.chatVisibility != 2; while (this.gameSettings.keyBindInventory.isPressed()) { this.displayGuiScreen(new GuiInventory(this.thePlayer)); } while (this.gameSettings.keyBindDrop.isPressed()) { this.thePlayer.dropOneItem(GuiScreen.isCtrlKeyDown()); } while (this.gameSettings.keyBindChat.isPressed() && var8) { this.displayGuiScreen(new GuiChat()); } if (this.currentScreen == null && this.gameSettings.keyBindCommand.isPressed() && var8) { this.displayGuiScreen(new GuiChat("/")); } to this Minecraft.java var8 = this.gameSettings.chatVisibility != 2; while (this.gameSettings.keyBindInventory.isPressed()) { this.displayGuiScreen(new GuiInventory(this.thePlayer)); } while (this.gameSettings.keyBindDrop.isPressed()) { this.thePlayer.dropOneItem(GuiScreen.isCtrlKeyDown()); } while (this.gameSettings.keyBindChat.isPressed() && var8) { GuiChat guiChat = new GuiChat(); this.displayGuiScreen(guiChat); guiChat.handleInput(); } if (this.currentScreen == null && this.gameSettings.keyBindCommand.isPressed() && var8) { GuiChat guiChat = new GuiChat("/"); this.displayGuiScreen(guiChat); guiChat.handleInput(); } } it basicly tells the chatGui to handle input after it is created also make sure to move that semi-colon from the top of the snippet to the bottom so that all of that code is included in the while(Keyboard.next()){} loop I have tested this and it fixes the issue perfectly, however i do not understand what all of the code does perfectly, so i suggest not using this fix immediately and instead, see what changed and fix that |