I Built My Own Wordle Engine to Support How I Actually Think

Why I Built My Own Wordle Like a lot of developers, I enjoy Wordle. But after playing for a while, I realised I didn’t just want to play it — I wanted to understand it. So instead of cloning a template, I built my own Wordle engine from scratch. Not because the world needed another clone. But because I wanted: Full control over the word pool Seeded daily logic I understood completely A stats system I could extend cleanly And a version that reflected how I actually think when solving puzzles That’s how Web Weavers Wordle started. Custom Word Pool (Under 1k → Nearly 6k Words) Originally, my word list was tiny — under 1,000 entries. It worked, but it felt constrained. So I rebuilt the dictionary layer entirely. Instead of a single static list, I moved to: Separate .txt files per word length Dynamic loading A combined VALID_SET for fast validation Per-length counts for UI stats The pool is now just under 6,000 words, all curated to match the theme (every answer starts with W). It’s modular