Per uploaded file sharedsensor.diff (11.9 KiB)

Buginator commented

Will this only be used for locked teams?

Also, if this fails: ASSERT(object != NULL, "Invalid pointer");
We will crash in a release build. Perhaps change that to ASSERT_OR_RETURN?

Oh, and you might want to add a assert check to make sure player is in range?

Per changed status from new to accepted

Per changed owner from `` to Per

Per commented

Why only for locked teams? I'm not sure about changing all asserts to assert_or_return - sometimes the extra conditional is not really worth it, but I'll look into this one.

Per commented

New version of the patch. It fixes a few bugs, and generalizes the code to be utilized also for droids. Currently this support for droids has little effect, however, due to a number of bugs in the action code that I do not want to fix in this patch.

It works the other way, though. You can take a sensor droid for a walk, point at interesting enemy structures, and sit back to watch the archangel missile battery fireworks.

Per uploaded file sharedsensor2b.diff (19.1 KiB)

Per uploaded file sharedsensor2c.diff (19.1 KiB)

Fixed a bug that showed up during mission testing.

Per set resolution to fixed

Per changed status from accepted to closed

Per commented

(In [7765]) Add the ability of allied players to share each others' sensors. Since iterating over all structures
by all players to see if we could use each as a sensor would be rather time consuming, I created a
new set of lists (currently with only one member) that sorts objects by function. This way we can
very quickly iterate over all sensors, even when there are several hundred buildings on the map.
Closes #636.