Documentation menu

Reference

Reliability

What happens when Jev is slow or down, and how jev-guard backs off.

Checks never run on the game’s main thread, so a slow or broken API can’t freeze the server. What it can do depends on the mode.

When a request fails

  1. Retries. A 429, 529 or 5xx answer is retried up to api.max-retries (2) times, waiting longer each time. One request may take api.timeout-ms (4 seconds).
  2. Circuit breaker. After circuit-breaker.failures (5) failed requests in a row, jev-guard stops calling Jev for circuit-breaker.cooldown-seconds (30), then tries again. /jevguard status shows api=PAUSED (circuit open) meanwhile.

What players notice

Mode When Jev is slow or down
shadow, deliver Nothing. Messages are already delivered; those checks are skipped and counted as errors.
hold After hold.timeout-ms (1.5 s), on-error decides.

With on-error: allow (the default) the message goes through unchecked. With block it is hidden and the player sees messages.unavailable. Use block only if unchecked chat is worse for you than no chat.

Something wrong or missing on this page?Open an issue on GitHub.