Can confirm in 1.21.9-rc1
You’re right- it works for me now!
Still seems to be an issue, but maybe it’s just me?
I don’t think this is likely the case, because putting another keybind to F5 works as normal.
Hello,
Thank you for replying so quickly! Fair enough, however I would like to add that in literature, "focussed" is about 40x rarer than "focused," (according to Google Books Ngram Viewer) and I thus think it would be substantially clearer for your audience if you were to use the much more common spelling, but I of course understand that you're unlikely to change it, so no worries.
That's correct, my apologies, but I do feel that it isn't invaluable to have it phrased another way (since I did not find the other two when looking to see if it had already been reported)
It's fixed for me; it might be worth you updating your launcher
Because when it was reopened it wasn't fixed
This issue has not been fixed on the latest version of the launcher, even though it is marked as resolved, as Ray said.
As a side note (since it appears it was like this before it was 'fixed') if an instance of Minecraft is open, and one opens the launcher, the issue does not occur.
This issue seems to be fixed on the log-in screen but still not the loading screen
My point was that the message you were mentioning used to say that the accounts had not yet started being migrated but it was changed to say that they have now been migrated (see MCL-18510)
@Ined Can we please get some support here? or advice what to do? or should we just file for a refund?
@ryan to be more specific, the having to login regularly is something we've had as long as we've had minecraft for switch. The crossbow error code is new
also want to note, we've had the issue forever where the login doesn't seem to 'stick' - we have to re-login all the time. this is not an exaggeration.
Any more info please on whats happening here?
I apoligize for the awful quality, the only way I was able to capture this was using a seperate device because it seems like the frame rate needs to match the refresh rate. I may be able to make a better recording later this week. The issue shown in the video is slightly different to the one that caused me to make this bug report but it's the same principle just less obvious.
https://photos.app.goo.gl/ qXXMPRuz129gmXDS6
Here is the link, I can post the video in other ways if necessary.
!20201003_223754_Moment.jpg|width=546,height=308!
Here is a still frame of right after I respawned, just to make it more obvious since it is only visible for a moment.
I have had it happen to me in 1.16.3, I believe but it's really rare and I don't know why or when it happens
I have just tried to recreate this bug however, I was unable to
Can confirm. Interestingly, while both the original report and the second method described in the comment give roughly the same vertical momentum, the version where you mount/dismount quickly seems to give much more horizontal momentum (or at least it did when I tested it). Also, I don’t think you need to be holding a spear for this method to work.