Build and Conquer Known Issues: Recorded UI Discrepancies

Which interface discrepancies can be shown directly?

The two records below contain conflicting labels within a single paused frame. Their live status is unconfirmed as of October 15, 2026. We have not reproduced them in a current game session or authenticated a developer fix. They are a dated issue log for reading the interface, not a list of guaranteed active bugs.

Record	Visible disagreement	Confirmed scope	Live status / verified fix
Strip Mall, September 30, 0:09	Tooltip: 3 workers; sidebar: 8 workers	Two staffing labels in the same recorded interface	Unknown / none established
Small Refinery, September 27, 0:14	Selected placement quote: $18,300; sidebar: $18,000	Two displayed prices in the same recorded frame	Unknown / none established

Neither discrepancy identifies its cause. A stale field, a context-dependent quote or another interface rule remains possible. Do not turn the observations into a claim about lost currency, incorrect staffing in the simulation or a reproducible exploit.

What should you check when the worker labels disagree?

IIlias_speeddyyy, September 30, 2026, 0:09. Game imagery © The Slop Company.

1. Confirm that both labels refer to the same named building rather than a previously selected card.
2. Read the current tooltip and selected sidebar separately; record both if they still disagree.
3. Inspect the completed building’s operating state and the city’s free-worker counter before expanding a batch.
4. Leave the disputed worker input blank in efficiency calculations until the applicable figure is clear.

These are suggested diagnostic checks, not a tested fix. Our shared mall record omits a numeric worker field, so no income-per-worker ranking silently chooses three or eight. Its undisputed income, upkeep and service labels remain usable with the stated date.

What should you check when the prices disagree?

IIlias_speeddyyy, September 27, 2026, 0:14. Game imagery © The Slop Company.

Record the current selected quote and purchase state before confirming construction. Do not use the lower sidebar number as a guaranteed debit or infer a discount formula from the difference. This site’s Small Refinery record leaves the single cost field unknown and therefore does not calculate a verified payback period for it.

Prices from separate recordings are a different kind of uncertainty. For example, the September 29 and 30 Supermarket records belong to different sessions. Their differences alone do not prove a bug or a developer balance change.

Is the 20-second volley notice a known bug?

The October 15 recording at 3:38 explicitly tells the player to wait 20 seconds before another 100 projectiles. That is a visible restriction, not evidence that launching is broken. A zero-ready counter likewise needs to be distinguished from selected targets and airborne projectiles. The creator’s proposed 99-projectile bypass has not been established by a controlled timing sequence, so it is not included as a confirmed exploit or workaround.

How should a new issue be documented?

Keep the date or version, exact building or product name, steps leading to the state, the observed and expected result, and a screenshot that includes the relevant counters. State whether the sequence can be repeated and whether a proposed workaround actually changed the result. Avoid deleting a city or repurchasing a building merely to test an unverified forum claim.

Where should you go next?

• Troubleshooting current blockers
• Strip Mall attributes and staffing conflict
• Refinery records and fuel planning