A useful place to start
Build and Conquer Wiki is an unofficial reference for English-speaking Roblox players. Use the directory above to find a specific question without searching through unrelated pages. Each guide has a separate topic, and every page links to three related resources. If you are new, begin with the beginner’s guide; if you are returning, check the update log before comparing older information with the current game.
The game identified in this site’s brief is Build and Conquer [V0.1], developed by The Slop Company. It is listed as Strategy, with eight players per server. In October 2026, it is in beta and receives frequent updates. These are the only game facts supplied for this launch. They provide context, but they do not establish how any particular mechanic works.
Pick the page that matches your question
The money guide is the place for a checked explanation of earning money. The trucks guide is reserved for a verified way to obtain trucks. Both currently separate their unanswered gameplay questions from general advice about checking a guide. A page title identifies what the page covers; it does not mean its procedure has already been tested.
The civilian and military building pages use the same comparison columns. This makes entries easier to compare after their names, roles, costs, and unlock conditions have been confirmed. Empty entries are marked as awaiting verification. Treat an empty cell as unknown, never as a free cost, no requirement, or an unavailable feature.
The codes page keeps active and expired lists separate. Neither list currently contains verified entries. This is a verification status, not a claim that codes do or do not exist. The update page follows the same rule: an empty patch log does not mean the developer has made no changes.
Read the status before the advice
Look for the editorial review date near the top of each inner page. That date describes when the page text was reviewed. A game test needs its own evidence and date. A fresh editorial date alone cannot tell you whether an instruction works in your current session.
When a procedure is eventually added, compare its stated game version with the version you are playing. If the wording or interface differs, stop treating the procedure as a match. Note the difference before following any further instruction. This is especially useful while the beta is changing frequently.
Help keep the reference accurate
A useful correction identifies the page, the claim in question, and what you observed. Include the date and version if you can establish them, and describe the relevant interface text in your own words. Keep account details and private messages out of your report. The About page explains how contributions will be reviewed and why unverified claims stay out of the guides.
This wiki aims to give you a clear route to an answer and a clear signal when that answer is still missing. Until a topic is checked, use the visible verification notices to decide whether the page can support your next move.