Another quirky bit of behavior from the 'OR' blocks...
'OR' blocks fail to fire when they have both an overlap and NOT overlap condition.
Jesus is NOT overlapping the straight and narrow path (inverse overlap)
Jesus is overlapping a Krull blade (ouch)
In this case I'd want Jesus to eat it if he is matching either one of those conditions. In r87, the block fails to fire for either event.
The attached capx demonstrates this bug and also validates that this logic works just fine when the 'OR' block is separated out into individual events.
Exmample .capx file