VelorFailover

Redirect on a crash, never on a kick.

ReleasedPaidOperations

Crash-aware fallback for Velocity networks, plus config-driven switch commands.

Gallery

Screenshot area

Real screenshots of this plugin will appear here.

Pings the server instead of guessing: a server that answers keeps Velocity's normal kick handling.
Only a failed ping triggers the fallback, so bans and moderator kicks are never redirected.
Planned stops and restarts are recognised from the kick message and players return to where they were.
Players return after consecutive successful checks, at a rate you set.
Config-driven switch commands and routes; a looping route is rejected with a warning.
Optional companion teleports returning players to spawn.

A watched server, a fallback and how fast players return.

yaml

health-check-interval-seconds: 10
return-stability-checks: 2
fallback-routes:
  - watch: survival
    fallback: lobby

Platforms: Velocity, Paper, Folia
Minecraft: Velocity 3.3+; optional companion on Spigot, Paper, Folia or Purpur 1.21+
Java: 17 / 21
Required: None
Optional: VelorFailoverSpawn
Category: Operations
Documented version: 1.2.2

The documentation describes version 1.2.2.

Planned stops depend on your stop message containing one of the configured texts.
If the fallback server is also down, nothing is redirected.

Will it move players when a moderator bans them?

No. A server that answers the ping means the kick is handled by Velocity exactly as without the plugin.

Is the Spawn companion required?

No. Without it, returning players simply keep their saved position.

Security: players can no longer trigger the spawn teleport signal themselves; the proxy drops client-sent messages on its channel.
The proxy plugin is built for Java 17.
A malformed config.yml no longer crashes the plugin: the line is reported and the previous settings stay active.
Switch commands say what happened; name clashes and looping routes are reported instead of silently accepted.