- Ductworks project 2 is your second build: a multi-section duct system with corners and branches.
- Core loop: plan the route, place sections, connect transitions, test airflow, then expand.
- Multiplayer roles: split planner, builder, and tester among up to 20 players per server.
- Golden rule: change one part of the layout at a time so problems stay traceable.
- Verified stats: 806K+ visits, 90.9% rating, released September 2026 on Roblox.
Planning Your Ductworks Project 2
Your second build in DUCTWORKS should move beyond the single straight route you likely tested first. A project 2 build adds corners, transitions, and one or two branches, which is where air physics becomes interesting and where most construction mistakes appear.
A connected duct system only moves air along a continuous path. Planning the source, the main route, and the destination before placing any parts prevents the most common project 2 failure: a layout that looks finished but never moves air end to end.
Project 1 vs Project 2 Comparison
| Aspect | Project 1 (First Build) | Project 2 (Second Build) |
|---|---|---|
| Route shape | Single straight line | Route with corners and transitions |
| Branches | None | 1-2 tested branches |
| Testing | One final check | Test after every structural change |
| Players | Solo is fine | Multiplayer roles recommended |
| Difficulty | ★★☆☆☆ | ★★★☆☆ |
| Main risk | Misaligned openings | Untested branches disrupting the path |
Distribution Build
- Main route feeds multiple destination areas
- Balanced branches tested one at a time
- Best for learning air distribution
Turned Route Build
- Same endpoints, multiple bends
- Compare against a direct path
- Best for mastering transitions
Expansion Build
- Start small, add sections per test round
- Record results at each stage
- Best for understanding system growth
Project 2 Step-by-Step Build Flow
Follow this sequence to keep your second build debuggable from start to finish. The workflow mirrors how experienced sandbox builders work: small verified stages instead of one large untested structure.
Define the Route
Decide where air starts, where it travels, and where it ends. Sketch the main path and mark which areas will receive airflow. Reserve extra space at every planned turn.
Place the Main Duct Sections
Use the bottom control bar to place a continuous line of ductwork along the planned route. Keep adjacent sections aligned so each connection can be inspected later.
Add Corners and Transitions
Build each turn individually and inspect both sides of the corner. The incoming and outgoing sections must meet the transition correctly, or air will not continue through the system.
Test Before Branching
Run the airflow test on the completed main path. If air does not travel correctly, check the most recent connection and direction change first before rebuilding anything.
Add Branches One at a Time
With the main route confirmed, add a single branch, test again, and compare the result. Repeat for each additional branch so every change has an observable effect.
Avoid adding several untested branches at once. When multiple new sections are added together, you cannot tell which connection changed the airflow behavior, and troubleshooting becomes guesswork.
Airflow Testing and Common Errors
Airflow in Ductworks depends on three things: the route being fully connected, the direction of each section, and how turns and branches are arranged. A repeatable test routine turns debugging from frustration into a checklist.
Error Diagnosis Table
| Symptom | Likely Cause | Fix | Priority |
|---|---|---|---|
| No air movement at all | Disconnected sections or gap | Inspect every connection along the route | High |
| Air stops mid-route | Misaligned corner transition | Realign both sides of the affected turn | High |
| Airflow behaves oddly | Section facing wrong direction | Rotate or adjust the section, retest | Medium |
| One area gets no air | Branch added without testing | Isolate the branch and retest it alone | Medium |
| System worked, now fails | Latest structural change | Undo or adjust the newest modification | High |
Inspect the source, follow the main route, check every transition, then review branch points. When a test fails, adjust the latest change first instead of rebuilding the whole system.
Test Frequency by Build Stage
| Build Stage | Test After Change? | What to Verify |
|---|---|---|
| Main path placement | Yes | Sections meet with no gaps |
| Each corner added | Yes | Both sides connect to the transition |
| Direction adjustments | Yes | Air travels the intended way |
| Each new branch | Yes | Distribution matches expectation |
| Cosmetic changes | Optional | Structure still connected |
Multiplayer Roles and Collaboration
The current game listing presents DUCTWORKS as a multiplayer experience, and public statistics show a maximum server size of 20 players. A project 2 build is an ideal group activity because construction and testing can be split cleanly between players.
Multiplayer Role Table
| Role | Responsibility | Best Practice |
|---|---|---|
| Layout Planner | Maps the main route and connection points | Mark the route before any building starts |
| Builder | Places and connects duct sections | Follow the mapped route section by section |
| Tester | Checks airflow and records results | Compare results between design versions |
| Final Reviewer | Approves changes before expansion | One designated player signs off each stage |
Public API data captured on 2026-10-08 shows Ductworks at 806K+ visits, roughly 1.2K concurrent players, a peak of about 2.4K, and a 90.9% rating. Server capacity and multiplayer rules can change with updates, so verify current limits on the official game page.
Group Experiment: Routes
Build a direct route and a turned route between the same endpoints, then compare airflow behavior between them.
Group Experiment: Branches
Test a single extended branch against a balanced multi-branch layout and record distribution at each destination.
Group Experiment: Expansion
Add one duct section per test round while one player documents the result after every stage.
Project 2 Completion Checklist
Project 2 Milestones:
- Main route placed and visually continuous
- Every corner tested on both sides
- Airflow confirmed on the main path
- First branch added and tested individually
- Retest completed after every structural change
Once your project 2 build passes every milestone, larger HVAC layouts, multi-room distribution systems, and more ambitious sandbox experiments become practical next steps. The staged build-and-test habit you practiced here scales to any size of duct network.
Related Page Directory
| Page | What It Covers | Best For |
|---|---|---|
| Beginner Guide | Interface, first build, core concepts | Players starting project 1 |
| Controls Guide | Bottom control bar, PC and mobile inputs | Input questions |
| Airflow Guide | Air physics and testing routines | Deeper mechanics study |
| Multiplayer Guide | Server play and cooperative building | Group projects |
FAQ
Q: What is a Ductworks project 2 build?
It is your second construction in Ductworks: a duct system that goes beyond a single straight route by adding corners, transitions, and one or two tested branches while keeping the airflow working end to end.
Q: How many players can join a Ductworks project 2 build?
Public statistics show a maximum of 20 players per server. For a collaborative build, splitting planner, builder, and tester roles keeps the project organized even with a smaller group.
Q: Why does my connected layout not move air?
Check for gaps between sections, a section facing the wrong direction, or a misaligned corner transition. Adjust the most recent structural change first, then rerun the airflow test before making other modifications.
Q: Are there codes or game passes for Ductworks?
No officially confirmed redeemable codes are listed for Ductworks. Public information indicates game passes such as Creator+, Custom Appearance, and Custom Playlist have appeared, but verify their exact effects in-game before purchasing.