Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make token selection sensitive to the score type selected #2

Open
privong opened this issue Feb 4, 2018 · 2 comments
Open

Make token selection sensitive to the score type selected #2

privong opened this issue Feb 4, 2018 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@privong
Copy link
Owner

privong commented Feb 4, 2018

For example, abbotts cannot score roads. So if roads are selected as an option, don't show the abbot as a token choice.
This will require some re-working or enhancement of the underlying database.

@privong privong added the enhancement New feature or request label Feb 4, 2018
@privong privong self-assigned this Nov 18, 2018
@privong privong added this to the v0.5.0 milestone Nov 18, 2018
@privong
Copy link
Owner Author

privong commented Nov 18, 2018

With commit 0e112d4, the order of entries has changed. So now this should be implemented by seeing which token was selected and then only showing tile/scoring types that are compatible with that type of token.

@privong
Copy link
Owner Author

privong commented Nov 20, 2018

When the "Traders & Builders" expansion is used, the score type of "Trade token" is added. But that score is not associated with a token type. This suggests that the score type should be input before the token type. Thus, in order to address this issue, the score type (road, meadow, etc.) should then limit the token types that can be chosen. Thus the mappings recorded should be the score type -> token type as initially suggested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant