[MC-54842] @e selector cannot find villagers in "old" 1.7.x worlds

Using the command /testfor @e[type=Villager,r=10] results 10 lines saying 'That entity cannot be found' when there are clearly 10 villagers in front of me. See the image below.

I expect the command return 10 lines saying 'Found Villager'.

Linked issues

relates to 2

MC-55654 Mobs transported from Nether to Overworld cannot be identified through commands Resolved

MC-65151 Selecting entities (mobs, villagers, armor stands, etc) using @e unreliable Resolved

Attachments

Comments 17

kumasasa 2014-05-08T20:18:01Z

Cannot confirm, see screenshots.

Michael Turner 2014-05-08T20:43:41Z

Thus far I have been unable to duplicate this in a single player world.

Michael Turner 2014-05-08T20:56:31Z

One villager is found after successful breeding. See screenshot.

Relogging causes the found villager to be lost and return 'That entity cannot be found' like the others.

kumasasa 2014-05-08T20:59:11Z

Is that an old world (e.g. from 1.7.x) ?

Michael Turner 2014-05-08T20:59:37Z

Yes

7 more comments

Michael Turner 2014-08-11T05:07:39Z

Still happening. New image added from 14w32d.

galaxy_2alex 2014-10-31T21:23:09Z

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.

Tobias Auerochs 2015-02-22T03:15:39Z

Yes this VERY MUCH is still present (1.8.3)

bob 2015-11-16T08:07:30Z

Still in 1.9 snapshots?

user-f2760 2017-02-14T15:10:28Z

Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.