DEV Community

Andy Stanly
Andy Stanly

Posted on

Why an Independent Guide Refuses to Post the Answer

A guide site for a daily trivia game has an obvious revenue path: post the answers, publish them early, take the traffic. It is also the fastest way to make the game stop being worth playing, and to make the guide useless to the people it was built for.

The policy at this site is therefore stated in the negative, which is unusual but unambiguous. It does not publish the current day's answers, because a guide that spoils the Daily removes the only reason to play it. It does not automate play or predict the answer boards. And it does not ask for anybody's game account.

Publishing a date on every rule is the whole verification loop

Every rule on the site is compared against the game's own pages before it goes up, and each guide carries the date it was last checked. That single mechanism does more work than it looks like doing, because it turns "we might be wrong" into a question with an answer.

  • A rule carries a checked date, so a reader can tell a stale guide from a current one.
  • Where the provider gives no explanation, the guide says so instead of inventing one — the rename page is the clearest example.
  • It does not check individual answers against the game's internal answer bank, and it cannot see your run.
  • If a valid answer was refused, the game's own report option is the right route, not an email to the guide.

That last point is the honest boundary of the whole operation. A guide can verify rules, because rules are published and stable. It cannot verify what the answer bank contains, because that is not visible from outside. Saying so plainly is more useful than pretending, and it routes the reader to the place that can actually fix the problem.

There is also a scope question worth stating plainly: the site is independent and not affiliated with the publisher, the game and its artwork belong to their respective owners, and the only address published is a contact email for corrections and accessibility problems. All of that is set out in the about crowdict page.

Top comments (0)