Skip to content

Conversation

Garanas
Copy link
Member

@Garanas Garanas commented Oct 14, 2025

Description of the proposed changes

Through the discussion in #6939 I noticed that a lot of relevant information surrounding this blueprint value is lost. With these annotations I hope to prevent this loss of information for the foreseeable future.

Checklist

  • Changes are annotated, including comments where useful

@github-actions github-actions bot marked this pull request as draft October 14, 2025 05:25
@Garanas Garanas marked this pull request as ready for review October 14, 2025 05:26
--- maximum range from the guarded unit before initiating return
---@field GuardReturnRadius number
--- guard range for the unit, automatically added if absent
--- Guard scan range for the unit. The guard scan radius is used by attack move and patrol orders. Through this scanning mechanic the patrolling (or attack moving) unit can find a target to chase. The scanning behavior includes neutral units.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There could be another line mentioning how it is automatically set in blueprint loading to reasonable values based on the unit's weapon ranges with a limit based on tech tier.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Processed in 316acaf

@Garanas Garanas merged commit 5a049b3 into develop Oct 16, 2025
3 checks passed
@Garanas Garanas deleted the annotate/guard-scan-radius branch October 16, 2025 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants