Planet Zoo 2 Merge Groups: Blueprint Tutorial & Troubleshooting

Stuck on Planet Zoo 2 merge groups when your barrier, shelter, and foliage assets refuse to combine into a single blueprint? This Planet Zoo 2 merge groups walkthrough explains the actual selection pipeline, the group-snap toggle that fixes most failed merges, and the troubleshooting steps to follow when a blueprint is not working as expected.

What Planet Zoo 2 Merge Groups Actually Do

Merge groups let you bundle several building pieces, scenery props, foliage clusters, and habitat barriers into a single named group that can be saved, moved, duplicated, and ultimately published as one blueprint. According to the official Planet Zoo 2 player guide on Blueprints and Workshop, the system was redesigned so that grouped objects retain their relative positions even when the entire group is rotated or lifted onto terrain, which is what makes modular zoo construction viable at scale.

In practice, a merge group is just a saved selection with a name. The underlying pieces are still individual objects, but the game treats them as one unit for selection, copying, and blueprint capture. This is why a habitat viewing shelter, a set of educational signage boards, and a small grove of decorative trees can behave as a single draggable item once they have been merged.

Players run into trouble when they expect a merge to behave like a single mesh object. It does not. A merge group is a logical container, not a fused geometry, which is why individual pieces inside the group can still be clicked, deleted, or edited through the detailed object panel. Understanding that distinction solves about half of the confusion reported on community forums about Planet Zoo 2 blueprint not working scenarios.

The Three Group States

Before troubleshooting why your Planet Zoo 2 merge groups commands refuse to behave like a single unit, it helps to know which group state your selection is actually in at the moment you trigger the merge. The build system distinguishes between three layers — a raw shift-click multi-selection, a named group created via the main toolbar's group button, and a saved blueprint stored in the local library — and each layer passes through the merge pipeline with a different set of edit permissions and Workshop eligibility, which is precisely why a freshly marquee-boxed habitat will not snap together the same way a named group from the group panel will.

If your selection is only a multi-selection, none of the merge commands will behave like a persistent group, which is the most common reason newcomers think that Planet Zoo 2 merge groups are broken. A shift-click marquee of thirty barrier pieces plus two viewing shelters registers as a live multi-selection, not a named group from the group panel, so merging it just produces a temporary union that dissolves the moment you click elsewhere on the build grid. To get a truly persistent group you have to first press the main toolbar's group button to commit those objects as a named group entry, then run the merge command from inside the group panel — only then will the result survive saving as a Planet Zoo 2 blueprint and become eligible for the Workshop upload flow.

Step-by-Step Planet Zoo 2 Blueprint Tutorial for Grouping

The official Planet Zoo 2 Frontier Workshop page confirms that the merge workflow follows a fixed order: select, group, name, save, optionally publish. Skipping a step is the single biggest cause of broken merges, because each step builds on the previous one.

Step 1: Build With the Grid in Mind

Before you click anything in the group menu, lay out your pieces on a consistent grid. Planet Zoo 2 uses a 1-meter build grid by default, and the group system stores the offsets between objects relative to the grid, not the world origin. If your foliage, shelter, and barrier are placed on mixed grid sizes, the merged group will visibly snap to the closest grid intersection the moment you move it.

If you are unsure about your current grid, open the build settings and confirm the grid size is set to 1m for scenery and 0.5m for fine detail props. Players who skip this step usually report that their merged group "explodes apart" when they try to move it, which is a grid offset issue, not a true merge failure.

Step 2: Select Everything You Want to Group

Use Shift + left-click to add pieces to your selection, or drag a marquee box around the area. Hold Shift while dragging to keep the marquee behavior, otherwise it will deselect as it moves. According to the official building your zoo guide, you can include scenery, props, foliage, and most facility items in the same group, but you cannot include live animals, guests, or staff members.

A useful trick is to hide the terrain and barrier layers first, so the marquee does not accidentally pick up a huge chunk of invisible terrain. Players who skip this often end up with a "merged" group that contains hundreds of terrain tiles, which then refuses to save as a blueprint because of the hidden object count.

Step 3: Press the Group Button

Once everything you want is selected, press the Group button in the main toolbar or use the keyboard shortcut G (default binding). A small dialog will appear asking you to name the group. Give it a descriptive name such as Tropical Aviary Shelter or Boreal Bear Viewing Platform, because this name becomes the blueprint name when you publish it.

If the Group button is greyed out, your selection is invalid. Common causes include selecting a guest, selecting a barrier segment that is part of a habitat instead of a free-standing one, or selecting more than the engine's soft cap of objects (reported by players to sit around 5000 items in the current build). The game will not warn you about the cap; it will simply refuse the action.

Step 4: Verify the Group Snaps Together

After naming the group, click somewhere empty to deselect, then click on one of the pieces inside the group. The entire group should now highlight as a single unit. Drag it slightly to test. If the group moves as one piece, the merge is working. If the pieces slide apart, you have a Planet Zoo 2 blueprint not working case, usually caused by mixed grid sizes or an unanchored prop in the middle of the group.

Step 5: Save to Your Local Library

Right-click the highlighted group and choose Save as Blueprint, or use the Library panel and drag the group into it. Saving creates a permanent local copy that survives even if you delete the original pieces from your zoo. This is also the step where you can tag the blueprint with category, description, and a thumbnail, all of which are visible on the Workshop listing.

If you want to learn how this pipeline fits into the broader save and share flow, the Planet Zoo 2 blueprint guide covers the full library, share-code, and folder system in much more detail.

Troubleshooting Planet Zoo 2 Blueprints When the Merge Fails

Even with the right steps, Planet Zoo 2 blueprints troubleshooting often comes down to a handful of recurring culprits. Community testing on the official Workshop and player Discord suggests that roughly 80% of "merge broken" reports fall into one of the categories below.

Group Is Recognized but Won't Save

The group highlights correctly, but Save as Blueprint is greyed out. This almost always means one piece in the group is anchored to something the blueprint engine cannot serialize, such as a habitat terrain stamp, a water plane, or an animal enrichment item that references a live animal ID. The fix is to remove the offending piece, regroup, and try again. Players report that a careful rebuild with only scenery, props, foliage, and facility items always succeeds.

Group Saves but Refuses to Place

When you load the saved blueprint from the library, the cursor shows the ghost preview but clicking does nothing. The most common cause is that the blueprint was saved in a different grid size than the current build grid, or the terrain heightmap at the original save location no longer exists. Switch grid size to match, flatten the target terrain, and try again. If placement still fails, the blueprint may be clipped against a barrier or path, so move a few meters and retry.

Group Merges but Pieces Drift on Move

This is a Planet Zoo 2 blueprint not working classic. You group pieces, drag the group, and the individual items slowly drift apart over distance. The cause is sub-grid placement: one or more pieces in the group were placed between grid lines, so the merge stored the offset as a fractional value. Over long moves, floating-point rounding accumulates and the drift becomes visible. Fix by snapping every piece to the grid, re-grouping, and re-saving.

Group Exceeds the Object Cap

The engine will not always tell you when a group is too large. Symptoms include a hang on save, a crash to desktop, or a blueprint that saves but fails to load with a "corrupted blueprint" message. Community testing puts the practical ceiling at around 3000 to 4000 objects per blueprint for stable sharing; above that, performance degrades for whoever downloads it. The Planet Zoo 2 pre-built zoos guide explains how to split oversized creations into modular packs that link together on placement.

Using the Workshop to Find Featured Blueprints and Group Examples

Once your local library is working, the Frontier Workshop is the natural next stop, both for inspiration and for testing whether your groups publish correctly. According to the Planet Zoo 2 Steam store page, Workshop integration is built directly into the game, and featured creations are promoted on the official site and inside the in-game browser.

What "Featured" Means in Planet Zoo 2

Featured blueprints are the creations that the Planet Zoo 2 team has hand-picked and promoted on the official Workshop landing page. At the time of writing, examples trending on that page include the Stone Cottage Trade Centre, the Trout Bridge, and the Botanical Bird Conservatory with its Tropical Aviary variant. These all share one trait: they were saved and published as proper merge groups rather than as loose multi-selections, which is why they download as a single draggable object.

Studying a featured blueprint is one of the fastest Planet Zoo 2 workshop tutorial shortcuts, because you can subscribe to it, place it in your zoo, and immediately ungroup it to see exactly how the original creator built and bundled the pieces. That reverse-engineering loop is how most experienced builders learn advanced group layouts, including how to nest multiple sub-groups inside a master group for very large creations.

How to Publish Your Own Merge Groups

From the library panel, select a saved blueprint, click Publish, fill in the title, description, category tags, and a 1080p thumbnail, then confirm. The blueprint enters a short moderation queue before appearing on the Workshop. Community reports suggest that blueprints with clean group structures, sensible category tags, and a single preview image are approved faster than bundles with multiple variants or no description at all.

If you want your blueprint to be considered for the featured rotation, the team's published guidance emphasizes that submissions should use merge groups rather than loose objects, include a detailed description of the intended use (habitat type, climate, animal size), and respect the 5000-object soft cap. Featured status is not permanent; the featured list rotates, so even promoted creations can be replaced as newer community work is highlighted.

Workshop Categories Worth Knowing

For a deeper tour of the in-game Workshop browser and the search filters that surface featured blueprints, the Planet Zoo 2 workshop creations guide walks through the navigation, the grid placement toggles, and the share-code system in detail.

Advanced Tips: Building Merge Groups That Survive Sharing

A merge group that works perfectly in your own zoo can break for anyone who downloads it, and Planet Zoo 2 blueprints troubleshooting on the receiving end is much harder than on the creator's end. The following practices reduce that risk significantly, based on patterns seen in the most-downloaded featured blueprints.

Avoid Live-Anchor Items

Anything that references a specific animal, a specific staff member, or a specific guest ID will not survive a transfer. Enrichment items, name plates with embedded IDs, and signage that auto-populates from a specific habitat all fall into this category. Replace them with neutral, ID-free versions before grouping, and the blueprint will load identically on every machine.

Use the Group Origin Intentionally

When you create a named group, the game stores an origin point that becomes the blueprint's placement handle. By default the origin is the center of the bounding box, but you can right-click the group and choose Set Origin to place it on a corner, a door, or a path junction. Builders who think about the origin up front save themselves hours of fiddly rotation later, because the blueprint always lands on the origin when placed.

Keep Nested Groups to Two Levels

It is technically possible to merge a group that already contains other groups, and the engine supports it, but community testing shows that three or more levels of nesting start to confuse both the save system and the placement system, with some nested groups silently dropping during load. Two levels is the practical sweet spot: a master group containing a few sub-groups for movable sections (such as a separate foliage cluster you might want to remove when placing on a smaller plot).

Match Your Grid Before Publishing

Before you publish, switch grid size back and forth, place a ghost copy of the blueprint, and confirm the pieces align. This catches sub-grid drift that you might not notice in your own zoo but becomes obvious on a different terrain mesh. A 30-second self-check at this stage eliminates roughly half of the "does not match preview" complaints that show up in the Workshop comments.

Tag and Describe for Search

Featured blueprints almost always include accurate category tags, a short description, and a clear title. Search on the Workshop is keyword-driven, so a blueprint tagged "shelter, foliage, tropical" will surface for many more queries than one with no tags. Treat the metadata as part of the build, not an afterthought.

Common Mistakes That Make Planet Zoo 2 Merge Groups Feel Broken

After a year of player reports on the Planet Zoo 2 official forums and Steam community hub, a handful of recurring mistakes account for the majority of "my merge groups don't work" threads, particularly around blueprint import, habitat adjacency, and the new group-tag system introduced in the v1.2 patch. Recognizing them early, before you invest hours placing scenery and barriers, saves significant frustration and prevents the need to re-import large workshop blueprints that fail silently due to filter mismatches.

Mistake 1: Treating Multi-Selection as a Group

Drag-selecting several items does not create a group. It creates a temporary multi-selection that disappears the moment you click empty space. New builders often save this multi-selection as a blueprint and are surprised when the pieces are loose after loading. The fix is always to press G first, name the group, and only then save.

Mistake 2: Including the Terrain

Marquee-selecting across a large area almost always picks up a terrain tile or two, even if the terrain is hidden. The resulting group then refuses to save as a portable blueprint, because terrain is local to the zoo. Use a tighter marquee, or hold Alt while marquee-selecting to exclude terrain.

Mistake 3: Forgetting That Paths Are Special

Paths can be grouped, but a group containing a path node can have unexpected effects on connected paths when placed. If your goal is a portable shelter, do not include the path leading to it; build the path separately, and let placement logic connect them after the group lands.

Mistake 4: Saving Across Patch Boundaries

If you built a group on patch 1.2 and your friend is still on patch 1.1, the blueprint may not load cleanly. Always publish a version note in the description, and subscribe to your own blueprint to test it on a fresh sandbox save before recommending it.

Mistake 5: Assuming Rotation Is Free

A merged group will rotate, but only around its origin. If the origin is in an awkward spot, the entire group will swing around it like a clock hand. Set the origin to a logical anchor (a door, a viewing window) before saving, and rotation will behave intuitively.

Frequently Asked Questions

Why is my Planet Zoo 2 blueprint not working after I save it?

The most common cause is that the selection was never turned into a named group, so saving captured a loose multi-selection instead. Re-select the pieces, press G, name the group, then save as blueprint. According to the official player guide, only named groups survive the save/load cycle as a single draggable unit.

How do I fix Planet Zoo 2 blueprints that load but refuse to place?

Match the current grid size to the size used when the blueprint was created, flatten the target terrain, and move a few meters away from any barrier or path. If placement still fails, the blueprint may include an item that is not yet enabled in your game mode, which can be confirmed by looking at the missing-object list in the library panel.

Can I merge groups that already contain other groups?

Yes, the engine supports up to two levels of nesting in practice. Beyond that, some nested groups can drop during load, especially after cross-patch transfers. If you need a very large build, split it into several smaller merge groups and place them side by side, which is the pattern used by most featured habitat blueprints.

What is the object limit per Planet Zoo 2 merge group?

There is no hard public limit, but community testing puts the practical ceiling at around 3000 to 4000 objects for stable sharing. Larger groups may save, but they tend to underperform on the receiver's machine, and some save attempts crash. Split oversized creations into modular packs linked by placement.

Where do I find Planet Zoo 2 featured blueprints to study and subscribe to?

The official Frontier Workshop page lists the current featured creations, and the in-game Workshop browser mirrors that list. Featured blueprints are the best learning material because they are nearly always saved as proper merge groups, which makes them easy to ungroup and inspect.