I have been moderating a product-focused community for about three years now, and this pattern never really goes away. Someone joins on a Tuesday, posts “how does the daily reset work?” and within an hour three people link the same sticky thread from last spring. The honest answer is that searching is a skill, and most people are bad at it when they are in a hurry.
It also covers XL live arcade games in practical terms.
A few reasons stand out. First, forum search tools are often clunky. If you type “daily promotions timer” but the thread says “slots with daily promotions,” you get zero results and assume the answer does not exist. Second, people want a human confirmation. They know the info is probably buried somewhere, but they also want someone to say “yes, this still works in the current patch.” That is not laziness, exactly. It is uncertainty about whether old threads are outdated.
I have also noticed that new members treat a forum like a chat room. They ask first because typing a question feels faster than reading three pages of a megathread. One concrete example from our community: we renamed a sticky from “FAQ” to “Start here before posting about daily promo timers,” and repeat questions dropped noticeably. The title matched the exact words people were typing.
A small tip for regulars: when you see a repeat question, answer it briefly and then add one line like “search for ‘daily reset thread’ next time.” That teaches the habit without shaming anyone. Over time, the same people who asked twice start answering the third time. It is less about forcing people to search and more about making the search result actually worth clicking.
If you want a calm example of how a well-run community handles repeat topics, this community guide walks through the exact wording we use. And for anyone curious about how product teams reduce repetitive support questions through better UX, the same principle applies to feature naming.