My reading of the code suggests that there are two separate boxes in play: a bounding box (indicating the size extents of the entity) and a collision box (indicating the boundary where a collision should be applied). In common usage, the two are the same. For my code, they are not the same.
noClip is a property of an entity, indicating that collisions shouldn't be applied to this entity. canCollide and canPush are similar (but subtly different) indicators. To my thinking, setting noClip on an entity should allow it to pass through any other entity or block, regardless of the other entity's noClip setting, and this is not the behavior I'm seeing.
The code reference I cited checks bounding boxes and then collision boxes, without checking any of the flags. It may be more proper to not check the bounding box at all, but this is in a utility function that is checking for intersecting boxes, which may be used elsewhere for purposes other than determining whether or not there was a collision. Checking noClip when iterating through the bounding boxes fixed my fringe case, but I don't know if it broke anything else.
The dragon is an entity and uses noClip, but collision detection is "lazy" in that 1) you can't push it, 2) it's handled as a square cube (head to tail distance is nominally the same as wingspan), and 3) you're not going to get close enough to notice the discrepancy – but if the dragon were to stay still, you would not be able to stand directly in front of or behind the wing because the bounding box would keep you from approaching any closer.
MC-928
Fixed in 1.4.5
I don't understand your question.
My reading of the code suggests that there are two separate boxes in play: a bounding box (indicating the size extents of the entity) and a collision box (indicating the boundary where a collision should be applied). In common usage, the two are the same. For my code, they are not the same.
noClip is a property of an entity, indicating that collisions shouldn't be applied to this entity. canCollide and canPush are similar (but subtly different) indicators. To my thinking, setting noClip on an entity should allow it to pass through any other entity or block, regardless of the other entity's noClip setting, and this is not the behavior I'm seeing.
The code reference I cited checks bounding boxes and then collision boxes, without checking any of the flags. It may be more proper to not check the bounding box at all, but this is in a utility function that is checking for intersecting boxes, which may be used elsewhere for purposes other than determining whether or not there was a collision. Checking noClip when iterating through the bounding boxes fixed my fringe case, but I don't know if it broke anything else.
The dragon is an entity and uses noClip, but collision detection is "lazy" in that 1) you can't push it, 2) it's handled as a square cube (head to tail distance is nominally the same as wingspan), and 3) you're not going to get close enough to notice the discrepancy – but if the dragon were to stay still, you would not be able to stand directly in front of or behind the wing because the bounding box would keep you from approaching any closer.
Still a problem in 1.4.7 ... catching up on changes in Forge for 1.5.1, will update after testing.
Verified, still a problem in 1.5.1
Work-around now @ line 1695:
if (axisalignedbb1 != null && !((Entity)list.get(j2)).noClip && axisalignedbb1.intersectsWith(par2AxisAlignedBB))