Start with Steam Discussions or the official website
Use Geoplanetical's Steam Discussions for community help and its Bug forum for problem reports. For the developer-linked Discord, open the official Polytale Games website and follow Join the Discord.
If you arrived from a Reddit search, use the game-specific destinations below to continue. Compare player explanations with the official wiki or patch notes before treating them as game rules. When asking for help, describe what happened in your campaign rather than assuming everyone is seeing the same behaviour.
Choose the right place for your question
| Destination | Use it for |
|---|---|
| Steam General Discussions | Gameplay questions and existing conversations about how a system behaves. |
| Steam Discussions: Bug | Problem reports that explain the attempted action, result and campaign context. |
| Steam Workshop Discussions | Questions about Workshop items and the presentation mods you use. |
| Official Geoplanetical wiki | Menu paths, normal gameplay instructions and the separate console command reference. |
| Polytale Games website | The Join the Discord link and Dispatches containing Steam patch notes, devlogs and announcements. |
Find an existing discussion and developer input
- Open Geoplanetical's Steam Discussions to reach the game's forums and existing topics.
- Choose General Discussions for gameplay help, Bug for a problem report or Workshop Discussions for a mod question, so your topic reaches the relevant readers.
- Search for the exact error message or mechanic involved to find related conversations, including older topics beyond the recently active list.
- Inspect replies for a Steam developer label or a developer-selected answer marker to locate developer input or a highlighted answer.
- Open Events & Announcements to compare the discussion with patch notes before relying on an older explanation or workaround.
- Select Start a New Discussion in the appropriate forum if existing topics do not address your issue. Steam requires you to sign in or create an account before posting.
Read the author information as well as the answer marker. Keep a reply written by the developer distinct from a player answer selected by the developer. If you pass the explanation along, preserve that distinction and compare any claimed rule with the official documentation.
Check patch changes and console use
Tell readers if console commands were involved. For example, yesman makes AI countries accept diplomacy you initiate, and the patch notes describe fixes for its behaviour after a refusal and during peace, ceasefire and armistice negotiations. Name the command and its state so readers can distinguish its effects from ordinary diplomacy.
Avoid using a simulation-changing cheat merely to investigate a report if you want to retain achievement eligibility. A successful cheat permanently disables achievements for that campaign. Turning its toggle off afterwards does not restore eligibility.
Include campaign context in your bug report
Use this checklist to make your report easy to follow. Include the details relevant to the symptom rather than a general account of your whole campaign. Keep your observations separate from your explanation of what might have caused them.
- Country and political role: identify the country you control, whether you are in government or opposition, and the office relevant to the attempted action.
- Campaign date and rules: include the in-game date and relevant settings, particularly when the issue concerns wars, disasters or emerging pandemics.
- Current build or patch: identify the installed build if available, and explain whether the problem still occurs after the update you are discussing.
- Reproduction steps: give the menu path, the option selected and the action taken, in the order needed to reach the problem.
- Observed result: describe what actually happened and include the exact error or blocking message when the game displays one.
- Expected result: explain what you expected the action to do, while making clear which part is your expectation rather than a documented rule.
- Installed mods: list the mods in use. Geoplanetical's supported presentation mods change names, portraits and flags; they do not change the simulation rules.
Use the official wiki to explain the disputed action
For a legislative problem, include the status shown on the law card. A parliamentary vote can still be followed by executive assent, a veto or judicial review before the law takes effect. Describing that stage gives other players more useful context than reporting only that the vote passed.
For an investment problem, include the programme's displayed blocking reason. An authorised programme can wait for financing, technology or industrial requirements before construction starts. Describe the warning and project status so readers can compare the same situation.