mojira.dev

chokoboy3

Assigned

No issues.

Reported

MC-270964 Race condition in can_break/can_place_on item stack components Fixed MC-250644 Linux/GNU: Custom keyboard layout options are ignored since 22w16a Community Consensus MC-242546 When optimizing 1.17 world in 1.18, old "Level" Compound is not deleted, resulting in increased world size Fixed MC-241942 Custom biomes are removed from existing chunks when upgrading to 1.18 from 1.17 Works As Intended MC-230625 /forceload doesn't load entities instantly anymore Duplicate MC-172496 /clear doesn't clear items in blocks like crafting tables Invalid MC-153463 Teleporting into a block in unloaded chunks causes the player to go through the block below Awaiting Response MC-131346 It's possible to place buckets of water, lava or fish in adventure mode Fixed MC-130770 Crash when there's an empty string in an item name Duplicate MC-130418 Leaves are not updated to the new block arguments when updating Duplicate MC-124129 Hovering over a player name shows "Type: minecraft:player" Works As Intended MC-124092 Some team options don't work Fixed MC-124091 Team color doesn't affect name above head Fixed MC-123778 Team color doesn't work in playerlist and sidebar before reconnecting Fixed MC-123672 Barrier blocks affect sunlight Fixed MC-123541 Non-op players can see block tags in F3 Works As Intended MC-123366 Item right click actions don't work whilst looking at a block in adventure mode Fixed MC-123331 'execute if/unless score' sets the score to 0 if unset Fixed MC-123116 teleport rotations are reversed Duplicate MC-122981 Death by projectile crashes server Duplicate

Comments

Can confirm this. Additionally, if you have a scoreboard.dat file with more than 500K entries in PlayerScores, the server will freeze for several seconds trying to save the file

Can confirm in 1.20.4

Can confirm

I can confirm this. In earlier versions, if you spawn a falling block with Time:0 every tick, it would appear as a single falling block which you were able to move by spawning it at different positions. Now, due to the flicker, this is no longer the case.
One solution could be to set Time to -1:

/summon minecraft:falling_block ~ ~ ~ {NoGravity:1,Time:-1}

This however will not look as smooth as it did in 1.16 and below and seemingly two falling blocks are sometimes present at the same time when moving the block (Like the flicker with Time set to 0, just offset by 1 tick and harder to notice)

It seems that the issue is that while the server respects world borders in multiple dimensions, the client only recognizes the world border in the overworld even when in another dimension. This means that visually, the world border is always in the position that it is in in the overworld.

If the overworld has a larger world border than the dimension that you are in, you will start taking damage at random and blocks will reappear as you break them, as the server recognizes that you have moved outside the world border but the client allows you to move.

If the overworld has a smaller world border than the dimension that you are in, it just seems like the dimensions have the same world border since the client prevents you from going outside even though it should be entirely possible. If you teleport outside of the world border, you will not take damage in this situation.

Also, it seems that the world border is reset server-side in other dimensions after reopening the world

Can confirm for 20w21a.

It seems that the painting for the most part isn't killed, it's just made invisible. Though sometimes it is killed and drops as an item.

I did a test with all the possible painting types:

[media]

Ran the command: 

/execute as @e[type=painting] run data merge entity @s {Invulnerable:1b}
[media]

It seems 1x1 paintings are the only ones that survive, though one of them was killed. I then did another test to see if 1x1 paintings would always survive:

[media]

Ran the command: 

/execute as @e[type=painting] run data merge entity @s {Invulnerable:1b}
[media]

It seems that rarely 1x1 paintings are also turned invisible / killed.

Making an arrow with very high damage will crash the game when hitting a player. This can be used by any player with creative by getting this item and placing it above themselves:
give @s chicken_spawn_egg{EntityTag:{id:"minecraft:arrow",damage:1e100d,pickup:1,crit:1}}
I believe this to be a serious issue allowing players with creative to crash any Minecraft server

This is not fixed for crafting tables, anvils, enchanting tables, looms, grindstones or cartography tables where the items are technically still in the player's inventory.

As this might be seen as a separate issue, I've created a separate bug report for it: MC-172496

It seems that now (1.15-pre1) a slow connection is necessary for it to occur regularly, though It's still possible in singleplayer but happens very rarely.

This is still a problem in 1.15 pre 1

Confirmed for 1.14.3

Confirmed for 1.14.2 and 1.14.3 pre-2

Affects 1.14

I believe this is a duplicate of MC-138053

Confirmed for 19w12a

Works as intended
Command blocks execute their commands from the middle of the block. dx, dy and dz aren't floored to an integer position anymore. So a command run at 5.5 50 5.5 with dx=2,dy=2,dz=2, will target the area 5.5,50.5,5.5 to 7.5,52,7.5

To fix this, you'll have to use /execute align xyz

This is partly fixed in 1.13-pre2. The only problem is that the outline of the block, you're looking at, doesn't appear.

persistent is set to false after restarting the world. Not just when updating.

Indeed I have. I'll enable it again and try to update from a backup.

Actually, no matter what arguments the leaves had in 18w21b, they will automatically be set to persistent=false. So even if you placed the block by hand, it'll disappear. Is this intended behaviour?