Combolands Council Votes: What Is Known So Far
A careful guide to Combolands council votes: separate the visible decision layer from player reports, and keep the current rule set marked for verification.
What can be said without filling the gaps
Council voting is a real player-facing question, but the current public evidence does not provide a complete, current rule table. The official store confirms that guild choices are central and that each run uses two guilds. A Steam Community discussion specifically asks what votes do beyond the passive bonuses shown to the player. That tells us where the confusion is; it does not prove a hidden vote formula.
This page is therefore a decision log and research boundary, not a hidden-mechanics guide. It does not claim exact vote timing, vote weights, reroll behaviour, conversion rules, or guaranteed outcomes.
The decision record to keep
When a vote affects your plan, capture the following before choosing:
| Field | Record this | Why it matters |
|---|---|---|
| Version | Installed build and date checked | Vote behaviour may change with a patch |
| Prompt | Exact text and every visible option | Short summaries can hide a condition |
| Run state | Guild pair, rank, island, and visible score context | Separates a vote effect from the broader run |
| Passive display | The bonus or description shown beside the vote | Distinguishes visible information from inference |
| Choice | Which option you selected and why | Makes the test reproducible |
| Result | Immediate change and later cascade | Separates direct effect from subsequent triggers |
Add a screenshot or recording when possible. A player report becomes much more useful when another player can inspect the same prompt and result.
A low-risk way to test a vote
- Write down the prompt before selecting an option.
- State one expected visible result, such as a changed offer, score, or available choice.
- Avoid changing guild pair, item context, and board position at the same time if the run allows a comparison.
- Record the first response and then the later cascade separately.
- Repeat the same question in a current build, or label the result as partial when the board cannot be recreated.
Do not use the absence of an immediately visible score change as proof that the vote does nothing. The sources do not establish when every effect is evaluated.
Patch and terminology traps
The official v1.0.4 notes mention a Politician guild-reselect effect, neutral buildings, and a fixed “no guild” state. Those are current patch-note terms that can intersect with guild decisions, but they do not publish the full council system. If a vote, reselect, or reroll result looks different after an update, keep both versions in the note.
Related evidence
The guilds page records the seven-label cross-check and official 21-pairing count. The building combos page helps separate a vote decision from a later building cascade, while updates is the place to check whether a patch changed the decision layer.
This page records what the linked sources support as of 2026-08-26. If a detail is not named, it stays open instead of becoming a guess.