Communities

A community is a user-run gaming or modding organisation. It is the umbrella an operator puts their servers, mods, assets and articles under, and it gets its own landing page, article section and browsers.

What only a community does

ageRequirementNONE | ADULT_18 | ADULT_21default NONE

The minimum age the community states its spaces are for.

This is a claim by the community’s owner, not an enforced gate. Nothing on this site verifies anybody’s age, and pretending otherwise would be worse than saying nothing. It exists so an operator running an adults-only server can say so, and so a reader browsing servers can opt into — or out of — seeing them.

It is an enum rather than a number because 18 and 21 are the two lines that actually exist in the jurisdictions our operators run in; a free integer would produce a filter with a dozen meaningless values in it.

namestringrequired

Globally unique, unlike a mod’s name. So is the URL slug — a community is not filed under an app, so there is no per-app namespace to disambiguate it.

appsrelation

Which apps this community is about. A community may span several.

What a community owns

A community can be named as the parent of:

• Servers — they appear on the community’s server browser
• Mods and assets
• Articles — the community gets its own article section at /c/<community>/articles

Naming a community on an item is what lets the community’s team co-manage it, and puts the item on the community’s pages.

What can be attached

The full standard set: media, links, dependencies, contributors, permissions, tags and categories, engagement, follows and the full set of boards.

Communities do not take releases — they publish nothing themselves; the items under them do.

Through the API