Requirements

Server

• Java 17 or newer. Older runtimes are not supported by the bundled PacketEvents build.
• A Bukkit-family server, Folia or the Fabric build. Spigot, Paper and their forks are all fine; regionised threading is detected and handled on Folia.
• No ProtocolLib, no second PacketEvents. Venus bundles its own PacketEvents and injects at the Netty level. A second copy of the same library is the most common cause of checks going silent.

Runtime resources

Venus keeps per-player state, a compensated world view and a short block/entity history. On a busy server that is measured in a few hundred kilobytes per player, driven mostly by the history windows you configure. The two options that dominate the memory footprint are the transaction timeout and the cancelled-packet budget, both documented in the shipped configuration file.

Network

Venus needs outbound HTTPS to the Venus backend while it downloads the core and, afterwards, while the cloud connection is up. If your host blocks outbound traffic, the anticheat still runs locally but cloud detections, ban waves and history upload stay offline; the console says which of those is unavailable at startup.

Proxies

Venus runs behind BungeeCord, Velocity and Waterfall. Two things matter:

• Players must be checked on the backend server, not the proxy — that is where the movement packets actually arrive.
• Modern forwarding and legacy forwarding both work; Venus reads the same handshake data your server already sees.