When discussing Krillion, include the date and keep answer words out of an unmarked title. If a result seems wrong, share the full question, exact input and observed outcome so another reader can check the same thing.
Share the result before the solution

This screen makes a spoiler risk visible: the total is safe to discuss more broadly, but the recap names answers. Use a spoiler warning for the screenshot, or share just the date and result.
Example post, not a recorded player result:
“Daily Dive · [date or Dive number] · [points or depth]. One result surprised me; answer discussion below the spoiler warning.”
Use the game’s share option where available and inspect what it includes before posting. An image can reveal a question or answer even when the title is spoiler-free.
- Keep named answers behind the community’s spoiler control.
- Warn before a screenshot with visible solutions.
- Check the forum or group’s actual rules.
- Do not assume every player is using the same local calendar date.
Ask a question another reader can reproduce
- Date and prompt: link to the exact dated question.
- Input: quote the spelling you actually submitted.
- Outcome: distinguish retry, expiry and an accepted tier.
- Evidence: add a reference or screenshot that supports your concern.
“I knew a better answer” is hard to investigate. “This credit satisfies both live-action appearances in this question” gives a specific fact to check. Do not invent the outcome of an input you did not submit.
Keep community guesses separate from the game’s method
| Claim in discussion | What would support it? |
|---|---|
| This word scored 15 | The dated question and a saved or observed result. |
| Most players chose this word | Actual player-submission data, which we do not hold. |
| This answer should qualify | A reference matching every condition; acceptance still needs separate evidence. |
A popular comment is not an official scoring explanation. Check the official FAQ for the game’s stated approach rather than repeating an inferred live voting system.
Choose the appropriate channel

For a correction, include the dated URL, question number, exact claim and a supporting reference. You can review the email before sending; do not attach account credentials or purchase details.
- Live game, account or purchase: use the official game’s support links.
- This site’s score, explanation or broken link: use Corrections.
- General discussion: use a community you already trust, after reading its rules.
We have not verified a daily pinned thread for every dive or an official public Discord, so this guide does not promise either. Avoid sharing credentials or treating a similarly named fan group as the game developer.