Core Keeper GuidesGuides, database, map tools, and update pages
Co-op entry

Latency Check

Latency Check: use the right page before the route turns messy.

A co-op entry for separating lag from setup, host, or version issues.

Database entries answer the first practical question. Once that answer is clear, the linked full page should take over.

Best linked page

Open the latency check page

Co-opAug 2026co-op / latency / connection

Player problem

Open this when the session is up but the play still feels delayed or noisy.

Where to use this

Use this after invite and version match when the remaining issue is play feel rather than access.

What you need first

A live session and a clear symptom of delay or jitter.

Next click

Use this entry to decide where the next click should go.

Database fields

Use these fields like a quick lookup before opening the longer guide.

Co-op

Role or purpose

co-op

Co-op

Where or unlock

Use this after invite and version match when the remaining issue is play feel rather than access.

Co-op

Best use

Confirming whether the lag is actually a setup issue.

Co-op

Next page

Open the shared base flow page

How to use this entry

Use this page to narrow the task, then move into one stronger route page.

Check whether the delay comes from the connection, the host, or the save baseline before changing anything else.

  • Confirming whether the lag is actually a setup issue.
  • Avoiding unnecessary gameplay changes when the session feel is the real problem.
  • Keeping co-op troubleshooting focused and short.
Open the latency check pageBack to Co-op

Common mistakes

  • Changing the save when the delay is a connection problem.
  • Skipping the first two co-op checks and jumping straight to advanced fixes.
  • Treating every noisy session as if the route itself were broken.

Visual cue

Latency Check visual

Tags

co-oplatencyconnection

Related entries

Open another entry only when the question actually changed.