ROOSTERMC Join Discord
⚙️

Behind the Roost

A plain-English look at the systems that make RoosterMC work without turning the player Wiki into an admin manual.

World / SystemRoosterMC
DifficultyInformational
RecommendedCurious players

Behind the Roost

RoosterMC uses a collection of custom and third-party systems to create its worlds and keep them running together.

Cross-Platform Play

Geyser translates Bedrock clients into the Java server environment. Floodgate allows Bedrock users to join without requiring a Java account while the Java server remains in online mode.

Version Compatibility

ViaVersion, ViaBackwards, and ViaRewind provide protocol-compatibility layers so a broader set of Java clients can connect. The newest/current supported client is still recommended for the best experience.

Dynamic Information

PlaceholderAPI lets different server systems share live values for interfaces, scoreboards, displays, and integrations.

NPCs

Citizens powers many server NPCs, including world selectors and RPG vendors/trainers.

World Infrastructure

PerWorldClusters manages world grouping, inventories, world loading, travel behavior, and protected areas. Void-generation technology is used for special worlds that should not generate ordinary terrain.

Fair Play

RACP provides anti-cheat, audit logging, and moderation/investigation tooling.

Synthetic Residents

RoosterBots are disclosed server-controlled residents used for atmosphere and testing.

The goal of these systems is to support the gameplay you see—not to make players learn a list of plugin names.

Last updated August 20, 2026