Units currently appear to "miss" targets that enter their LoS right now. The cause is rP24217: range queries now return units farther away, and those units might actually be out of range if distance is computed center-to-center, which both UnitAI and LOS do. This means that code relying on range query updates is possibly broken, and indeed units miss things (see ticket).
I would like to update UnitAI to calculate distance properly but can't: LOS remains problematic for now (see D3083)
This simply introduces an optional revert of rP24217, by allowing queries to ignore sizes, like they did before. It fixes UnitAI queries.
I also use this for Build Restrictions and Auras, where the new feature was doubtful (mostly because if affects structures, which can have different sizes, and this harms readability of the templates for balancing purposes).
This therefore reverts rP24643, rP24349 (with the exception of the iber monument footprint), and the template changes in rP24217 itself.
It also reduces alertRaiser ranges slightly, this was missed in the original diff.
NB: this very much does not reopen #3381. In fact, buildings will see entities much earlier than entities see buildings, because the former account for their own size while the latter don't. I don't think it's a huge deal for balancing purposes, it shouldn't change much for raiding.
MAYBE we want to bump stonethrower range a little (they sit at 80).
Reported by: Freagarach