Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #315; this treats ammo items that produce capture bots as placement items for the captured spawners, and reads the CaptureSpawnerTechnologyTrigger to display its information in the tooltips.
I ended up not reading CaptureRobotPrototype at all; it doesn't contain interesting information about what the capture robot does. The interesting information is the chain of triggers from an ammo item to a projectile entity to a capture bot entity, and also the (non-trigger) chain from the ammo item to the valid targets to the capture result.
I briefly considered trying to tie accessibility of captured spawners to both capture rockets and spawners, but (1) the dependency analyzer doesn't support "... or (A and B)" tests and (2) biter and spitter spawners are always accessible anyway.