Ok so I found why...

m1sterX had a widow that got revealed by an ally's weavers, just at the base of the cerb and that's what the tremor was shooting at.

Still, it was on a force fire ground order, but I guess the top of the mountain was too high so the tremor was not in range.

It's one of those cases where the unit is issued a fire order and it automatically stops before going far enough to compensate for the elevation of the target.



Also it looks like I fat fingered fire at will state so it made sense the tremor would target the widow... just not that it stopped while out of range of the force fire target, but that's not new.

Actually, I didn't. I just checked my default states and for some reason tremor is on inherit factory instead of hold fire. I reinstalled recently so I lost my previous settings, but I don't recall having to set tremor to hold fire. I thought that was the default state.

Maybe I changed the default states on my previous install so long ago that I forgot, but I really don't see why I would ever want to leave a tremor on fire at will.

Cyclops sometimes refuses to fire the main gun at a Stinger even if they are both on level ground.
Is this reported on Github?