Paul Winstanley
Assigned
Reported
Comments
It may have been a lag issue. There were some weird things going on with
entities.
On Wednesday, 5 November 2014, qmagnet (JIRA) <[email protected]> wrote:
> qmagnet
> <https://bugs.mojang.com/secure/ViewProfile.jspa?name=qmagnet> commented
> on an issue Re: Baby villagers walking through barrier blocks
> <https://bugs.mojang.com/browse/MC-66613>
>
> Cannot reproduce.
> [image: Add Comment]
> <https://bugs.mojang.com/browse/MC-66613#add-comment> Add Comment
> <https://bugs.mojang.com/browse/MC-66613#add-comment>
> Minecraft <https://bugs.mojang.com/browse/MC> / [image: Bug]
> <https://bugs.mojang.com/browse/MC-66613> MC-66613
> <https://bugs.mojang.com/browse/MC-66613> Baby villagers walking
> through barrier blocks <https://bugs.mojang.com/browse/MC-66613>
> I was working on my adventure map and I had some villager children in a
> house. There were just holes for windows, so I put barrier blocks in after
> seeing them escape. Later, I saw one of the children standing the block
> where one of the barriers was. I thought I might have not put a block
> there, but I checked and the hitbox was there. I don't know if this ...
> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) [image:
> Atlassian logo]
>
/summon Villager ~ ~ ~
{Invulnerable:1,PersistenceRequired:1,CustomName:Hati,CustomNameVisible:1,Profession:3,Offers:{Recipes:[]},Age:-200}
On Friday, 31 October 2014, Marcono1234 (JIRA) <[email protected]> wrote:
> Marcono1234
> <https://bugs.mojang.com/secure/ViewProfile.jspa?name=marcono1234>
> commented on an issue Re: Baby villagers walking through
> barrier blocks <https://bugs.mojang.com/browse/MC-66613>
>
> Could you please add the exact command you used
> [image: Add Comment]
> <https://bugs.mojang.com/browse/MC-66613#add-comment> Add Comment
> <https://bugs.mojang.com/browse/MC-66613#add-comment>
> Minecraft <https://bugs.mojang.com/browse/MC> / [image: Bug]
> <https://bugs.mojang.com/browse/MC-66613> MC-66613
> <https://bugs.mojang.com/browse/MC-66613> Baby villagers walking
> through barrier blocks <https://bugs.mojang.com/browse/MC-66613>
> I was working on my adventure map and I had some villager children in a
> house. There were just holes for windows, so I put barrier blocks in after
> seeing them escape. Later, I saw one of the children standing the block
> where one of the barriers was. I thought I might have not put a block
> there, but I checked and the hitbox was there. I don't know if this ...
> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) [image:
> Atlassian logo]
>
Using /setblock destroy also breaks the rails, so it doesn't work.
No because it was a specific one with a name and lots of NBT data.
It seems that it has been fixed since the snapshot when this happened
On Monday, 22 December 2014, [Mod] Galaxy_2Alex (JIRA) <[email protected]>
wrote:
> [Mod] Galaxy_2Alex
> <https://bugs.mojang.com/secure/ViewProfile.jspa?name=galaxy_2alex>
> resolved an issue as Awaiting Response
>
> Is this still a concern in the current Minecraft version? If so, please *update
> the affected versions* in order to best aid Mojang ensuring bugs are
> still valid in the latest releases/pre-releases. If this has been done, we
> can reopen the issue.
>
> Keep in mind that the "Resolved"-Status on this ticket just means
> "Answered", and that we are waiting for further information on whether this
> issue still exists or not. We will reopen it as soon as the requested
> information has been delivered.
> Minecraft <https://bugs.mojang.com/browse/MC> / [image: Bug]
> <https://bugs.mojang.com/browse/MC-66613> MC-66613
> <https://bugs.mojang.com/browse/MC-66613> Baby villagers walking
> through barrier blocks <https://bugs.mojang.com/browse/MC-66613> Change
> By: [Mod] Galaxy_2Alex
> <https://bugs.mojang.com/secure/ViewProfile.jspa?name=galaxy_2alex>
> Resolution: Awaiting Response Status: Open Resolved [image:
> Add Comment] <https://bugs.mojang.com/browse/MC-66613#add-comment> Add
> Comment <https://bugs.mojang.com/browse/MC-66613#add-comment>
> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) [image:
> Atlassian logo]
>