chickenshooray
- diamondplayables
- JIRAUSER761719
- Europe/Stockholm
- Yes
- No
MC-264943If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
{{/setblock ~ ~ ~ minecraft:suspicious_sand{item:Unknown macro: {id}}
}}- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!
If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
- /setblock ~ ~ ~ minecraft:suspicious_sand{item:
Unknown macro: {id}}
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!
If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
- /setblock ~ ~ ~ minecraft:suspicious_sand{item:
Unknown macro: {id}}
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!
If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
- /setblock ~ ~ ~ minecraft:suspicious_sand{item:
Unknown macro: {id}}
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
- `/setblock ~ ~ ~ minecraft:suspicious_sand{item:{id:"minecraft:gold_nugget",Count:24b}}`
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!
If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
- `/setblock ~ ~ ~ minecraft:suspicious_sand{item:{id:"minecraft:gold_nugget",Count:24b}}`
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
- /setblock ~ ~ ~ minecraft:suspicious_sand{item:
Unknown macro: {id}}
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!
If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
- /setblock ~ ~ ~ minecraft:suspicious_sand{item:
Unknown macro: {id}}
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
/setblock ~ ~ ~ minecraft:suspicious_sand{item:
Unknown macro: {id}}
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!
If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
/setblock ~ ~ ~ minecraft:suspicious_sand{item:
Unknown macro: {id}}
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!If I brush a fixed Suspicious Block that has 28 items, it should give me 28 items back, but it doesn't. (28 is just an example, but you get the idea)
Steps to reproduce:
- `/setblock ~ ~ ~ minecraft:suspicious_sand{item:{id:"minecraft:gold_nugget",Count:24b}}`
- Brush the block that was just placed down.
- See that the items' stack size isn't 28.
- The number isn't fixed either - you get a different stack size each time you do this.
Extra information:
After further testing, I've seen that the number breaks starting from 24 all the way to 64.
(I got lazy, it could happen for numbers below 24 too, I haven't checked this yet)
Please fix this, I'm making an adventure map that features lots of coins hidden in suspicious sand blocks, and I really wanted the brushed amount to be correct. Thanks!
For some reason, /execute on origin doesn't work when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host.
- Toss a Lingering Splash Potion of any kind.
- Run:
/execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bug- It should work.
- Now, log out and log back in before the Lingering Potion wears off
- Run the command in step 3 again
- It doesn't work anymore, but it should - it's the exact same command, the exact same entity, on the exact same owner.
Note: This can also be done with Arrows/Spectral Arrows/Tridents, the same happens there too. This bug behaviour wears off only when the server restarts itself.
For some reason, /execute on origin doesn't work when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host.
- Toss a Lingering Splash Potion of any kind.
- Run:
/execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bug- It should work.
- Now, log out and log back in before the Lingering Potion wears off
- Run the command in step 3 again
- It doesn't work anymore, but it should - it's the exact same command, the exact same entity, on the exact same owner.
Note: This can also be done with Arrows/Spectral Arrows/Tridents, the same happens there too. This bug behaviour wears off only when the server restarts itself.
For some reason, /execute on origin doesn't work when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host, and the area you're doing this in must be loaded.
- Toss a Lingering Splash Potion of any kind.
- Run:
/execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bug- It should work.
- Now, log out and log back in before the Lingering Potion wears off
- Run the command in step 3 again
- It doesn't work anymore, but it should - it's the exact same command, the exact same entity, on the exact same owner.
Note: This can also be done with Arrows/Spectral Arrows/Tridents, the same happens there too. This bug behaviour wears off only when the server restarts itself.
For some reason, /execute on origin doesn't work when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host,
and the area you're doing this in must be loaded.- Toss a Lingering Splash Potion of any kind.
- Run:
/execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bug- It should work.
- Now, log out and log back in before the Lingering Potion wears off
- Run the command in step 3 again
- It doesn't work anymore, but it should - it's the exact same command, the exact same entity, on the exact same owner.
Note: This can also be done with Arrows/Spectral Arrows/Tridents, the same happens there too. This bug behaviour wears off only when the server restarts itself.
For some reason, /execute on origin doesn't work when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host,
and the area you're doing this in must be loaded.- Toss a Lingering Splash Potion of any kind.
- Run:
/execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bug- It should work.
- Now, log out and log back in before the Lingering Potion wears off
- Run the command in step 3 again
- It doesn't work anymore, but it should - it's the exact same command, the exact same entity, on the exact same owner.
Note: This can also be done with Arrows/Spectral Arrows/Tridents, the same happens there too. This bug behaviour wears off only when the server restarts itself.
For some reason, /execute on origin doesn't work when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host,
and the area you're doing this in must be loaded.- Toss a Lingering Splash Potion of any kind.
- Run:
/execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bug- It should work.
- Now, log out and log back in before the Lingering Potion wears off
- Run the command in step 3 again
- It doesn't work anymore, but it should - it's the exact same command, the exact same entity, on the exact same owner.
Note: This can also be done with Arrows/Spectral Arrows/Tridents, the same happens there too. This bug behaviour wears off only when the server restarts itself.
For some reason, /execute on origin doesn't work when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host,
and the area you're doing this in must be loaded.- Toss a Lingering Splash Potion of any kind.
- Run:
/execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bug- It should work.
- Now, log out and log back in before the Lingering Potion wears off
- Run the command in step 3 again
- It doesn't work anymore, but it should - it's the exact same command, the exact same entity, on the exact same owner.
Note: This bug behaviour wears off only when the server restarts itself.
/execute on origin doesn't workif the player has logged out, then logs back in again./execute on origin doesn't work on Area Effect Cloud if the player owner left and rejoins.
/execute on origin doesn't work on Area Effect Cloudif theplayer owner left and rejoins./execute on origin doesn't work on Area Effect Cloud's player owners that left and rejoins.
/execute on origin doesn't work on Area Effect Cloud's player ownersthat left andrejoins./execute on origin doesn't work on Area Effect Cloud's player owners after rejoining.
For some reason, /execute on origin doesn't work on Area Effect Clouds when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host,
and the area you're doing this in must be loaded.- Toss a Lingering Splash Potion of any kind.
- Run:
/execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bug- It should work.
- Now, log out and log back in before the Lingering Potion wears off
- Run the command in step 3 again
- It doesn't work anymore, but it should - it's the exact same command, the exact same entity, on the exact same owner.
Note: This bug behaviour wears off only when the server restarts itself.
For some reason, /execute on origin doesn't work on Area Effect Clouds when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host,
and the area you're doing this in must be loaded.- Toss a Lingering Splash Potion of any kind.
- Run:
/execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bugItshould work.- Now, log out and log back in
before the Lingering Potion wears off- Run the command in step 3 again
- It doesn't work anymore, but it should - it's the exact same command, the exact same entity, on the exact same owner.
Note: This bug behaviour wears off only when the server restarts itself.
For some reason, /execute on origin doesn't work on Area Effect Clouds when the player has logged out, then logged back in again.
To replicate:
- You must be in a server or a LAN hosted world, but not as the world's host,
and the area you're doing this in must be loaded.- Toss a Lingering Splash Potion of any kind.
- Run: /execute as @e[type=minecraft:area_effect_cloud,sort=nearest,limit=1] on origin run say bug
- This should work as you'd expected it to.
- Now, log out and log back in before the Lingering Potion's cloud disappears
- Run the command in step 3 again
- It doesn't work anymore, but it should, as it's the exact same command, the exact same entity, on the exact same owner.
Note: This bug behaviour wears off only when the server restarts itself.
Previously, setting an entity's CustomName to "" would clear its name entirely.
This is the only method to do this, as /data remove doesn't work on CustomName, at all.
(seeMC-128225for that issue)However, with the recent changes to text parsing, setting an entity's CustomName to "" wouldn't work anymore (it still ran, but as if nothing happened), removing this tool from the system for good. It is now impossible to delete an entity's name.
Please fix this, as this has been a thing for so long before 1.20.3 (and now 1.20.4)'s release.
Previously, setting an entity's CustomName to "" would clear its name entirely.
This is the only method to do this, as /data remove doesn't work on CustomName, at all.
(seeMC-128225for that issue)However, with the recent changes to text parsing, setting an entity's CustomName to "" wouldn't work anymore (it still ran, but as if nothing happened), removing this tool from the system for good. It is now impossible to delete an entity's name.
Please fix this, as this has been a thing for so long before 1.20.3 (and now 1.20.4)'s release.
Demonstration video to demonstrate this
Previously, setting an entity's CustomName to "" would clear its name entirely.
This is the only method to do this, as /data remove doesn't work on CustomName, at all.
(seeMC-128225for that issue)However, with the recent changes to text parsing, setting an entity's CustomName to "" wouldn't work anymore (it still ran, but as if nothing happened), removing this tool from the system for good. It is now impossible to delete an entity's name.
Please fix this, as this has been a thing for so long before 1.20.3 (and now 1.20.4)'s release.
Demonstration video to demonstrate this by
Previously, setting an entity's CustomName to "" would clear its name entirely.
This is the only method to do this, as /data remove doesn't work on CustomName, at all.
(seeMC-128225for that issue)However, with the recent changes to text parsing, setting an entity's CustomName to "" wouldn't work anymore (it still ran, but as if nothing happened), removing this tool from the system for good. It is now impossible to delete an entity's name.
Please fix this, as this has been a thing for so long before 1.20.3 (and now 1.20.4)'s release.
Demonstration video to demonstrate this by
It's now impossible toremove CustomName from entities.Setting CustomName to empty values no longer clears entities' names.
Previously, setting an entity's CustomName to "" would clear its name entirely.
This is the only method to do this, as /data remove doesn't work on CustomName, at all.
(seeMC-128225for that issue)However, with the recent changes to text parsing, setting an entity's CustomName to "" wouldn't work anymore (it still ran, but as if nothing happened), removing this tool from the system for good. It is now impossible to delete an entity's name.
Please fix this, as this has been a thing for so long before 1.20.3 (and now 1.20.4)'s release.
Previously, setting an entity's CustomName to "" would clear its name entirely.
This is the only method to do this, as /data remove doesn't work on CustomName, at all.
(seeMC-128225for that issue)However, with the recent changes to text parsing, setting an entity's CustomName to "" wouldn't work anymore (it still ran, but as if nothing happened), removing this tool from the system for good. It is now impossible to delete an entity's name.
Please fix this, as this has been a thing for so long before 1.20.3 (and now 1.20.4)'s release.
Such a change permanently removes datapack creators' abilities to erase an entity's name, which is crucial for projects that does that very thing, which has been around for a very long time.
Previously, setting an entity's CustomName to "" would clear its name entirely.
This is the only method to do this, as /data remove doesn't work on CustomName, at all.
(seeMC-128225for that issue)However, with the recent changes to text parsing, setting an entity's CustomName to "" wouldn't work anymore (it still ran, but as if nothing happened), removing this tool from the system for good. It is now impossible to delete an entity's name.
Please fix this, as this has been a thing for so long before 1.20.3 (and now 1.20.4)'s release.
Such a change permanently removes datapack creators' abilities to erase an entity's name, which is crucial for projects that does that very thing, which has been around for a very long time.It is now impossible to delete an entity's name.
Previously, setting an entity's CustomName to "" would clear its name entirely.
This is the only method to do this, as /data remove doesn't work on CustomName, at all.
(seeMC-128225for that issue)However, with the recent changes to text parsing, setting an entity's CustomName to "" wouldn't work anymore (it still ran, but as if nothing happened), removing this tool from the system for good. It is now impossible to delete an entity's name.
Please fix this, as this has been a thing for so long before 1.20.3 (and now 1.20.4)'s release.
Such a change permanently removes datapack creators' abilities to erase an entity's name, which is crucial for projects that does that very thing, which has been around for a very long time.
Setting CustomName to empty values no longer clearsentities'names.As of 1.20.3, it is now impossible to delete an entity's name.
From further testing made in
MC-264943it also happens on Suspicious Gravel, the count size has problems from 24 onwards (haven't tested lower amounts yet), the items are randomly distributed for some reason, I can't tell what kind of distribution this thing follows yet, and it's messing with tables that drops Suspicious Blocks with a count more than said amount, since it always creates this kind of data before dropping the item.Tested: Any invalid values would result in the command working as normal, but no effects would happen to the name.
Can I get control of this? It needs to be consistently updated if there's any hope of getting it fixed and/or seen by anyone else. EDIT: Affects 1.20.3 and 1.20.4
This is now a crucial problem I think.
Removing CustomName is now outright impossible to do due to
MC-267259This still exists all the way up to 1.20.5 Prerelease 3.
Still exist in 1.20.5-rc1.
It seems like we won't be able to remove custom names for 2 versions in a row after having been able to in another way since 1.13. Ouch.
Still exists in 1.20.5-rc2.
Sadly, this is still the case in Release 1.20.5.
Still exists in 1.20.6-rc1. Is this even a critical bug?