Overlapping trigger areas has problems

Issue occurs because certain functions that read by the individual object ID (or a single effect for the pixel) ignore anything beyond the first thing they find.

Needed fix: Rework handling of trigger areas so that as far as possible they work on a "does a <type> trigger exist on pixel X, Y" rather than "is the first object found at pixel X, Y an object of <type>"?