Weekly Regular Documentation Revisions 01.05-01.11 - develop #2026
+1,048
−919
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
allow to set display duration for BannerType
…without JPEG compression).
Allow CellSpread.Cylinder and AffectsAir/Ground to affect application of Warhead effects
AutoDeath upon ownership change
…#643 in `Whats-New.md`
allow `Harvester.CanGuardArea` to return harvest mission if there's no valid target around
customize AllowWeaponSelectAgainstWalls per techno & WeaponHelper tweak
Supplement a1be09e
DeathFishAtEase
added
the
No Documentation Needed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For non-urgent documentation modifications, they should now be submitted through this dedicated Pull Request and will undergo weekly batch merging.
Documentation changes associated with other feature/bugfix pull requests should remain within their respective Pull Requests.
For example: If a Pull Request gets merged into the main branch without completing required documentation updates, the content should first be synchronized to this dedicated documentation branch. Subsequent corrections will then be made within this dedicated documentation Pull Request.