Andrew F

You need to start with a vanilla client. No modloader. Then once you can produce the issue, try to make the test case as small as possible. Provide screenshots.

Yes, this bug is caused by window management (not specifically the window being out of focus), but it does not pause the game. Incredibly it can be used in multiplayer, and all other players can interact with the player as they are stuck in midair.

Players apparently use this as an exploit to gain an advantage in competitive games, a Web search led me to people chatting about this back in 2020. I also saw mention that it can be done by reloading texture packs or taking screenshots repeatedly.

I can repro by right-clicking the title bar in the 1.21.3 release on a Realms server. Can this bug be reopened, or else linked to an open ticket (I could not find any)?

I cannot reproduce the issue in 1.21.1, in single player or on a Realms server.

Potentially related to AA/AF like MC-1794? Consider re-testing with the workarounds listed in the "Mod Notice" on that ticket and adding findings.

When reporting bugs against version 1.20.6 please make sure you have actually tested in version 1.20.6.

I can see that this was fixed in 1.20.5, and the translatable text was added:

"commands.setworldspawn.failure.not_overworld": "Can only set the world spawn for overworld",

Attempted to reproduce it anyway:

the_nether:

/execute as @p in minecraft:the_nether run tp @p 0 100 0
/setworldspawn 0 100 0

the_end:

/execute as @p in minecraft:the_end run tp @p 50 60 50
/setworldspawn 50 60 50

Seems like a misunderstanding of the selection syntax. Try again, with syntax like this:

/kill @e[distance=0..50, type=!player]

The reason you were not allowed to report this against 1.20.5 is that Mojang does not intend to investigate an issue that is already resolved, so you are expected to try to reproduce the bug in the latest release (1.20.6) before reporting it.

Affects Version/s: 1.20.6

Environment: Windows 11, Minecraft Java 1.20.4/Fabric (Modded)

These two things probably need to be reconciled. I would expect an environment that matches the reported version.

I don't think -0.5 is meant to be a valid value, I believe that attribute is defined to be min 0.0 & max 100.0. If -0.5 is not failing, a separate bug to be filed?

What color is +0.5?

Likely WAI.

Being able to apply the enchantment does not indicate that the enchantment should have any effect. You can replace "bow" and "crossbow" in the example commands with "wooden_sword" to get a wooden sword with Quick Charge V. Actually, you could put the enchantment on a cherry_boat if you want.

Quick Charge can still be a crossbow-only enchantment. I don't see anything suggesting Mojang wanted to make it more versatile. Perhaps it will be considered a bug that Multishot and Piercing work on bows.

I have just experienced this after updating to Bedrock V1.16.221

Playing on a Bedrock realm, I had logged in and out a few times whilst building so I could look at a reference on a creative world, after a while I realised that some villagers were missing, I had a look around and something like half the villagers and animals near my base were gone.
3 of 4 villagers, 1 of 2 iron golems, 10 of 16 sheep, about 10 of 16 cows, 1of1 horse, 3 of 3 rabbits. Some cats and a dog were unaffected.

The villagers and golem were free to roam, but the cows and sheep were confined to pens.
I was working near the villagers and sleeping through the night, so I know they weren't killed.
The animals had been in those pens for weeks with no escapes.

I guess they disappeared when logging out then back in again, but can't confirm.

It's true that Realms is more strict than the game, but according to the ECMA-404 spec, newlines, carriage returns, and tab characters are illegal within JSON strings:

Insignificant whitespace is allowed before or after any token. Whitespace is any sequence of one or more of
the following code points: character tabulation (U+0009), line feed (U+000A), carriage return (U+000D), and
space (U+0020). Whitespace is not allowed within any token, except that space is allowed in strings.

In fact, even in JavaScript, which is much less strict than JSON, those characters are not allowed (per ECMA-262):

All characters may appear literally in a string literal except for the closing quote character, backslash, carriage return, line separator, paragraph separator, and line feed. Any character may appear in the form of an escape sequence.

Finally, single quotation marks have no importance in JSON syntax, so they should not be used in JSON to mark strings (incl. the nested JSON inside the tag definition).

These example lines:
 

"tag": "{     
              title:\"Book title\", 
              author:\"Some name\",
              pages:[   
                \'\"text\"\'
              ]
            }"

... should become:

"tag": "{     \n              title:\"Book title\", \n              author:\"Some name\",\n              pages:[   \n                \"\\\"text\\\"\"\n              ]\n            }"

or you might as well compress it, since it's hardly readable anyway:

"tag": "{title:\"Book title\",author:\"Some name\",pages:[\"\\\"text\\\"\"]}"

I agree there is a bug here in that the parse & validation are inconsistent, but I don't necessarily agree that Realms is wrong.

Here is a JavaScript snippet I tested in Chrome that should convert your loot table(s) to be compliant with Realms and then will copy it to your clipboard:

var loot = {
    "type": "minecraft:loot",
    "pools":
      [{   
        "rolls": 1,
        "entries": [{
          "type": "minecraft:item",
          "name": "minecraft:written_book",
          "functions": [{
            "function": "minecraft:set_nbt",
            "tag": "{                   title:\"Book title\",               author:\"Some name\",              pages:[                   '\"text\"'              ]            }"
          }]
        }]
      }]
    };

for (pool of loot.pools) { if (pool.entries) for (entry of pool.entries) { if (entry.functions) for (func of entry.functions) { if (func['function'] === 'minecraft:set_nbt') func.tag = JSON.stringify(eval(`(${func.tag})`)); } } }
copy(loot);

(Replace the loot object literal with the contents of your loot table file.)