Unity: prepare one pickup prefab for many places
Create a reusable collectible model and learn the difference between changing the shared asset and changing one placed instance.
First Play Studios · Edition 1 · Updated November 14, 2026
Three pickup placeholders share one prefab while a deliberate per-instance change remains understandable.
Before you start- An existing Unity 6 3D project
- Understand GameObjects, child objects, and the Inspector
In this guide
Decide what should be shared
A prefab stores a configured GameObject and its components and children as an asset. Instances placed in scenes refer to that asset. This makes a useful home for a collectible’s visual structure, instead of building each copy independently.
Our prototype collectible is a seed pouch made from a small sphere and a cube tied at its top. This lesson covers reuse and editing. It deliberately does not award inventory, detect a player, or save progress; a prefab is a reusable structure, not automatic collection logic.
Make the template before multiplying it
Create an empty GameObject called SeedPouch at scale (1, 1, 1). Add a Sphere child called Body and a small Cube child called Tie. Adjust the children until the silhouette reads as a pouch. Keep the root at a sensible origin, such as the middle of its base, so placing it on a table is predictable.
Create a Prefabs folder in Assets. Drag the configured root from the Hierarchy into that folder to create the prefab asset. Place three instances from the asset into the scene and spread them apart. The objects should share construction but have their own placement.
Trace where a change belongs
Open the prefab asset for editing and make the Tie slightly larger. Save the change and inspect the three instances. Then deliberately change one instance’s Body scale and inspect its overrides. An override represents a difference on that instance; it is not a new independent prefab.
Before applying an override back to the asset, ask whether every pouch should inherit it. Keep a special local change local. Revert an accidental change through the prefab controls rather than trying to remember the previous numbers. This habit becomes valuable when a project has many repeated doors, enemies, and rewards.
Prove that shared and local edits are different
- Create the SeedPouch asset and place three named instances: PouchLeft, PouchMiddle, and PouchRight.
- Edit the shared Tie shape and observe all three instances.
- Change only PouchMiddle’s Body scale. Identify the override in its Inspector.
- Revert that local override and check that the middle pouch returns to the shared shape.
- Describe one future property that should be shared and one that should vary by placement.
Check your result.
- All three objects remain linked to the same prefab asset.
- A shared visual edit reaches the unmodified instances.
- The local experiment can be reverted without rebuilding the object.
Common mistakes to watch for.
- Duplicating an ordinary scene object does not by itself create a prefab asset.
- Applying a local override can change other instances; inspect the effect first.
- Do not mistake a prepared pickup model for a working collection system.
Keep the conversation useful.
I’m using Unity 6 with a SeedPouch prefab and three instances. Help me understand this specific shared edit or instance override. Ask what I want every instance to inherit before recommending Apply or Revert. Give me a small comparison test and keep collection logic out of this step.
Sources & version notes.
Unity 6, checked against the 6000.0 prefab manual. Authoring exercise only; not run in the editor and not a complete collectible mechanic.
Further reading from the original documentation:
Practice times are estimates. Software-specific exercises are documentation-based unless their version note says otherwise.A question or a small win?
Tell the workshop what happened when you tried this guide. Ask for a useful next step, or share something you got working.
See discussions about this guide We’ll include the guide link in your draft. Sign in to post, then add your own question or progress before sharing.