MrSquishy
MCPE-25935
Still an issue in 1.2.0.31.
The command
returns the message "Could not replace slot 27, must be a value between 0 and 27."Should say "...must be a value between 0 and 26."
Command:
/replaceitem entity @s slot.inventory 27 stoneIssue: Returns the message "Could not replace slot 27, must be a value between 0 and 27." Should say "...must be a value between 0 and 26."
/replaceitem - wrongsyntaxerror messageforcount/replaceitem - wrong error message when count is out of range
/replaceitem - wrong error message whencountis out of range/replaceitem - wrong error message when slot ID is out of range
Steps to reproduce:
1. Place down any any non-black banner
2. Stand on the banner and run the command:/clone ~ ~ ~ ~ ~ ~ ~ ~ ~13. The banner new banner will appear as a blank, black banner, though middle clicking on the banner will still return the correct item.
Edit: Looks like this also affects colored beds, which always appear as white beds after being cloned.
Steps to reproduce:
1. Place down any any non-black banner
2. Stand on the banner and run the command:/clone ~ ~ ~ ~ ~ ~ ~ ~ ~13. The
bannernew banner will appearas a blank, black banner, though middle clicking on the banner will still return the correct item.Edit: Looks like this also affects colored beds, which always appear as white beds after being cloned.
Steps to reproduce:
1. Place down any any non-black banner
2. Stand on the banner and run the command:/clone ~ ~ ~ ~ ~ ~ ~ ~ ~13. The new banner will appear black, though middle clicking on the banner will still return the correct item.
Edit: Looks like this also affects colored beds, which always appear as white beds after being cloned.
Steps to reproduce:
1. Place down and stand on any bed.
2. Run the command:/clone ~ ~ ~ ~ ~ ~ ~ ~ ~23. Hover your cursor over the bed to see its hitbox outline. The actual hitbox is the correct size, but the outline is huge.
Likely related to MCPE-25195
Steps to reproduce:
1. Place down and stand on any bed.
2. Run the command:/clone ~ ~ ~ ~ ~ ~ ~ ~ ~23. Hover your cursor over the bed to see its hitbox outline. The actual hitbox is the correct size, but the outline is huge.
Likely related to MCPE-25195
Cocoa beans cannot be placed on jungle logs if the log is in another chunk. To reproduce, place a log on the edge of a chunk and try to
placea cocoa bean on each face;placingwill only succeed on faces within the same chunk as the log.Cocoa beans cannot be placed via setblock/clone on jungle logs if the log is in another chunk. To reproduce, place a log on the edge of a chunk and try to setblock a cocoa bean on each face; it will only succeed on faces within the same chunk as the log.
Cocoa beans cannot be placed via setblock/fill/clone on jungle logs if the log is in another chunk. To reproduce, place a log on the edge of a chunk and try to setblock a cocoa bean on each face; it will only succeed on faces within the same chunk as the log.
Cocoa beans can't be placed across chunk borders via setblock/fill/clone
Cocoa beans can't be placed across chunk borders viasetblock/fill/cloneCocoa beans can't be placed across chunk borders via commands
Verification builds: 1.8.0.14 (Beta)
Summary: Inside a function file, using execute @e ~ ~ ~ function <> runs the new function off of the original entity instead of the referenced @e entity.
Use Case: Changing which entity runs a function allows the @s selector to be used, which is significantly more efficient than an @e selector.
Repro Steps:
1. Download the attached behavior pack and equip it on a new world.
2. From the chat line, run the command:
{{}}/function testObserved Results: Both the "test" function and the "test_handoff" function print the player's name (both files use say @s)
Expected Results: The "test" function should say the player's name and the "test_handoff" function should say the armor stand's name, as "test_handoff" is called using the command:
/execute @e[type=armor_stand] ~ ~ ~ function test_handoff
Screenshots/Videos attached: Yes
Notes: Running the following command from the in-game chat line produces the expected result (i.e., returns the armor stand's name):
/execute @e[type=armor_stand] ~ ~ ~ function test_handoff
Verification builds: 1.8.0.14 (Beta)
Summary: Inside a function file, using execute @e ~ ~ ~ function <> runs the new function off of the original entity instead of the referenced @e entity.
Use Case: Changing which entity runs a function allows the @s selector to be used, which is significantly more efficient than an @e selector.
Repro Steps:
1. Download the attached behavior pack and equip it on a new world.
2. From the chat line, run the command:
/function testObserved Results: Both the "test" function and the "test_handoff" function print the player's name (both files use say @s)
Expected Results: The "test" function should say the player's name and the "test_handoff" function should say the armor stand's name, as "test_handoff" is called using the command:
/execute @e[type=armor_stand] ~ ~ ~ function test_handoff
Screenshots/Videos attached: Yes
Notes: Running the following command from the in-game chat line produces the expected result (i.e., returns the armor stand's name):
/execute @e[type=armor_stand] ~ ~ ~ function test_handoffVerification builds: 1.8.0.14 (Beta)
Summary: Inside a function file, using execute @e ~ ~ ~ function <> runs the new function off of the original entity instead of the referenced @e entity.
Use Case: Changing which entity runs a function allows the @s selector to be used, which is significantly more efficient than an @e selector.
Repro Steps:
1. Download the attached behavior pack and equip it on a new world.
2. From the chat line, run the command:
/function testObserved Results: Both the "test" function and the "test_handoff" function print the player's name (both files use say @s)
Expected Results: The "test" function should say the player's name and the "test_handoff" function should say the armor stand's name, as "test_handoff" is called using the command:
/execute @e[type=armor_stand] ~ ~ ~ function test_handoffScreenshots/Videos attached: Yes
Notes: Running the following command from the in-game chat line produces the expected result (i.e., returns the armor stand's name):
/execute @e[type=armor_stand] ~ ~ ~ function test_handoff
Clarified the description - the issue with with using setblock/fill/clone to try and set cocoa across chunk borders. Manually placing via right click works just fine.
This was fixed in R10. The report should be closed out.