ViaRewind Plugin FAQ

Yes. ViaRewind does nothing on its own — it depends on ViaVersion and ViaBackwards being present. Drop all three jars into your plugins folder and restart the server.

Check the console on startup for the ViaRewind entry loading after ViaVersion and ViaBackwards, and run the ViaVersion status command to see the loaded add-ons. If ViaRewind is missing from that list, it failed to load.

It requires Java 8 or newer. If your server runs on an older Java runtime, the plugin will refuse to load.

The most common cause is a missing or outdated ViaBackwards, since ViaRewind hooks into it for the older protocol translations. Make sure all three plugins are the same generation and loaded in the right order.

This usually means a plugin on your server is sending packets that ViaRewind can't translate down to the old client's format. Try removing or updating the offending plugin, or check the ViaVersion debug output to see which packet is failing.

No. Legacy clients can only render what their version supports, so anything added in later versions will appear as a placeholder, missing texture, or simply not show up. ViaRewind translates packets, not assets.

No — they play with their own version's mechanics, including old combat cooldowns and hit registration. ViaRewind only makes the connection possible; it doesn't unify gameplay rules across versions.

It adds some packet translation overhead per legacy connection, but for a typical player count the impact is small. If you see lag, check whether other plugins are also processing packets for those players.

Usually yes, but anti-cheat plugins that inspect packets may flag or block translated traffic from legacy clients. Test with your specific setup and whitelist the Via plugins if needed.

Generally no — it works out of the box once ViaVersion and ViaBackwards are present. Only touch the config if you need to disable specific translations or debug a connection issue.