-
Notifications
You must be signed in to change notification settings - Fork 5
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
Rules to apply #31
Comments
Here are some sequential conflicting rules for the game, where players encounter conflicting objectives one after the other, forcing them to adapt and make strategic decisions as they progress through the game: Level 1: Sentence Structure vs. Run-On Sentences (Sequential Conflict):
Level 2: Subject-Verb Agreement vs. Pronoun Reference Clarity (Sequential Conflict):
Level 3: Spelling Bee vs. Word Choice Dilemma (Sequential Conflict):
Level 4: Comma Placement vs. Hyphenation Hunt (Sequential Conflict):
Level 5: Redundancy Riddle vs. Ambiguity Challenge (Sequential Conflict):
Level 6: Semicolon & Colon Check vs. Quotation Mark Mastery (Sequential Conflict):
Level 7: Capitalization Challenge vs. Apostrophe Misuse (Sequential Conflict):
Level 8: Sentence Structure Shuffle vs. Paragraph Transition Challenge (Sequential Conflict):
These sequential conflicting rules create a dynamic and strategic gameplay experience, where players encounter alternating proofreading objectives as they progress through the levels. It requires them to adapt their focus and prioritize different proofreading tasks, adding depth and complexity to the game. Final Confirmation Challenge:
This rule adds an additional layer of complexity to the game, as players must not only correct errors but also comprehend the text's meaning and context. It encourages thorough proofreading and comprehension skills before progressing to the next level. |
What rules do we want to have
Maybe have list of conflicting rules
Ex:
Can only pick one of the following
Must have even number of chars
Must have odd number of chars
Ex:
The text was updated successfully, but these errors were encountered: