Azkunki

@[Mod] Galaxy_2Alex
I think "die" is misleading (the dolphin's HP doesn't instantly drop to 0. Unless that's what happens now ? Although I would then say it must actually be another bug). Probably not that important but I prefer to change that 🙂 (and while I'm at it, moving "out of water" because it currently implies spawning the dolphin in water then moving it out of it does the same, which is not the case)

@Michael Wobst

Looks like it indeed ! I guess my issue can be set to "Resolved" then (but maybe still make them related ? Seems possible to me that my issue could come back by fixing MC-187598, depending on how it would be done).

Seems mostly fixed with 1.16 pre2, although not entirely. This is the most I could do with this new pic, and only with honey blocks :

It seems to depend a lot on what is under the water. In short, with sand well lit, the line disappears a lot more, while sand less lit or dirt make the line more visible (I could even notice it with fishes passing by).

@anonymous : No. We're talking about a keyboard shortcut that can more or less work anywhere, not only on Minecraft. And for this reason, even if it was possible to change the keyboard shortcut, it would be a bad idea since you would get used to your custom shortcut on Minecraft and keep doing it outside of Minecraft as well, where it would still be Ctrl+A. If would ever get used to your custom shortcut on Minecraft (which wouldn't prevent using the wrong shortcut more or less often, even out of Minecraft, most likely).

Also, even if it was possible to change the shortcut AND that it was a thing only on Minecraft, it could still be an issue, since as you said yourself, not every key fits the way you play.

I can only agree with @ZeNico13 (and, I mean, it's the bug update. If it's not a priority now, when will it be ?). However, and although it does not concern me anymore thanks to my new computer (but for the sake of those that are still affected), I'd like to remind you that there's also MC-127862, which will become worse if and when MC-121278 will be fixed (if it's the only one of the pair to be fixed).

In short, it would become worse because it would mean that Ctrl+A wouldn't require to actually (physically) do Ctrl+Q on the keyboard, hence with MC-127862, when writing something, it would become far, far more common to lose everything, since "A" is obviously much more common than "Q" (MC-12762 is basically the Ctrl key being virtually locked, so keyboard shortcuts can interfere, in a variety of ways, while doing something else).

Yeah, still happens on my laptop (maybe a little harder, but still pretty easily).

That's good news I guess ! Although it would be nice to get feedback from more people. In any case, I may check on my laptop later (since I still have it), it would be interesting to see if I can still reproduce that bug. Especially that I think on the contrary the new hardware helped for me ^^ (although not necessarily from being more powerful) I mean, pressing Alt Gr for about 1h30min was on 1.14.4, where we know the bug wasn't fixed ! (doesnt mean it was fixed for me, but it became at least really hard to reproduce, thus either impossible or very unlikely to happen under normal circumstances).

I never tried myself on that version though (not on my laptop), only on 1.14 (and without Optifine, since it wasn't out yet back then (may be a nice idea for my test on my laptop to do it without Optifine actually, and if I can reproduce the bug, try again but this time with Optifine). Even with 1.13 I never tried reproducing it with Optifine, I was barely launching the game once in a while for some tests).

Can anyone still reproduce this bug ? I assume it's still there, but I'm on a new computer now, and I can't seem to reproduce it anymore (even tried putting something on Alt Gr while I was away, which was for about 1h30min, but no. That was on 1.14.4, which was already confirmed by @Sven).

I've been thinking it could maybe be caused by hardware ? My laptop (on which I had the bug) had Intel i3 CPU and NVidia GPU (GTX 410M I think). My new PC has AMD Ryzen 5 1600 CPU and AMD RX570 GPU.

And Windows 10, although it doesn't seem at all to change anything.

EDIT : Also my framerate was still limited to 30 (like before). Since I talked about framerate that may be at least part of the issue. Although I probably had a quite more stable 30 fps than on my laptop.

@Stef B

Except that if you start doing that in Minecraft, you'll get used to doing that out of Minecraft as well :/ Which then makes it annoying anywhere, not only in Minecraft. And to make it even worse, Ctrl+Q is a shortcut that can sometimes act like Alt+F4 (and you won't always get a warning saying you have unsaved changes. For instance, if I do it like that, when writing in my browser, it won't always warn me about anything, depending on what site I'm writing (although it doesn't seem to work anywhere anyway right now, for me. Which is weird, especially that I'm pretty sure it should have worked on Firefox and windows explorer (also tried on Notepad++, but I may have unbound that there, which could be an explanation). Maybe I've got some bug that makes that useless yet potentially annoying shortcut not work anymore for me ?)

@val59000mc

It's not at all the third most voted bug (it's the 287th), and it has been reported around 1.5 year ago. Which doesn't change that it's surprising such a bug is still around after so long of course, it's like they don't care (which is why I'm not active anymore here, and as well why I have much higher hopes in "you-know-what-game-I'm-talking-about" (or maybe not, but I obviously can't say here clearly what I'm talking about). At least it's quite promising on every aspect so far (and with some luck, maybe it will make Mojang wake up)).

I'd like to add something I said in my bug report (that is a duplicate). So I'll copy-paste that here. Like I said there, I'm not sure this was something that existed, but even if it wasn't, I'm hoping the devs couls add that while they're at it, because it would be so useful ! (at least for IDs such as scoreboard criterias) So here it is :

" I can't remember if something like that was there in 1.12, but a useful thing would be to have additionnal suggestions that would always be at the top (except if there are results that would end before having a "non-letter character") but that would never suggest anything after the next "non-letter character".

Explanation :

• Start with nothing written for the criteria → Every ID is suggested

• Type "d". Let's imagine you have a mod called "Doors" → Suggestions will be "deathCount", then "dummy", THEN "doors" items

• Delete that "d", you actually wanted to type "minecraft" → Suggestions are "minecraft.", then all the full IDs starting by that

• Add that dot → Suggestions are "minecraft.broken:", "minecraft.crafted:", "minecraft.custom:" etc (so we have a clear list of what is possible directly after "minecraft.", instead of having to scroll down for half a day or try every letter, and more than carefully since something like "crafted" and "custom" happens), and then we have all the full IDs starting by that

• Tpye "c" → Suggestions are "minecraft.crafted:" and "minecraft.custom:", then all the full IDs starting by that (as usual)

► So, in short, nothing changes at all about which full IDs are shown, we only add what are all the categories in which they are scattered. "

I'm not sure what to think. It seems to have only been partially fixed, in the sense that you can for example write "minecraft:acacia_button{}" without having an error being displayed, but the game still doesn't suggest opening a curly bracket. Of course, this block would have no use of it (and it seems to be why that bracket isn't suggested, the same way " { " and " [ " are both "missing" for blocks such as carpets). But I guess a mod could add one ? Maybe that in this case, the curly bracket would then automatically start being suggested as well ? That would be a nice thing, but I am unable to test if that's the way it works.

To make it clear though, now " [ " does show in most cases for /fill, /setblock and /clone, as well as " { " for /give, /replaceitem and /clear (normal blocks only for the last one). And if the fact that they don't appear for any block is intended, then I guess we're still missing the suggestion " { " for all "#blocks" in /clear commands (but then I think it would be the only thing missing).

As for the part of the bug where I talked about brackets not showing after a tab-completion, I realized it must be WAI since "Tab" can be used to move between the suggestions. Of course it won't both allow to navigate through the block suggestions but only suggest the brackets at the same time.

It would have been nice if the game could provide the bracket suggestions in a more intuitive way, but both solutions I thought of are bad (keeping in mind a player not knowing about these brackets should still easily see them being suggested).

Anyway, maybe I should remove that part ?

@ZeNico

I said "having this bug still around is still better than fixing it BUT not fixing at the same time MC-127862". That means "the best would be to fix them BOTH as soon as possible", not "it's better to not fix these bugs at all".

"Plus, there, we are talking about keyboard shortcuts that are often used in game!"

Except that it does not have irreversible consequences, it's annoying at most. Whereas MC-127862 is a bug that is far worse since there you can lose everything you were writing (something you might not remember well, and the bug stays active as long as you don't happen to press "Ctrl". And in top of that, only the left one works if I'm not mistaken. So if you don't know how to stop the bug, you're in for a lot of trouble, maybe up to restarting your game. Because EVERY time you will use arrow or deletion keys, it will act for the whole word). And if you fix the bug with shortcuts combinations using A (or Q / Z / W / M), as I already said, it will just make MC-127862 much worse. Because then, every single time you will type an "A" while the bug is active will instantaneously delete everything you were writing (I mean, this time you won't even have the time to realize you should stop pressing backspace (most likely) and maybe save some text from deletion, and it will occur insanely often since the letter "A" is a pretty common one. Maybe even more (a little more) in French than in English ("on vA pAs se mentir, cette combinAison de bugs est pArticulièrement chiAnte").

In other word, to never be affected by this bug even when it's active, you would manage to always write exactly what you wanted to write (so never in need to modify anything) while doing a lipogram in "A"... Good luck :/ (a lipogram in "Q" is much, much, much easier, you can't disagree on that)

NB : A "lipogram" is a text in which you purposely omit one of several letters. Doing so with the letter "E" of course is the hardest, but it's still quite a challenge as well with the letter "A". While the letter "Q" is quite pretty easy to avoid.

Still in 1.13.

@Bertrand @Valentin @Jonathan

In my opinion, having this bug still around is still better than fixing it BUT not fixing at the same time MC-127862. For a short explanation of the issue : "Alt Gr" can cause "Ctrl" to be virtually locked. Meaning that when it's the case, typing the letter "A" (quite common letter) would delete everything (which already happens on QWERTY / QWERTZ keyboards that also have an Alt Gr key, such as german ones).

Of course, that bug isn't problematic only with "A" key, but it would make it worse.

Even more efficient way to waste one's time than here, though.

@Neko

Because everything it says is false ? That's what you're implying... Not everything written there may be true, but how was I supposed to know that this information was false ? And by the way, is it even indeed false ? I mean, I doubt you know by heart everything down to its slightest details yourself, so it could very well still actually be true, just you not knowing.

Now, whether the wiki was right or not, the only thing I can say is that it would be a nice feature.

@Kumasasa

No, it's something different. The issue you linked involves pressing simultaneous keys, but is not in any way caused by Minecraft (as stated there. There are plenty of combinations that are impossible, but precisely because it's a hardware issue, these combinations are 'never' the same from a keyboard to another).

Here, it is by holding for a little too long a single key ("Alt Gr"), and that's an issue that wasn't there in 1.12.2.

@Dominik

Not seeing the fps fluctuate doesn't mean they don't fluctuate. And although I highly doubt the bug is caused by low framerate, it does seem to worsen it (at least in some cases). Doesn't mean it's the case, but you should check with Alt + F3 (the graph don't show up every time, so it may be necessary to try several times, and it never works when F3 infos are already visible, so hide them first), you should check if you have at least some little lag spikes, when playing normally, that would bring you... let's say under 60 fps. You can try as well to limit your fps to 30, to check if it gets worse or not.

@Violine

I'm on Windows 7. But it looks like it's not due to the OS anyway.

Did you try to limit the fps to 30 ? Also, maybe you didn't wait long enough ?

@FVbico

I never said either it was marked as fixed for pre6, and it just so happens I do remember it was indeed already "1.13+". Now, if that wasn't short before pre6 came out, then it was short after that (fixed at 3PM, Rima's comment at 3:42PM. But is there a way to know the exact moment a version was released ? If so, it would allow to check. Else it doesn't matter much anyway x) Thanks for the info with the tabs by the way, never really paid attention to them, could prove useful)

@Play Dash

But it was "Fixed" short before 1.13-pre6 came out, hence RimaNari's comment (and maybe Greg's one too, I don't know).

Now, we will soon see anyway whether pre7 fixes this or not (but it most likely will, of course), so let's just wait for that ^^

Not visible does not mean nonexistent. It could still be in the code, and most likely was.

And I just tried, by the way, and in 1.13-pre4 (because I have a profile with last snapshot and a profile with pre4 but too lazy to move to pre5 whereas it changes nothing here) :

• Adding "Moistness" doesn't work (I guess it didn't even have a name yet anyway)

• The dolphin would already start to take damage after 2400 ticks (2 minutes). I recalled when launching the game that I was wondering about that too, so I checked while I was at it.