Open the developer-linked community
Use the invite in the opening answer when your immediate goal is to find the game's Discord. The Mayors Rebalance announcement and the Construction Points Overview both publish the same invite, giving you two official posts against which to check the destination. This is more specific than a search result simply describing a server as official without showing which developer communication links to it.
Keep the game's community distinct from this independent fan wiki. This site can organize the supplied game information and link to the developer-published invitation, but it does not operate or moderate that external server. When you follow the invite, read the information Discord presents for that destination rather than assuming that the wiki's navigation or contact address describes the community's own joining and posting process.
Verify ownership through official announcements
The useful verification is the relationship between an official game announcement and the invite it publishes. A third-party directory may list the game or describe its community, but that description is secondary to the developer's own published link. Use the official sources listed below if you want to confirm why this particular invitation is identified as the game's community destination.
The two developer posts are separate publications from the same official authority, not independent playtests or proof of every server detail. Their value here is that they repeat the same invite in the game's own announcement context. That supports the identity of the destination without justifying an invented server population, a claimed staff roster or a promise about which channel will be visible after every reader joins.
Use the community for focused gameplay questions
The collected material identifies discussion and feedback as reasons for the official community link. A useful gameplay question states the system you are trying to understand and the specific obstacle your county has reached, rather than only saying that the game does not work. This is suggested communication practice for asking a clear question, not a claim that the server requires a particular template or organizes help in a particular channel.
For example, distinguish a settlement that cannot level up from a workshop missing an input or a route that is not delivering a good. Those are different questions, and naming the product, settlement or relevant region helps keep the issue understandable. The upgrade, production and trade guides can help you identify the question before you decide whether a community discussion is still needed.
Include the version behind your question
The research distinguishes the June Next Fest demo, the updated October demo and the planned Early Access release. Include the version or testing period relevant to your experience when asking a question, especially if an older guide or video seems to describe different behavior. This gives the discussion a concrete context without assuming that every historical report describes the current demo or that all save compatibility questions have the same answer.
The distinction matters for progress as well as mechanics. October demo progress can continue into Early Access according to the developers, while June Next Fest saves are incompatible with the updated demo. If that is the issue you want to discuss, read the demo guide first and identify the build that created your county rather than presenting every old save as part of one undifferentiated demo version.
Make feedback specific enough to understand
When describing a problem, include what you attempted, what the game displayed and what result you expected. A screenshot of the relevant interface can make a production or route question easier to understand, provided it shows the actual issue you are asking about. This is a practical way to prepare feedback, not evidence that a developer has reproduced the issue or that the same action fails for every player.
Avoid presenting an interpretation as an established bug before the relevant supply or version checks are clear. A missing ingredient, an unsupported transport direction and a demo progression cap involve different documented systems even when each one interrupts your plans. Keeping the description tied to the observed screen and game version lets the community consider the specific problem without requiring you to invent an explanation in advance.
Read server information before choosing where to post
The supplied research does not verify channel names, moderation rules or the exact joining sequence inside the Discord server. Read the server's current information after following the official invite, and use whatever posting guidance that destination actually provides. This keeps the page useful without inventing a bug-report channel, a verification button or an access requirement that a reader might not see.
The same principle applies to expectations about replies. The developer-published link establishes an official community destination, but it does not promise a particular response time or guarantee that a specific member of the development team will answer every question. Ask the focused gameplay or feedback question you actually have, while following the current information supplied by the server itself rather than a fictional procedure added by an outside guide.
Use the official Steam community as another route
The official Steam discussions provide another game-community destination already identified in the site's official links. They are useful when the question concerns a developer announcement or a discussion you can read without relying on an invented description of Discord's internal structure. Use the destination that fits your question, while keeping any player report's date and version separate from a current official statement.
For product identification, the Steam guide links the main game and separate free demo. For a particular mechanic, the relevant guide may answer the question before you need to post it elsewhere. These options supplement the official invitation rather than replacing it with an unrelated community link or suggesting that a fan wiki's own contact inbox is the developer's support service.
Keep the invitation and gameplay evidence separate
An official invite answers where the developer-linked community is, not whether every claim made in a community conversation is verified. Treat a discussion of a recipe, platform or future feature according to the evidence actually supplied for that claim. This distinction lets the community be useful for questions and feedback without turning the existence of a Discord link into proof of unsupported game information.
Use the official invitation to reach the destination established by the developer posts. Bring a specific question, its version context and any relevant interface information, then follow the server's current guidance for where that question belongs. If you only need an explanation of the opening economy, the beginner guide is a direct starting point that keeps food, construction and equipment questions separate.
Official sources
Information checked November 4, 2026. Send a correction.