Nethonos
- Nethonos
- nethonos
- Europe/Stockholm
- Yes
- No
MC-143209
Low
NormalConfirmed for 18w21a.
Confirmed for 1.13-pre3.
Confirmed for 1.13-pre2.
Confirmed for 1.13-pre1.
Confirmed for 18w22c.
Confirmed for 18w22b.
Confirmed for 18w21b.
2018-06-25_18.21.46.pngYou can spawn a horse with out AI with "/summon minecraft:horse ~ ~ ~ {NoAI:true}" and the horse has no gravity and if you hit it, it will not move.
But if you spawn a passenger on it with this command:
{id:"minecraft:husk",NoAI:true}
/summon minecraft:horse ~ ~ ~ {NoAI:true,Passengers:[]}
The horse will be fall down, if it spawn in the air and if you hit it, it will move in a direction.
This does not happen to all other rideable (with commands) creatures:
{id:"minecraft:husk",NoAI:true}
/summon minecraft:sheep ~ ~ ~ {NoAI:true,Passengers:[]}
{id:"minecraft:husk",NoAI:true}
/summon minecraft:cow ~ ~ ~ {NoAI:true,Passengers:[]}
You can spawn a horse with out AI with "/summon minecraft:horse ~ ~ ~ {NoAI:true}" and the horse has no gravity and if you hit it, it will not move.
But if you spawn a passenger on it with this command:
{id:"minecraft:husk",NoAI:true}
/summon minecraft:horse ~ ~ ~ {NoAI:true,Passengers:[]}
The horse will be fall down, if it spawn in the air and if you hit it, it will move in a direction.
This does not happen to all other rideable (with commands) creatures:
{id:"minecraft:husk",NoAI:true}
/summon minecraft:sheep ~ ~ ~ {NoAI:true,Passengers:[]}
{id:"minecraft:husk",NoAI:true}
/summon minecraft:cow ~ ~ ~ {NoAI:true,Passengers:[]}
Only NoAI-horse with NoAI-passenger does not float and is knocked back in case of damage
You can spawn a horse with out AI with
/summon minecraft:horse ~ ~ ~ {NoAI:true}and the horse has no gravity and if you hit it, it will not move.
But if you spawn a passenger on it with this command:
/summon minecraft:horse ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]}The horse will be falling down, if it spawns in the air and if you hit it, it will move in a direction.
This does not happen to all other rideable (with commands) creatures:
/summon minecraft:sheep ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]} /summon minecraft:cow ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true}]}You can spawn a horse with out AI with
/summon minecraft:horse ~ ~ ~ {NoAI:true}and the horse has no gravity and if you hit it, it will not move.
But if you spawn a passenger on it with this command:
/summon minecraft:horse ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]}The horse will be falling down, if it spawns in the air and if you hit it, it will move in a direction.
This does not happen to all other rideable (with commands) creatures:
/summon minecraft:sheep ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]} /summon minecraft:cow ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]} /summon minecraft:llama ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]} ...
Only NoAI-horse in combination with NoAI-passenger does not float and is knocked back in case of damage
Only NoAI-horse in combination with NoAI-passenger does not float and is knocked back in case of damage
You can spawn a horse with out AI with
/summon minecraft:horse ~ ~ ~ {NoAI:true}and the horse has no gravity and if you hit it, it will not move.
But if you spawn a passenger on it with this command:
/summon minecraft:horse ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]}The horse will be falling down, if it spawns in the air and if you hit it, it will move in a direction.
This does not happen to all other rideable (with commands) creatures:
/summon minecraft:sheep ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]} /summon minecraft:cow ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]} /summon minecraft:llama ~ ~ ~ {NoAI:true,Passengers:[ {id:"minecraft:husk",NoAI:true} ]} ...
Only NoAI-horse in combinationwithNoAI-passengerdoes not float and is knocked back in case of damageAll mobs with passengers float in the air, but not horses with passengers
Cursor from writable book, startsan the first letter instead of the last letter you wroteCursor from writable book, starts on the first letter instead of the last letter you wrote
If you write any text in the writable-book and closed the book and you reopened it. The cursor starts on the first letter / charactor instead of to start from the last charactor.
And if you click "
Strg" and "Ende" (in german)your cursor goes only to the end of line and not to the end of page.If you write any text in the writable-book and closed the book and you reopened it. The cursor starts on the first letter / charactor instead of to start from the last charactor.
And if you click "CTRL" and "END" your cursor goes only to the end of line and not to the end of page.
The bug
When summoning a falling block with another entity as a passenger (that passenger could be another falling block as well), that passenger will be inside of the block once the block lands on the ground. Before 1.14, it used to be ejected on top of the block.
Most noteworthy, this causes falling blocks riding other falling blocks to pop off as items instead of being placed, rendering so-called "one command creations" unusable.
How to reproduce
Run:/summon minecraft:falling_block ~5 ~10 ~ {Time:1,BlockState:{Name:"redstone_block"},Passengers:[{id:"cow"}]}→
The cow will be inside of the block once the block lands
The bug
When summoning a falling block with another entity as a passenger (that passenger could be another falling block as well), that passenger will be inside of the block once the block lands on the ground. Before 1.14, it used to be ejected on top of the block.
Most noteworthy, this causes falling blocks riding other falling blocks to pop off as items instead of being placed, rendering so-called "one command creations" unusable.
How to reproduce
- Example:
/summon minecraft:falling_block ~5 ~10 ~ {Time:1,BlockState:{Name:"minecraft:redstone_block"},Passengers:[{id:"minecraft:cow"}]}→
- Example:
/summon minecraft:falling_block ~5 ~10 ~ {Time:1,Passengers:[{id:"minecraft:falling_block",Time:1,Passengers:[{id:"minecraft:falling_block",Time:1,Passengers:[{id:"minecraft:falling_block",Time:1}]}]}]}→
The bug
When summoning a falling block with another entity as a passenger (that passenger could be another falling block as well), that passenger will be inside of the block once the block lands on the ground. Before 1.14, it used to be ejected on top of the block.
Most noteworthy, this causes falling blocks riding other falling blocks to pop off as items instead of being placed, rendering so-called "one command creations" unusable.
How to reproduce
- Example:
/summon minecraft:falling_block ~5 ~10 ~ {Time:1,BlockState:{Name:"minecraft:redstone_block"},Passengers:[{id:"minecraft:cow"}]}→
- Example:
/summon minecraft:falling_block ~5 ~10 ~ {Time:1,Passengers:[{id:"minecraft:falling_block",Time:1,Passengers:[{id:"minecraft:falling_block",Time:1,Passengers:[{id:"minecraft:falling_block",Time:1}]}]}]}→
The bug
When summoning a falling block with another entity as a passenger (that passenger could be another falling block as well), that passenger will be inside of the block once the block lands on the ground. Before 1.14, it used to be ejected on top of the block.
Most noteworthy, this causes falling blocks riding other falling blocks to pop off as items instead of being placed, rendering so-called "one command creations" unusable.
How to reproduce
1. Example:
/summon minecraft:falling_block ~5 ~10 ~ {Time:1,BlockState:{Name:"minecraft:redstone_block"},Passengers:[{id:"minecraft:cow"}]}→
2. Example:
/summon minecraft:falling_block ~5 ~10 ~ {Time:1,Passengers:[{id:"minecraft:falling_block",Time:1,Passengers:[{id:"minecraft:falling_block",Time:1,Passengers:[{id:"minecraft:falling_block",Time:1}]}]}]}→
@Nethonos, would you like to become the reporter so you can update the affected versions yourself?
Update: the Particle String was found as
particle.invalidOptions
Outdated Version of this Comment:
Credits to Nethonos.
I want to share this Error Message with y'all!
How to reproduce:
Try to use this Command:
/particle minecraft:dust{}
confirmed in 1.13-pre3
And sugar cane, doors and fence gates creates underwater a non waterlogged block
confirmed 1.13-pre4 too
In 1.13-pre5 all ids are fixed, but "eye_of_ender_signal" is yet "eye_of_ender" and not "ender_eye"
Confirmed for 1.13-pre5
Confirmed for 1.13-pre5
confirmed in 1.13-pre6
Confirmed for 1.13-pre6
confirmed in 1.13-pre8
confirmed in 1.13-pre8
confirmed in 1.13-pre8
Confirmed for 18w30a
Confirmed for 18w30b
If I spawn a invisible passenger, the name tag should be visible:
{\"text\":\"NameTag\"}/summon minecraft:villager ~ ~ ~ {CustomNameVisibel:true,CustomName:"
",Passengers:[\{id:"minecraft:armor_stand",Invisible:true}]}
please open for that thing
Confirmed for 19w04b and 1.13.2
@FVbico not in this case. It is the opposite of MC-107849. All NoAI:true-entities float in the air but if you make a horse with passenger the horse does'nt float. That is the bug in this case.
But for the entire Minecraft, you have right, the NoAI shouldn't make NoGravity for entities too.
@Kieran Borovac only horses behave differently. All other makes like llamas make this not.
Confirm 1.14
Confirmed for 1.14
Confirmed for 1.14.1 Pre-Release 1
Confirmed for 1.14.1 Pre-Release 2
Confirmed for 1.14.2 Pre-Release 2
Confirmed for 1.14.2 Pre-Release 3
Confirmed for 1.14.2 Pre-Release 4
Confirmed for 1.15.1
Confirmed for 1.15.2-pre2
Confirmed for 20w06a
Confirmed for 1.15.2 and 20w06a
Confirmed for 20w07a
Confirmed for 1.15.2 and 20w10a
Confirmed for 20w14a
Confirmed 20w14a
Confirmed for 20w15a
Confirmed for 20w15a
Confirmed for 20w16a
Confirmed for 20w20b
Confirmed for 20w22a
Confirmed for 1.16-pre4
Confirmed for 1.16-pre4
@Marcono1234 yes I would like it.
Confirmed for 1.16-pre5
Confirmed for 1.16-pre6
Confirmed for 1.16-pre7
Confirmed for 1.16-pre8
Confirmed for 1.16-rc1
Confirmed for 1.16.1
Confirmed for 20w28a
Confirmed for 1.16.3
Confirmed for 1.16.4-pre2
Confirmed. I can't find the string in Crowdin too.
Can confirm in 21w11a.
Can confirm in 21w11a.
Can confirm in 21w11a.
Can confirm in 21w16a.
Can confirm in 21w16a.
@[Mojang] Adrian Östergard
In earlier versions, you could specify block states with numbers.
Example:
minecraft:stained_glass:11
Here was "11" the metadata (today block state)
And here a old video at 3:54 you can see that meta datas/ block states was a thing:
https://www.youtube.com/watch?v=yoLzUirxNcw
Can confirm in 21w18a.
Can confirm in 21w18a.
Can confirm in 21w19a.
Can confirm in 21w19a.
Can confirm in 21w20a.
Can confirm in 21w20a.
Can't you assign a number to each structure and then use the random function to select one of the numbers and only then create the instance? Why do all instances have to be created already if only one of them is randomly selected?
Can confirm in 1.17 Pre1.
Can confirm in 1.17 Pre1.
Can confirm in 1.17 Pre2.
Can confirm in 1.17 Pre2.
Can confirm in 1.17 Pre3.
Can confirm in 1.17 Pre3.
Can confirm in 1.17 Pre4.
Can confirm in 1.17 Pre4.
Can confirm in 1.17 Pre5.
Can confirm in 1.17 Pre5.
Can confirm in 1.17 RC1.
Can confirm in 1.17 RC1.
Can confirm in 1.17 RC2.
Can confirm in 1.17 RC2.
Can confirm for 1.17.1
Can confirm in 1.18-pre6
Can confirm in 1.18-pre6
Can confirm in 1.18-pre6
Can confirm in 1.18
Can confirm in 1.18
Can confirm in 1.18
Can confirm in 1.18
Can confirm in 23w04a
'/execute store result score @s objective run scoreboard players set @s otherObjective 5'
works like the bug reporter means:
=> objective = 5
=> otherObjective = 5
This bug is fixed in 1.19. Can someone mark it as fixed, please
The bug is still in 1.19.4 and 1.20-pre2
Since 23w42a (1.21) the bug is smaller.
Because the fourth block will drop only randomly not always like the versions before.
Can confirm in 1.20.2 and 23w42a
Can confirm in 1.20.2 and 23w42a
Can confirm in 1.20.4 and 23w51b
Can confirm in 1.20.4
Can confirm in 1.21
I can confirm
Confirmed in 1.21.4