Core Rules v1.5In force since 16 Oct 2026
Rules change.
Search engines don't notice.
Ask a Riftbound rules question with a date. rb_errata answers from the rules that were in force that day, and cites the exact rule and version, like core@1.4:419.4.a. It runs on your own computer, offline.
“If my spell gets countered, does it still count for Legion?”
- −
No.Legion needed you to have played another card, and a countered card was not played.
- +
Yes.Play triggers still don't fire, but Legion checks whether another card was Finalized. A countered spell was.
- v1.124 Oct 2025
- v1.212 Dec 2025
- v1.330 Mar 2026
- v1.424 Jul 2026
- v1.516 Oct 2026
- today: 4 Nov 2026
Answers as of a date
Every rules version carries the dates it was in force. Rules that weren't in force on your date are removed before ranking, so an outdated rule can't come out on top.
Works inside Claude Desktop
An MCP server gives AI apps tools to search the rules, see what changed, read one rule and list versions. Every result says which version it came from.
Local, offline, measured
Postgres and Ollama on your machine, no API key. Every claim about quality is measured on labelled questions, with the predictions that were wrong published next to the right ones.
How it works
- You ask with a date. “Does a countered spell count as played?” as of 4 Feb 2026.
- Only rules in force that day are searched. That date falls in v1.2, so the wording Riot changed in v1.3 is out.
- The answer cites the version. Every claim points at a rule like
core@1.2:412.1.b.
// search_rules, called by Claude Desktop
{
"question": "Does a countered spell count as played?",
"as_of": "2026-02-04"
}
// result (rule text omitted here)
[{
"ref": "core@1.2:412.1",
"rules": ["core@1.2:412.1", "core@1.2:412.1.a", "core@1.2:412.1.b"],
"valid_from": "2025-12-12",
"valid_to": "2026-03-30",
"newer_version_exists": true
}]