Add CLUEstering 2.12 compatibility - #84
Open
jmcarcell wants to merge 1 commit into
Open
Conversation
jmcarcell
force-pushed
the
fix-cluestering-pointspertile-compatibility
branch
from
September 1, 2026 08:50
de4fe6e to
1545334
Compare
jmcarcell
changed the title
Member
|
Will this be properly detected for a build with CLUE@main? |
Member
Author
|
It doesn't, my idea is to leave it here as a reminder for when |
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
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.
CLUEstering 8dab85381fb30fbbbf9e7d86ec26c5536e4d0ae9 removes the pointsPerTile constructor parameter, with CLUEstering 2.12 as the API boundary whenever it's released.
BEGINRELEASENOTES
ENDRELEASENOTES