Apply designer's Crosshairs turbulence rule; add spread-cloud setups - #489
Merged
Perlkonig merged 1 commit intoSep 26, 2026
Conversation
Turbulence now follows mrraow's clarified rule: after a manoeuvre's own movement and height change, the plane loses one height if it moved from a non-cloud hex into a cloud hex along the way, crashing if already at 0. Flying within a cloud bank costs nothing, placing a new plane is never penalised, and each swoop in a dive is resolved separately. This drops the optional fourth PlaneInfo field used by the earlier exemption. Clouds render darker when Turbulence is active, standing in for a storm-cloud glyph, and the 2026 rules PDF is linked. Two experimental setup variants, symmetric and asymmetric spread clouds, place clouds with the designer's coverage-first algorithm, which blocks open lines of fire before filling gaps. A symmetric board with a centre cloud ends one short of the target, as the designer intends. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BK3bL3XekxLsqgRWgYBv7W
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Turbulence now follows mrraow's clarified rule: after a manoeuvre's own movement and height change, the plane loses one height if it moved from a non-cloud hex into a cloud hex along the way, crashing if already at 0. Flying within a cloud bank costs nothing, placing a new plane is never penalised, and each swoop in a dive is resolved separately. This drops the optional fourth PlaneInfo field used by the earlier exemption.
Clouds render darker when Turbulence is active, standing in for a storm-cloud glyph, and the 2026 rules PDF is linked.
Also two other random algorithms for evaluation, especially by mrraow. They're marked experimental.