JoinGG.cc
Analysis

The cost of cross-platform play for community hosting

Console platforms require that their users are protected by systems the platform can hold somebody accountable for. A community server cannot provide that, so it is excluded from the certified path rather than banned outright. The loss is not just numerical: console players have no habit of choosing servers, so excluding them removes the population that would most benefit from being shown an alternative.

By SweetMask · · 4 min read

Crossplay is presented as a technical achievement and is mostly a policy one. The hard part was never making a console and a PC exchange packets — it was getting three platform holders to agree on what happens when something goes wrong, and the terms of that agreement are what community hosting runs into.

The requirement that actually bites

Console platforms require that players on their platform are protected by systems the platform can hold somebody accountable for. Moderation, reporting, age controls, and the ability to act on a complaint.

A community server cannot provide that. It is run by a person with no relationship to the platform, no contractual obligation, and no process the platform can audit. From the platform's position that is not a server, it is an unmanaged environment containing its users.

So the usual outcome is not that community servers are banned from crossplay. It is that they are excluded from the certified path, which amounts to the same thing.

The three arrangements that result

Console players in a walled garden. Official servers only. Crossplay works, community servers are unreachable, and the console population never encounters the community layer at all.

Crossplay on community servers, without console. PC and sometimes mobile can reach community-hosted games; console cannot. This is the most common shape and it is why so many games have a thriving community scene that console owners have never seen.

Full crossplay with certification. Rare, and it requires the publisher to run or approve the hosting, which turns a community server into a franchise.

None of these is a technical outcome. All of them are decided by contract.

What it costs the community layer

Population, obviously. But more specifically: it costs the community layer the players least likely to find it by other means.

A PC player who wants a particular ruleset will find a server list and look. A console player has no equivalent habit, because their platform has never presented servers as a thing you choose. Excluding console is therefore not just a numerical loss, it is the loss of the population that would most benefit from being shown an alternative.

The versions that do work

Games where community hosting survived crossplay generally did one of two things.

Kept the console experience entirely separate. No pretence of unity — console gets official matchmaking, PC gets servers, and nobody is told they are the same product. Honest, and it works.

Gave the server a certified wrapper. The publisher provides the moderation and reporting layer, and the server owner configures the game inside it. This preserves most of what makes community servers worth having while satisfying the platform.

The second is more work and is the only arrangement that has produced genuine crossplay community hosting at any scale.

What a server owner should take from it

If your game supports console crossplay, find out whether your server can be reached from console before building anything around the assumption. The answer is usually no, and discovering it after you have advertised is worse than knowing.

If the answer is no, that is not necessarily a problem: it means your audience is defined, and defining your audience is most of what a listing has to communicate anyway. A server that says clearly which platforms it serves loses nobody it could have kept.

The moderation problem crossplay creates

The technical costs get discussed and the moderation cost does not, although it is the one that reaches the owner first.

A crossplay server has players on platforms with different identity systems, different reporting routes, and different degrees to which a ban can be made to stick. A console account may not be addressable by the tools that work on the desktop version, and the platform holder's own enforcement runs on a track the server cannot see or influence.

The practical result is that the same offence produces different consequences depending on where somebody is playing from, and the community notices that long before the staff articulate it. A server that bans a PC player permanently and cannot meaningfully remove the equivalent console account is not being inconsistent on purpose, and explaining that is harder than it sounds.

Worth deciding in advance whether the server's rules are enforceable across every platform it admits. If they are not, the honest options are to say so or to admit fewer platforms, and the servers that do neither spend their moderation capital on arguments about fairness that were built into the arrangement.

The part worth arguing about

The platform requirement is not unreasonable. Somebody does have to be accountable for what happens to a fifteen-year-old in a voice channel, and "a volunteer on the internet" is a genuinely unsatisfying answer.

But the current arrangement resolves that by removing the option rather than by defining what an acceptable community server would look like. A certification path for individual server owners (a set of requirements you could actually meet) does not exist anywhere, and its absence is a choice rather than a technical limit.

Until it exists, the community layer and the console layer are two separate games wearing the same name, and the players on each side mostly do not know the other exists.

crossplayplatformscommunity serverspolicy

More