It gave a wrong answer
The agent answered, but the answer wasn’t right. Before flagging it, it helps to know which kind of wrong you’re looking at, because the fixes differ.
Outdated after a patch
The most common case. The answer was correct last week, but a patch changed the number and the agent’s data hasn’t caught up yet.
Look at the timing. If you shipped an update recently, the agent may be answering from the previous build until the data refresh lands, usually within a day. You can watch for this as a bump in low-confidence answers in your analytics. If it’s urgent, pause the agent until the refresh completes.
Misread the question
The number is real, but the agent answered a different question than the one the player meant. This happens with ambiguous or very short questions.
Often the player rephrasing fixes it. If the agent consistently misreads a certain kind of question, that’s a tuning issue on our side worth flagging so we can see the pattern.
Held back by a spoiler rule
Sometimes an answer looks wrong because it’s incomplete: the agent blurred or withheld the part past your spoiler line. That’s working as configured. If the content is no longer a spoiler, move the line.
A genuine mistake
If the number is wrong and it isn’t a stale patch, or the recommendation is bad on its own terms, flag it. The fastest path is a 🚩 reaction on the message or the Report to Campfire action; for detail, send it to us with a screenshot. Full steps are on flagging a wrong answer.
What to tell us
When you report a wrong answer, three things get it fixed fastest:
- The question, and the agent’s answer (a screenshot is ideal).
- What the right answer is.
- Whether you’ve patched the game recently.