Scale down letterFrequencies for fewer tiles. #5
Conversation
This file contains 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
Using a pool of 144 letters can lead to a mix of pulled letters that has an odd mix. For example, since there could always be 3 "V"s in the bag, a short game drawing 36 tiles could draw all 3. Arguably, for a 36 tile game, there should only be one V. calculateFrequencies() isn't perfect as the new frequencies are calculated by division and floats get messy. For a 36 tile game, 46 tiles wind up in the bag.
|
Thanks for this game! I find the mix of pulled letters can be quite irritating sometimes. This should level the playing field a bit. |
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.
Using a pool of 144 letters can lead to a mix of pulled letters that has an odd mix.
For example, since there could always be 3 "V"s in the bag, a short game drawing 36
tiles could draw all 3. Arguably, for a 36 tile game, there should only be one V.
calculateFrequencies() isn't perfect as the new frequencies are calculated by division
and floats get messy. For a 36 tile game, 46 tiles wind up in the bag.