Skip to main content

AccessReplicationState

What this realm has been told about a fact, as four distinct states rather than a boolean and a guess. Helpers live in AccessReplicationStateUtils.

Three of these look like "false" if you flatten them, and each needs a different response:

  • NOT_YET_ARRIVED -- the server has not spoken. Never overrides; the local answer stands.
  • ABSTAINED -- the server has no layer for this fact either. Nobody anywhere can answer it.
  • UNRESOLVED -- the server tried and could not answer yet. A real answer, so it stops a local fall-through.
  • RESOLVED -- the server has an answer, carried alongside in value.

Collapsing these is how a chapter picker ends up empty forever: "has not arrived" and "cannot be answered" render identically while meaning opposite things about whether waiting will help.

Show raw api
{
    "functions": [],
    "properties": [],
    "types": [],
    "name": "AccessReplicationState",
    "desc": "What this realm has been told about a fact, as four distinct states rather than a boolean and a\nguess. Helpers live in [AccessReplicationStateUtils].\n\nThree of these look like \"false\" if you flatten them, and each needs a different response:\n\n* **NOT_YET_ARRIVED** -- the server has not spoken. Never overrides; the local answer stands.\n* **ABSTAINED** -- the server has no layer for this fact either. Nobody anywhere can answer it.\n* **UNRESOLVED** -- the server tried and could not answer yet. A real answer, so it stops a local\n  fall-through.\n* **RESOLVED** -- the server has an answer, carried alongside in `value`.\n\nCollapsing these is how a chapter picker ends up empty forever: \"has not arrived\" and \"cannot be\nanswered\" render identically while meaning opposite things about whether waiting will help.",
    "source": {
        "line": 19,
        "path": "src/access/src/Shared/Replication/AccessReplicationState.lua"
    }
}