Lemon Lord
- LegendarySunburn
- legendarysunburn
- Europe/Stockholm
- Yes
- No
MC-159750![[Mojang] Bartosz Bok](../../../data/avatars/users/10122.svg){kind=small}
When creating a new scoreboard objective, it's possible for 'dummy' to neither show up in the criteria options or function as a valid scoreboard criterion. This bug does not affect objectives made prior to loading up the world, as they will stay in the world's data/scoreboard.dat file with 'dummy' still set as their criteria. This does affect datapacks greatly, as whenever the issue arises (which is occasional), datapacks are unable to recognise any functions with a /scoreboard objectives add <name> dummy command in them.
Unchanged log file is attached as requested. I only noticed the issue about 30min into play.
Title says it all. There is no longer any ability to use the `fish` option in the `/loot` command. Whilst it was never a very useful feature, as it stands, it's just a completely non-functional feature within the game. I took some screenshots at various levels of user-support. The command used for each was various spins on:
/loot give @s fish minecraft:gameplay/fishing/treasure ~ ~ ~ mainhand
Various levels of user support for each screenshot:
- Running the command as is.
- Running the command whilst holding a fishing rod.
- Changing the coordinates of the command to be the top (also tested a block above the top) of a 5x4x5 pool of water.
Each of these resulted in the red "An unexpected error occurred trying to execute that command" message. My theory is that the changes to how fishing works as of 20w12a accidentally disabled this functionality and given how very rarely people use it, it wasn't noticed until now.
As per the first commenter's suggestion, I tried this in a river and then in an ocean and noticed absolutely no change.
Title says it all. There is no longer any ability to use the `fish` option in the `/loot` command. Whilst it was never a very useful feature, as it stands, it's just a completely non-functional feature within the game. I took some screenshots at various levels of user-support. The command used for each was various spins on:
/loot give @s fish minecraft:gameplay/fishing/treasure ~ ~ ~ mainhand
Various levels of user support for each screenshot:
- Running the command as is.
- Running the command whilst holding a fishing rod.
- Changing the coordinates of the command to be the top (also tested a block above the top) of a 5x4x5 pool of water.
Each of these resulted in the red "An unexpected error occurred trying to execute that command" message. My theory is that the changes to how fishing works as of 20w12a accidentally disabled this functionality and given how very rarely people use it, it wasn't noticed until now.
As per the first commenter's suggestion, I tried this in a river and then in an ocean
and noticedabsolutely no change.Title says it all. There is no longer any ability to use the `fish` option in the `/loot` command. Whilst it was never a very useful feature, as it stands, it's just a completely non-functional feature within the game. I took some screenshots at various levels of user-support. The command used for each was various spins on:
/loot give @s fish minecraft:gameplay/fishing/treasure ~ ~ ~ mainhand
Various levels of user support for each screenshot:
- Running the command as is.
- Running the command whilst holding a fishing rod.
- Changing the coordinates of the command to be the top (also tested a block above the top) of a 5x4x5 pool of water.
Each of these resulted in the red "An unexpected error occurred trying to execute that command" message. My theory is that the changes to how fishing works as of 20w12a accidentally disabled this functionality and given how very rarely people use it, it wasn't noticed until now.
As per the first commenter's suggestion, I tried this in a river and then in an ocean with absolutely no change.
Description of bug:
I have 5 identical advancements with 5 advancement rewards-functions that print which advancement was received.
Theadvancementistriggered when I hit the zombie. The advancement order is seemingly shuffled upon every /reload.
You can find the data pack I used for this attached below if you'd like to replicate it yourself.
Steps to reproduce:
- Install data pack in worldsave's datapacks folder.
- Type /reload
- Hit any mob
- Type /reload
- Hit any mob
- Look for the order in chat
Expected result:
I would expect them to execute either in the lexicographical order of their filenames (i.e. 1.json and it's function first, 2.json and it's function second) or order of their 'date last modified'. For this example, I made sure those are the same. Even the rewards-functions are ordered alphabetically by name and by 'date last modified'.
Actual result:
For all intents and purposes random.
Description of the bug:
I have 5 identical advancements with 5 advancement rewards-functions that print which advancement was received. All advancements are triggered when I hit the zombie. The advancement order is seemingly shuffled upon every /reload.
You can find the data pack I used for this attached below if you'd like to replicate it yourself.
Steps to reproduce:
- Install data pack in worldsave's datapacks folder.
- Type /reload
- Hit any mob
- Type /reload
- Hit any mob
- Look for the order in chat
Expected result:
I would expect them to execute either in the lexicographical order of their filenames (i.e. 1.json and it's function first, 2.json and it's function second) or order of their 'date last modified'. For this example, I made sure those are the same. Even the rewards-functions are ordered alphabetically by name and by 'date last modified'.
Actual result:
For all intents and purposes random.
lllll.zip
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
Lemon Lord at also applies the target's rotation and dimension to the context (as opposed to positioned as), so rotated as shouldn't change anything.
Still affects Release 1.15.1
Can confirm for 1.15.1 when in a repeating function but a simple solution is to only update it's rotation once every 2 ticks instead of once per tick. Has something to do with its visual updating getting pushed back one tick whenever it changes rotation. This is why when you /tp something a short distance, you can see it visibly move rather than just vanish from one spot and reappear in another one in the next frame. Rotation interpolation is what is causing this effect, logging out and back in will fix it too but that's hardly a solution.
Edit 12/1/20 7:48pm +1000:
My solution does not actually work, I have noted the problem to persist for more than 20 seconds at a time instead of a handful of ticks.
Edit like idk 2h later:
Have noticed that the ticket maker's command actually wouldn't work. The command that would be expected to work would be:
not what they said. I'll make a new ticket for my issue.
DrownedZombie, what do you mean they don't "visually display their ... animations"? Is it not a bug that the animation is not displayed?
I should clarify that this issue was not present in the more recent snapshots but I'm yet to test for the 20w13's.
@Marcono1234, yes you might be right. I'm so far unable to tell what the proper format is for this, Mr Bok has not given an example of something that would work. It seems this is a duplicate of
MC-177085though.Confirmed for 20w14a, neither teleportation nor Motion NBT editing function.
Can we get a higher Mojang priority? This is getting kinda ridiculous and pardon me if I'm overestimating the talented legends over at Mojang but this seems like a relatively easy fix.
Aye, thanks @Marcono1234, wasn't sure where to submit feedback like this. The actual feedback website is a little confusing and doesn't work how I would have thought. Survey was just what was needed though.
Hahahaha how was this considered to be 'important' priority? Ah well, I won't object to Mojang's Bug Exterminators doing what they do best.
Haha, alright, if you say so, Mr Orr.
Still confirmed in 1.16-pre2.
I can confirm that in 20w27a, I can no longer reproduce this issue. Tried a couple of things but this was by no means a complete examination. Not sure how @Sir Flossup is unable to play the game, I figure they might have messed with the '/attribute' command rather than health boost.