This version of The Password Game has 22 rules
The Password Game on this site has 22 cumulative rules. They begin with familiar password requirements, then introduce current-date information, pattern matching, digit arithmetic, Roman numerals, a country and chemical element, uppercase vowels, prime length, a perfect square, a NATO phonetic word, and an ASCII divisibility check. Cumulative means a rule remains active after you solve it. The final answer must satisfy Rules 1 through 22 simultaneously, which is why a late edit can turn an early green card red.
Other versions may quote a different total, order, or mechanic. When playing here, trust the numbered list in the current game: the finish line is Rule 22. Rules 1 through 10 establish foundation and daily content. Rules 11 through 18 create the densest overlap between numbers, words, and live prompts. Rules 19 through 22 form the final optimization stage, where length and letter values must be tuned without damaging earlier work.
Rules 1-4: the basic foundation
Rule 1 requires at least five characters. Rule 2 requires a number. Rule 3 requires an uppercase letter. Rule 4 requires an accepted special character from the displayed set. These checks resemble ordinary password requirements, but this is a puzzle. Use disposable nonsense rather than a real credential. Keep the opening block short because many words, digits, and symbols will be added later. A minimal base is easier to audit than a long phrase.
Avoid optional text even now. Extra digits matter when the sum must equal 25. Extra uppercase letters may become Roman numerals. Vowels later need uppercase conversion, and every character changes final length. Use a neutral uppercase consonant that is not I, V, X, L, C, D, or M, one obvious digit, and one allowed symbol. The goal is flexibility, not memorability. Every early character should satisfy a rule or be easy to replace.
Rules 5-7: weekday, date, and alphabet pair
Rule 5 asks for today’s weekday. Rule 6 asks for today’s date number. Rule 7 requires two adjacent characters that are neighbors in the alphabet, such as ab, st, or yz. The first two values depend on the current day, so an old answer can be stale. Put them in a visible daily block. For the alphabet rule, choose a pair you can find later rather than relying on a coincidence buried inside a long word.
The date contributes to the later digit sum. The weekday contributes vowels, possible Roman letters, length, and ASCII values. This is the first major example of cumulative interaction: satisfying a current rule changes inputs to future ones. Do not optimize those totals yet, but remember where the blocks live. When the target of 25 or uppercase-vowel rule appears, return to the known block instead of searching the entire string blindly.
Rules 8-10: month, moon, and weak words
Rule 8 requires any month. Rule 9 requires the current moon phase emoji shown by the game. Rule 10 rejects common weak-password terms such as password, qwerty, and 123456. Choose a month with later conflicts in mind, place the moon in its own block, and remove banned terms even when they appear as substrings. These rules shift the challenge away from ordinary password composition and toward exact content management.
The month affects uppercase vowels, Roman extraction, length, and ASCII. The moon can change with time and may count differently from plain letters in another editor, so use the live length rule near the end. The weak-word condition must stay true while new text is added. At Rule 10 the password may already seem advanced, but the most interdependent mathematical and prompt-driven requirements are still ahead. Preserve clear block boundaries before continuing.
Rules 11-13: digit sum, Roman product, and year
Rule 11 says all digit characters must add up to 25. Rule 12 says Roman numeral tokens must multiply to 35. Rule 13 requires 2026, whose digits contribute ten. V-VII supplies factors five and seven when the hyphen separates them; XXXV can also parse as 35. Keep a written digit subtotal and isolate the Roman block. These two math rules are frequently broken later by mandatory numbers and uppercase words.
Do not finalize digit sum yet. Binary digits, an atomic number, and a perfect square are coming. Do not assume Roman product remains stable after a country, element, NATO word, and uppercase vowels are added. Every uppercase I, V, X, L, C, D, or M can enter the calculation. Treat the first green state as a baseline and audit both systems after every relevant addition.
Rules 14-16: element, binary, and country
Rule 14 requires the selected chemical element symbol. Rule 15 requires a continuous binary string at least four digits long using zeroes and ones. Rule 16 shows a flag and requires its country name. Copy the element with displayed capitalization, use a short binary run such as 1010, and spell the country correctly. Element and country are dynamic prompts, so another player’s solution may not match your run.
Binary ones change digit sum. The element symbol and country can contain Roman letters. Country vowels must be uppercased in the next rule, while all letters change length and ASCII. Add the three blocks separately and check earlier cards after each addition. If the product of 35 or total of 25 breaks, the latest block is the first place to inspect. Controlled insertion is faster than repairing several unexplained failures at once.
Rules 17-18: uppercase vowels and atomic number
Rule 17 requires every vowel to be uppercase: A, E, I, O, and U. Convert vowels throughout weekday, month, country, and other words. Rule 18 requires the atomic number of the same element from Rule 14. Enter the exact displayed number. Both rules reach backward across earlier content. Uppercase I is Roman, and the atomic number contributes to digit sum, so two previously green math cards may change immediately.
Perform two audits. Scan all uppercase Roman sequences and calculate their product. Then add every Arabic digit. If the Roman result is no longer 35, identify the new token before changing the protected block. If digits no longer total 25, remove optional numbers and adjust a dedicated tuning digit only after preserving date, year, binary, and atomic number. Clear accounting replaces random trial and error.
Rules 19-20: prime length and perfect square
Rule 19 requires total length to be prime. Rule 20 requires a perfect-square number such as 4, 9, 16, 25, 36, 49, 64, or 81. Put the square in its own numeric block so adjacent digits do not create a different integer. Select one that fits the remaining digit budget, then move length toward a nearby prime with low-risk filler. These are late rules because almost every future edit changes length.
Prime length is fragile. A filler letter changes ASCII; a Roman letter may change Rule 12; a digit changes Rule 11 and can merge with the square. Symbols are often safer for length because they do not contribute to letters-only ASCII, but they still count as characters. Use the live validator when emoji are present and make one-character adjustments. Large filler blocks destroy the information needed to tune accurately.
Rules 21-22: NATO word and ASCII
Rule 21 requires a NATO phonetic word such as Alpha, Bravo, Echo, Golf, Hotel, Oscar, Papa, Xray, or Zulu. Choose one, uppercase its vowels, and inspect its Roman letters. Rule 22 requires the ASCII sum of all English letters to be divisible by seven. Digits, symbols, and emoji do not contribute to that letter sum. This is the final numbered rule, but solving it can still break prime length or Roman numerals.
Stabilize required words, total the letter codes, and find the remainder modulo seven. Add or replace a safe consonant to correct it, then recheck prime length. A letter changes both ASCII and length; a symbol changes only length. Use that distinction to tune the final state. The game ends only when NATO word, ASCII division, prime length, and Rules 1 through 20 all remain green together.
Which rules change and which are flexible?
Weekday, date, moon phase, element, atomic number, and country are dynamic. The year 2026, digit target 25, Roman target 35, and ASCII divisor seven are fixed here. Month and NATO word are flexible because many accepted choices exist. Dynamic values must come from the live prompt, fixed targets must be calculated, and flexible choices should be optimized to reduce conflicts. This classification explains why a universal copied password is unreliable.
Choose a month and NATO word that introduce fewer Roman letters, fit remaining prime length, and offer a useful ASCII remainder. You cannot replace a mandatory country or element just because it is inconvenient. Optimize optional content first, preserve live answers, and use small tuning blocks for final math. Understanding which values can move gives much more control than memorizing the order of cards alone.
Why 22 rules feel harder than 22 questions
The challenge comes from overlap. A country name is required text, vowels, possible Roman numerals, several ASCII values, and a contribution to length. An atomic number is required content and part of digit sum. A NATO word satisfies one rule while changing three others. The same characters are reused as inputs to new validators, so a correct answer for Rule 21 can break Rules 12, 17, 19, and 22.
Treat the password as a shared data structure rather than a sentence. Give each block a purpose, record numeric totals, and reserve flexible tuning for the end. After every digit edit, audit numeric rules. After every letter edit, audit vowels, Roman numerals, ASCII, and length. This model makes the stacked design predictable. The count is finite; the apparent chaos comes from connections between rules, not hidden requirements beyond Rule 22.
The 22-rule finish checklist
Verify minimum length, number, uppercase letter, special character, current weekday, current date, adjacent alphabet pair, month, moon emoji, no weak term, digit sum 25, Roman product 35, year 2026, element symbol, four-digit binary run, country, uppercase vowels, atomic number, prime length, perfect square, NATO word, and ASCII sum divisible by seven. Check from Rule 1 to Rule 22 without assuming earlier green cards stayed solved.
The answer to how many rules are in The Password Game on this site is 22. More usefully, they form manageable groups: foundation, daily content, number and Roman math, live knowledge, text normalization, and final optimization. Build and verify those groups in order, and never use a real password in the puzzle. With a block-based string and disciplined auditing, the count becomes a roadmap rather than an intimidating stack of surprises.
Plan the 22 rules in three passes
A practical first pass collects content: solve Rules 1 through 10, then add year, element, binary, country, and atomic number. Do not perfect digit sum, length, or ASCII during this pass because mandatory content is still changing. The second pass normalizes the whole string: uppercase vowels, identify every Roman token, select the square and NATO word, and bring all digits to 25. At the end of this pass, every required fact and word should be stable.
The third pass handles optimization: move to a prime length and make the letter ASCII sum divisible by seven. Use a correction letter for the ASCII remainder and nonletter symbols for additional length, checking the full list after each edit. If an earlier rule breaks, return only to the block responsible for that character type. Three passes do not reduce the number of rules, but they reduce repeated work by delaying fragile totals until the content that controls them has stopped changing.