Tobias Auerochs
- Tobi29
- tobi29
- Europe/Berlin
- Yes
- No
MC-65151
Description:
One block (both transparent or not) has backface culling whilst any others
don't. This happens for nether portals and "Xray-blocks" (Glowstone, TNT,
Redstoneblock).Effects:
Nether portal: One block is less transparent than the others
Xray-Blocks: Can't look outside when standing in the blockHow to reprocude: (For a nether portal)
1. Stand inside a lit nether portal (you have to do it before it teleports you!)
2. Place a block (e.g. Torch) somewhere else
3. The portal block, your head was in, will turn less transparent and be
visible, when standing in the center of it.
4. Placing or removing any (nearby) block fixes it as well as reloading (F3+A)Description:
One block (both transparent or not) has no backface culling whilst any others
do. This happens for nether portals and "Xray-blocks" (Glowstone, TNT,
Redstoneblock).Effects:
Nether portal: One block is less transparent than the others
Xray-Blocks: Can't look outside when standing in the blockHow to reprocude: (For a nether portal)
1. Stand inside a lit nether portal (you have to do it before it teleports you!)
2. Place a block (e.g. Torch) somewhere else
3. The portal block, your head was in, will turn less transparent and be
visible, when standing in the center of it.
4. Placing or removing any (nearby) block fixes it as well as reloading (F3+A)
One block has backface culling whilst others don'tOne block has no backface culling whilst others do
Summary:
When using @e selectors to target villagers, that were previously unloaded, it fails to execute and says "That entity cannot be found".
Note: Recently the same issue happened with silverfish, might be affecting all mobs (never happened with other entities though)How to reproduce:
1) Spawn a couple of villagers (e.g. spawn-egg or summon command)
2) Teleport away to unload their chunk
3) Teleport back to them
4) Try targeting them with @e (e.g. /kill @e)
5) It should give the "That entity cannot be found" error for most of them
Mac OS X 10.9.4 (13E28)
Java 1.8.0_11Mac OS X 10.9.4 (13E28)
Java 1.8.0_20
Summary:
When using @e selectors to target villagers, that were previously unloaded, it fails to execute and says "That entity cannot be found".
Note: Recently the same issue happened with silverfish, might be affecting all mobs(never happened with other entities though)How to reproduce:
1) Spawn a couple of villagers (e.g. spawn-egg or summon command)
2) Teleport away to unload their chunk
3) Teleport back to them
4) Try targeting them with @e (e.g. /kill @e)
5) It should give the "That entity cannot be found" error for most of themSummary:
When using @e selectors to target villagers, that were previously unloaded, it fails to execute and says "That entity cannot be found".
Note: Recently the same issue happened with silverfish, might be affecting all mobs(never happened with other entities though)
Note 2: Had this happen with Armor Stands as well, fairly certain that this happens with all entities
Note 3: Having two entities with the same UUID and killing one causes same behaviourHow to reproduce:
1) Spawn a couple of villagers (e.g. spawn-egg or summon command)
2) Teleport away to unload their chunk
3) Teleport back to them
4) Try targeting them with @e (e.g. /kill @e)
5) It should give the "That entity cannot be found" error for most of them
Sorry, I did search, but didn't find this report :/
Forgot to attach crash report...
Summary and description were wrong: One block has no backface culling and all others do.
Was fixed some time ago with the new block models
Note: This probably relates to
MC-54842(don't know if / how i could add that myself)I had this exact issue happen in a world with no villagers at all, only armor stands (and possibly some zombies), so it doesn't seem to be caused only by villagers.
Also, the silverfish case I had myself was with silverfish that had NoAI:1 so that doesn't seem to be the cause either.
Fairly certain it is some issue with entities not being removed properly by an unloading chunk or something.
Yes this VERY MUCH is still present (1.8.3)
This bug is still present in 1.8.3
Probably a duplicate of
MC-65151