I noticed that if, for some reason, the /kill command is set to kill the player from a repeated command block, it may cause the player to be unable to pause due to being killed too fast to register inputs if the command came from an active repeating command block.
The more command blocks that cause this to occur, the more likely it'll be that you won't be able to pause(or the pause screen gets exited due to respawning). Lower framerates seem to help circumvent this to some extent, though.
Clarification: this only happens of doImmediateRespawn is set to true.
Linked issues
duplicates 1
Comments 3
It is killing the player, yes, but it shouldn't also prevent the player from pausing the game if they immediately respawn.
Thank you for your report!
We're tracking this issue in MC-215769, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as invalid. Please take a look at the parent ticket (MC-215769) and see if an explanation is provided there in the description of the ticket or in the comments for why this issue is invalid.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Not a bug. The command block is just doing what it was told.
Duplicate of MC-215769.