- Brick Buddies co op is designed around two-player couch cooperation and shared construction tasks.
- Core objective: Move blocks from the truck, clear sheep, and stack floors on the foundation.
- Best control habit: One player manages movement while the other focuses on positioning and release timing.
- Main challenge: Swinging blocks must be aligned carefully before they are dropped.
- Performance tip: Build quickly, but protect the structure from unstable landings and blocked routes.
Brick Buddies co op: How the Two-Player Format Works
Brick Buddies is a cooperative tower-building game built around local, couch-based teamwork. The available demo presents two players working together to collect construction blocks, move them across a worksite, and place them onto a growing tower. The game’s humor comes from turning simple coordination into a series of difficult, often chaotic decisions.
The co-op format assigns both players responsibility for the same construction operation. Rather than building separate structures, the team shares the same objective, the same blocks, and the same time pressure. A misplaced release can affect the entire tower, while poor communication can leave one player swinging in the wrong direction.
Video Highlights:
- Two players coordinate a shared crane-like construction process.
- Sheep can block the truck and interrupt the material route.
- Blocks must be aligned over a foundation before release.
- Career-style objectives can require different floor types and total-floor targets.
- The demo supports controllers and is designed for couch co-op play.
The most important rule is to decide who is handling movement and who is calling the drop. Both players may have control over the operation, but trying to correct every movement at once creates unnecessary swings. Establishing clear roles makes the tower easier to stabilize.
| Co-Op Element | What It Means | Recommended Habit |
|---|---|---|
| Shared construction | Both players contribute to one tower | Agree on the target before moving |
| Block transport | Materials come from the truck | Keep the route clear before grabbing blocks |
| Swing control | A suspended block can drift or rotate | Make small corrections instead of long inputs |
| Release timing | The block must land on the structure | Call “drop” only after movement settles |
| Floor objectives | Some stages require specific floor types | Check the requirement before choosing a block |
Mover
- Controls the block’s general direction
- Keeps the load aligned with the tower
- Uses short, measured adjustments
Spotter
- Watches the landing position
- Calls forward, backward, higher, or lower
- Confirms when the block is ready to release
Route Keeper
- Clears sheep from the truck path
- Checks available materials
- Prevents wasted movement between placements
Assign one player as the primary mover and the other as the spotter. Swap roles between attempts if the first arrangement feels uncomfortable, but avoid issuing conflicting movement commands at the same time.
Tower-Building Workflow and Material Control
Every construction attempt follows a repeatable loop: collect a block, clear the route, move it toward the tower, position it over the foundation, and release it. The process sounds straightforward, but the suspended load can swing, rotate, or sit too high for accurate placement.
The truck is an important part of the route. Sheep can interfere with access, so clearing them is not just a cosmetic task. If the truck cannot move into position, the team may lose time or be forced to work from an awkward angle. Handle the route before committing to a complicated lift.
| Phase | Primary Goal | Common Risk | Better Approach |
|---|---|---|---|
| Clear | Remove sheep from the truck route | Materials remain inaccessible | Open the path before lifting |
| Collect | Grab the correct block | Wrong block wastes time | Confirm the floor requirement first |
| Transport | Move the block across the site | Swinging creates drift | Use gradual directional inputs |
| Align | Center the block over the structure | Edges can miss the foundation | Use the tower as the visual reference |
| Release | Drop the block safely | A high drop can destabilize the stack | Lower slowly and wait for movement to settle |
Use the foundation as the visual anchor for every placement. A block that looks close from one player’s view may still be offset from the other player’s perspective. The spotter should describe corrections in simple terms, such as “slightly left,” “forward,” or “lower.” Long explanations are difficult to follow while the block is moving.
The team should also avoid rushing after a successful placement. A block may appear secure while the structure remains unstable. Give the load time to stop swinging, then confirm that the new floor has counted before moving on. This is especially important when a stage tracks floors, stars, or required categories.
Do not release a block simply because it touches the tower. A partial landing may fail to count, block the next route, or make later floors harder to place.
Inspect the Requirement
Before moving a block, identify the target floor count and any visible floor-type requirement. This prevents the team from spending time on a block that does not advance the objective.
Clear the Truck Route
Move sheep away from the truck and make sure the next material can travel toward the foundation. A clear route gives both players more room to correct the load.
Choose Movement Roles
Decide who gives movement input and who watches alignment. The spotter should provide short, direct instructions instead of several corrections at once.
Lower Before Releasing
Bring the block down gradually, wait for excessive swinging to stop, and confirm that its center is over the intended landing area.
Confirm the Floor Count
Check that the placement registered before collecting another block. If the floor did not count, reassess the landing rather than assuming the next block will fix the mistake.
| Control Problem | Likely Cause | Correction |
|---|---|---|
| Block swings too far | Large or conflicting inputs | Use brief taps and pause between corrections |
| Block is too high | Lift continues during alignment | Lower before making final horizontal adjustments |
| Player cannot reach the target | Load is positioned at a poor angle | Reposition the crane or route before releasing |
| Truck stops moving | Sheep block the path | Clear the obstruction before collecting another block |
| Placement does not count | Block is off-center or on the wrong surface | Recenter it and verify the required floor type |
Timing, Balance, and Star Performance
Brick Buddies rewards more than simply reaching the top of a tower. The demo includes star-based performance goals, and faster attempts appear to be important when aiming for a stronger result. However, speed should support accuracy rather than replace it.
A rushed placement can create a chain of problems. The block may land outside the intended area, the truck may become trapped, or the next player may have difficulty reaching the correct position. Restarting can sometimes be more efficient than trying to recover a badly aligned structure, but teams should first learn which mistakes are recoverable.
Accuracy First
- Center blocks over the landing area
- Avoid high-impact drops
- Protect the next placement
Speed Second
- Clear sheep early
- Plan the next block during transport
- Reduce unnecessary repositioning
Recovery Control
- Stop swinging before correcting
- Save usable blocks when possible
- Restart when the route becomes inefficient
The strongest rhythm is “move, settle, place.” During the movement phase, make broad corrections only when necessary. During the settling phase, stop adding inputs and let both players observe the block. During the placement phase, use small adjustments and a controlled release.
| Performance Focus | Strong Result | Weak Result |
|---|---|---|
| Completion speed | Efficient route and limited pauses | Repeated repositioning |
| Placement quality | Floors land near the intended center | Edges or unstable contact |
| Route management | Sheep cleared before they interfere | Truck repeatedly blocked |
| Communication | One clear movement caller | Both players give simultaneous commands |
| Recovery | Mistakes are assessed quickly | Team continues after the structure becomes impractical |
Treat every attempt as a route-planning exercise. The fastest teams are not necessarily moving constantly; they are reducing corrections, preventing blocked paths, and preparing the next placement early.
A useful practice method is to separate learning runs from score runs. During a learning run, test how far the block can move, how quickly it swings, and how much correction is needed near the foundation. During a score run, use the route that produced the fewest pauses and failed placements.
Do not judge the team only by whether the tower reaches the required height. If the stage asks for particular floor categories, a tall structure can still fail the objective. Read the requirement, select blocks deliberately, and keep track of which categories have already counted.
Couch Co-Op Preparation Checklist
Brick Buddies works best when both players can communicate quickly and see the construction area clearly. Because the game focuses on shared control, the physical setup around the screen matters almost as much as the in-game plan.
Before starting a serious attempt, agree on a vocabulary. “Left” and “right” can become confusing when players are facing different directions, so terms such as “toward the truck,” “toward the tower,” “higher,” and “lower” are often easier to understand. Keep instructions short and confirm when a movement has finished.
Before the First Attempt:
- Confirm that both players have a working controller
- Choose a mover and a spotter before lifting the first block
- Clear sheep from the truck route
- Read the required floor count and floor categories
- Agree on simple movement and release callouts
| Preparation Item | Why It Matters | Suggested Check |
|---|---|---|
| Controller check | Input problems can look like coordination errors | Test movement, lift, rotate, and release |
| Player roles | Clear responsibility reduces conflicting commands | Name one mover and one spotter |
| Screen position | Both players need a reliable view | Sit where the tower and load are visible |
| Callout language | Fast corrections require concise terms | Use consistent direction words |
| Restart plan | Failed attempts can waste time | Decide when recovery is no longer worthwhile |
For new teams, start with a slower objective rather than immediately chasing the best star result. Learn how the block responds, how sheep affect the route, and how much space is needed to align the load. Once the basic loop feels comfortable, focus on faster transitions between blocks.
The available material identifies Brick Buddies as couch co-op for two players and controller-supported. Remote play may depend on connection quality, so treat it as a possible alternative rather than the primary setup.
When frustration rises, pause and reset the roles. Many failed attempts come from both players trying to solve the same problem simultaneously. A short role reset can restore communication without requiring a full restart.
Brick Buddies co op FAQ
Q: How many players does Brick Buddies co op support?
The available demo is presented as a two-player couch co-op experience. Both players work together on the same tower rather than constructing separate buildings.
Q: What is the main objective in Brick Buddies?
The team collects blocks from a truck, clears sheep from the route, and stacks the blocks onto a foundation to meet floor and performance requirements.
Q: What is the best role split for two players?
One player should usually manage the block’s movement while the other watches the landing position and gives short alignment instructions. This reduces conflicting inputs.
Q: Why did a placed block fail to count?
The block may have landed off-center, touched the wrong part of the structure, or failed to match the required floor category. Confirm the requirement before attempting the next placement.
Use the first few attempts to learn the tower’s spacing and the block’s movement behavior. Once the route is familiar, focus on cleaner communication, controlled releases, and fewer unnecessary corrections.