← Mini-games · Runtime config

WordSpar

Wordle-style daily vocabulary — guess the word in 5 tries (EN) / 4 tries (HI).
wordspar

What this game is

  • 5×5 grid for English, 4×4 for Hindi (Devanagari grapheme clusters per R-MG-2).
  • Daily difficulty mix per weekday (Mon hardest, Sun easiest).
  • AES-256-GCM per-day key (R-MG-3) — server never reveals the answer until solve/fail.
  • Title "Wordsmith" (any solve), "Linguist" (HI solve specifically).

Player's view

┌─────────────────────────────┐
│   C R A N E    ← guess 1    │
│   S L A T E    ← guess 2    │
│   _ _ _ _ _    ← guess 3    │
│   _ _ _ _ _                 │
│   _ _ _ _ _                 │
│   [ Q W E R T Y … ]         │
└─────────────────────────────┘
Compact mockup so you can match config keys to UX elements.

Configuration

Empty field = use compile-time default (shown in grey). Changes propagate to mobile within ~1 second via Postgres NOTIFY.

grid_rows
Number of guess attempts (English).
Default: 5 using default
grid_cols
Word length (English).
Default: 5 using default
hi_grid_rows
Number of guess attempts (Hindi).
Default: 4 using default
hi_grid_cols
Word length in Devanagari graphemes.
Default: 4 using default
pool_memory_window_days
How long before a previously-used word can repeat.
Default: 1825 using default
key_endpoint_daily_limit
How many times /key can be called per user per day. Usually 1.
Default: 1 using default
hi_pool_min_viable
Min live HI pool size to keep the game daily. Below = weekly cadence.
Default: 1200 using default
difficulty_curve_by_dow
7 entries Sun..Sat. Each = [common, standard, hard] summing to 1.0. Example: [[0.6,0.3,0.1],[0.5,0.3,0.2],…]
using default
Writes go through admin audit log (action minigames.config.update) and trigger a Postgres NOTIFY that the API's in-process loader picks up immediately.