mojira.dev

tholleman

Assigned

No issues.

Reported

MC-276782 Duplicate entries in a tag does not impact the weight Invalid MC-272206 ~ matcher for components will match too much Invalid MC-271628 Enchantment effect "projectile_spawned" doesn't trigger for fishing rods and tridents Fixed MC-271627 Specific enchantment predicate will match with any enchantment Invalid MC-271604 Soul speed becomes active while falling Duplicate MC-270950 Endermen can jump-step out of cobwebs Confirmed MC-270930 Mobs will visually keep armor and weapons after removing them Community Consensus MC-270842 Scores are not kept when a mob converts to another mob Confirmed MC-270679 Clicking on text with run_command can cause EncoderException and will exit to multiplayer menu Fixed MC-270041 Component predicate for lodestone_tracker requires pos Invalid MCL-23634 Starting minecraft shows "waiting on install" Invalid MC-263516 The levels condition for the trigger enchanted_item is outdated Invalid MC-261951 Dragon/piglin head does not move when placed on a jukebox that is playing a record Fixed MC-259247 The execute on owner sub-command does not select the owner of a horse, donkey, llama, or mule Fixed MC-252388 Grindstone gives infinite xp for cursed books Cannot Reproduce MCL-20191 No patch notes for 21w44a Fixed MCL-19649 Fullscreen option reverts in .conf files Fixed

Comments

Was this supposed to be marked as invalid? "Working as intended" or "Won't fix" would make more sense.

Thanks for pointing it out. The function directory was plural.

I've confirmed the issue to still be in 1.21 Pre-Release 2

Cool, thanks

Thanks, I've gotten too used to seeing warnings in the log when something goes wrong

Saw this happen today in 1.20.6

This is unexpected behavior due to a problem in the game's code. This is a perfectly valid bug.

You can read more about what counts as a valid bug here

Still an issue in 1.20.5

I commented this in MC-269642 but probably should have made a separate report. 

I worked around it with a function that returns 1 or 0 based on the player data. I then used execute if function which was fine for my needs. That solution wouldn't work if you want to do this check in a json file

The issue is that the predicate tests with component instead of predicates as mentioned in MC-270707. There is no predicate for a lodestone_tracker but that probably makes this a feature request.

I guess the resolution should now be "fixed" since (+NBT) has been removed

The same will happen to custom stack sized knowledge books.

/give @s minecraft:knowledge_book[minecraft:recipes=["minecraft:acacia_boat"],minecraft:max_stack_size=64] 64

Using the knowledge book in survival will consume the entire stack instead of just one.

Is this still a bug considering the mob attack reach changes in 23w33a?

It's been a while and this is still unresolved. For anyone who's also experiencing this issue, you can set the files to read-only as a temporary workaround.

cd ~/.minecraft
sed -i 's/"fullscreen" : false/"fullscreen" : true/' window_settings_launcher.conf window_settings_log.conf
chmod 444 window_settings_launcher.conf window_settings_log.conf

I recommend following this issue if you're gonna do this. Changing the file rights back after this issue is fixed could help avoid issues in the future.

This also happens with markers which is even weirder since markers riding entities worked perfectly before this snapshot.

Seems it's still pending approval. Just wait a day. I might post an update here once it gets approved as well

Let's not start a discussion in these comments. Moesh has said this should be a feature request so I made one here I hope everyone who wants to see it added will vote for this feature.

That's odd, I just restarted minecraft and now I can't reproduce it. Same 2 worlds I tried it in. I still have the xp I gained though.

Yes, the issue still persists in version Linux 5.13.0-30-generic 2.2.11106 on Ubuntu 20.04.4 LTS

Here are the steps to reproduce as shown in the video:

  1. change fullscreen to true in window_settings_launcher.conf

  2. open the Minecraft launcher, it will start in fullscreen

  3. close the Minecraft launcher, do not resize the window

  4. window_settings_launcher.conf is now back the default. Opening the Minecraft launcher again will no longer start it in fullscreen.

I should add that the video is edited to speed up the loading time. There is no bug with the animation.

The issue described in MCL-14797 is not the same. The issues are with different files. However, it is possible that the underlying cause is the same.