Compatibility

Server software

• Spigot, Paper and forks — the primary target. Venus detects Paper-specific threading and a few NMS behaviours at runtime instead of assuming them.
• Folia — supported. Regionised threading is detected and entity work is scheduled through the entity scheduler.
• Fabric — supported through a dedicated build; entity and world access go through the platform layer rather than NMS reflection.

Version translation and Bedrock

ViaVersion, ViaBackwards and ViaRewind are fully supported, including players several versions behind the server. Packets are read after translation, so a check sees the player's real client behaviour rather than a rewritten packet.

Geyser and Floodgate are supported. Bedrock players are identified through the Geyser UUID convention and can be excluded from checks that assume Java movement — the shipped configuration already contains the standard exclusions.

Staff tooling

• PlaceholderAPI — Venus registers an expansion, so alerts and other plugins can reuse its placeholders.
• TAB and other scoreboard plugins — coexist normally; Venus does not own the tab list.

Known interactions

• Netty-injecting plugins. Anything else that puts a handler in the pipeline can reorder packets. When checks behave oddly for one group of players, a second injector is the most common culprit.
• Anti-cheat-to-anticheat. Running two anticheats at once is not supported; both will cancel and resync packets and each will see the other's corrections.
• Custom knockback and explosions. Servers that replace vanilla knockback should say so in the configuration so the simulation matches.
• Geyser-style custom movement. Vehicles and riding are simulated separately; if a plugin rewrites vehicle packets, expect vehicle checks to need the corresponding exemption list entries.