Ultimus
- ultim_0
- ultim_0
- Asia/Shanghai
- Yes
- No
MC-171883![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Mojang] Henning Erlandsen](../../../data/avatars/users/79333.png){kind=small}
Under normal circumstances, when you click on a block with a debug stick, the stick will select a block state (left-click) or change the selected block state (right-click), as the wiki describing.
However, what I have been annoyed with is:
With a debug stick on the hand, if right-clicking on a block which is interactive, such as trapdoor (usually wooden), anvil, chest, lever, cake and sign, the debug stick will not work. Instead, the targeted block will be used. This event is preventable by holding the shift key. I think that the bug is of the debug stick itself.
For example, although you have selected the "facing" block state of a chest by left-clicking, right-clicking on the chest opens the chest instead of changing this block state. What's more, right-clicking on a cake decreases the amount of the pieces, but no subtitles were shown, so predicting that the cake is eaten instead of changed with the debug stick.
In order to use debug stick to change the block states of such blocks, you must hold the shift key and then right-click on the block. This means that you can only cycle the block state of such blocks in single (reverse) order.
ADDITION: As far as I am concerned, ""
Under normal circumstances, when you click on a block with a debug stick, the stick will select a block state (left-click) or change the selected block state (right-click), as the wiki describing.
However, what I have been annoyed with is:
With a debug stick on the hand, if right-clicking on a block which is interactive, such as trapdoor (usually wooden), anvil, chest, lever, cake and sign, the debug stick will not work. Instead, the targeted block will be used. This event is preventable by holding the shift key. I think that the bug is of the debug stick itself.
For example, although you have selected the "facing" block state of a chest by left-clicking, right-clicking on the chest opens the chest instead of changing this block state. What's more, right-clicking on a cake decreases the amount of the pieces, but no subtitles were shown, so predicting that the cake is eaten instead of changed with the debug stick.
In order to use debug stick to change the block states of such blocks, you must hold the shift key and then right-click on the block. This means that you can only cycle the block state of such blocks in single (reverse) order.
ADDITION:
As far as I am concerned, ""Under normal circumstances, when you click on a block with a debug stick, the stick will select a block state (left-click) or change the selected block state (right-click), as the wiki describing.
However, what I have been annoyed with is:
With a debug stick on the hand, if right-clicking on a block which is interactive, such as trapdoor (usually wooden), anvil, chest, lever, cake and sign, the debug stick will not work. Instead, the targeted block will be used. This event is preventable by holding the shift key. I think that the bug is of the debug stick itself.
For example, although you have selected the "facing" block state of a chest by left-clicking, right-clicking on the chest opens the chest instead of changing this block state. What's more, right-clicking on a cake decreases the amount of the pieces, but no subtitles were shown, so predicting that the cake is eaten instead of changed with the debug stick.
In order to use debug stick to change the block states of such blocks, you must hold the shift key and then right-click on the block. This means that you can only cycle the block state of such blocks in single (reverse) order.
ADDITION: As far as I am concerned, "any issues resulting of its usage are closed as Won't Fix" because the stick is a tool to decrease or create bugs. But what I have to state is that debug stick cannot produce bugs in this issue.
Under normal circumstances, when you click on a block with a debug stick, the stick will select a block state (left-click) or change the selected block state (right-click), as the wiki describing.
However, what I have been annoyed with is:
With a debug stick on the hand, if right-clicking on a block which is interactive, such as trapdoor (usually wooden), anvil, chest, lever, cake and sign, the debug stick will not work. Instead, the targeted block will be used. This event is preventable by holding the shift key. I think that the bug is of the debug stick itself.
For example, although you have selected the "facing" block state of a chest by left-clicking, right-clicking on the chest opens the chest instead of changing this block state. What's more, right-clicking on a cake decreases the amount of the pieces, but no subtitles were shown, so predicting that the cake is eaten instead of changed with the debug stick.
In order to use debug stick to change the block states of such blocks, you must hold the shift key and then right-click on the block. This means that you can only cycle the block state of such blocks in single (reverse) order.
ADDITION: As far as I am concerned, "any issues resulting of its usage are closed as Won't Fix" because the stick is a tool to decrease or create bugs. But what I have to state is that debug stick cannot produce bugs in this issue. Therefore, I think that the issue is with the stick itself instead of its usage.
The Bug
As you can see, when using Pick Block key on the cauldron filled with powder snow, it returns nothing, neither cauldron nor powder snow bucket.
While playing Minecraft, if Minecraft goes out of memory, it sometimes pops up some text reminding this. However, it is not translated into other languages. The text is even not available in Crowdin as you can see in the
firstscreenshot.The
secondscreenshot was taken in 1.16.2, in which version I set my language as Chinese. I believe that this bug remains in current version.While playing Minecraft, if Minecraft goes out of memory, it sometimes pops up some text reminding this. However, it is not translated into other languages. The text is even not available in Crowdin as you can see in the second screenshot.
The first screenshot was taken in 1.16.2, in which version I set my language as Chinese. I believe that this bug remains in current version.
While playing Minecraft, if Minecraft
goes out of memory, it sometimes pops up sometextreminding this. However, it is not translated into other languages. The text is even not available in Crowdin as you can see in the second screenshot.The first screenshot was taken in 1.16.2, in which version I set my language as Chinese. I believe that this bug
remains in current version.While playing Minecraft, if Minecraft runs out of memory, it sometimes pops up some message reminding this. However, it is not translated into other languages. The text is even not available in Crowdin as you can see in the second screenshot.
The first screenshot was taken in 1.16.2, in which version I set my language as Chinese. I believe that this bug still exists in current version.
"Out of memory!"textkeeps untranslated"Out of memory!" message keeps untranslated
The Bug
While playing Minecraft, if Minecraft runs out of memory, it sometimes pops up some message reminding this. However, it is not translated into other languages. The text is even not available in Crowdin as you can see in the second screenshot.
The first screenshot was taken in 1.16.2, in which version I set my language as Chinese.
I believe thatthisbug still exists in current version.Expected Result
"Out of memory!" message should be translated.
Code analysis
The "Out of memory!" message is hardcoded in the OutOfMemoryScreen class instead of using translatable text. See this comment for a full analysis.
The Bug
While playing Minecraft, if Minecraft runs out of memory, it sometimes pops up some message reminding this. However, it is not translated into other languages. The text is even not available in Crowdin as you can see in the second screenshot.
The first screenshot was taken in 1.16.2, in which version I set my language as Chinese. Actually, the bug still exists in current version.
Expected Result
"Out of memory!" message should be translated.
Code analysis
The "Out of memory!" message is hardcoded in the OutOfMemoryScreen class instead of using translatable text. See this comment for a full analysis.
The Bug
While playing Minecraft, if Minecraft runs out of memory, it sometimes pops up some message reminding this. However, it is not translated into other languages. The text is even not available in Crowdin as you can see in the second screenshot.
The first screenshot was taken in 1.16.2, in which version I set my language as Chinese.
Actually, the bug still exists in current version.Expected Result
"Out of memory!" message should be translated.
Code analysis
The "Out of memory!" message is hardcoded in the OutOfMemoryScreen class instead of using translatable text. See this comment for a full analysis.
The Bug
If you place a block which needs support below (e.g. sand, gravel, anvil, dragon egg and scaffolding) at the altitude Y=1 without supporting below, let it fall just 1 block and land on the altitude Y=0, it turns into an item instead of a block.How to Reproduce
- Create a world in the current snapshot
- Go to the altitude Y=0
- Place such a block at Y=1
- When it lands on Y=0, you will notice that it turns into a dropped item
Falling block placing at Y=1 changes into dropped item when landing on Y=0
Hello! According to the Minecraft Wiki, when using spawn eggs, for each time, there is a possibility of 1/1200 (about 0.083%) to spawn a blue axolotl, so you may be not lucky enough.
Maybe it's an intended feature.
Seems to be a duplicate of
MCPE-137158.Still exists in 1.18-pre5.
Seems to be a duplicate of
MC-238959.Can confirm in 1.18.1
The related strings are available in Crowdin now. THX a lot!
Hey pal, can you provide your seed and coordinate?
Just a placeholder, the function of propagule may be updated in the following snapshots.
Confirmed in 22w16a.
By the way, "Ok" should be "OK". The "K" should be capitalized.
Seems to be a feature request, not a bug.
Related to MC-187125, maybe.
Maybe invalid, because /locate will only search the structures generated in the beginning of your world.
BTW this bug has been existing since 22w11a.
See also MC-187125.
Using the command /place can also result in similar bug. See MC-248248.
Recommend another ruined portal:
*Seed: -2334795469883784838
*Coordinates: 760 -64 2040
By the way this portal generates below a Tiankeng (sinkhole), whose altitude is about -50. This may cause the underground portal to generate weirdly.
confirmed in 1.20.1.
This issue seems to be INVALID since you may be submitting a feature request.
By the way, similar bug was detected in the potato quest of the April Fools snapshot 24w14potato, which is a branch of 24w12a.
Can you provide your screenshot of the command block and its GUI? The configuration of command block might affect its function.