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

Raising stakes in game play. #16

Open
bizquig opened this issue Nov 23, 2016 · 2 comments
Open

Raising stakes in game play. #16

bizquig opened this issue Nov 23, 2016 · 2 comments
Assignees
Labels

Comments

@bizquig
Copy link
Collaborator

bizquig commented Nov 23, 2016

We should raise stakes in the game play.

Proposal: we have a list of "challenges" and the computer randomly picks one and assigns it for that round, and then picks another challenge for the following round, etc. until the game is over. These challenges might start at round 3 or 4 or something. That way we have a normal couple rounds, then the "puzzle" part kicks in and hopefully stakes get greater.

These challenges would be ranked as "lower gear" and "higher gear" so that the game continues to build. The "lower" ones would be relatively easier to pull off, "higher" more challenging. Say in a 10 round game the first 3 rounds are normal (no challenges), 3 rounds of "lower" challenges, 3 rounds of "higher" challenges, then some sort of set "stakes is high" last round. What that "stakes is high" last round challenge is remains to be seen. Feel free to offer suggestions.

Examples of some challenges:

  1. If you can use two tiles in a your word you can get another bonus.
  2. If you can play four consonants in a row (SCHNAPPS, e.g.) you get another another bonus.
  3. Use all five vowels in your word to get another bonus
  4. Have a palindrome string in your word (CANNABIS, e.g. has the palindrome "ANNA") to get another bonus.
@bengottlieb
Copy link

I think this all sounds good. We need to codify them.

@bizquig
Copy link
Collaborator Author

bizquig commented Jul 11, 2017

Is this worth pursuing again for the MVP? Or shelve it for the next rollout?

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

No branches or pull requests

2 participants