The fossilized bird in Cobblemon almost always "doesn't work" for one of two reasons: you're trying to revive it alone when it needs a second fossil paired with it, or your Resurrection Machine isn't fully assembled or properly loaded. Fix those two things first and you'll solve the problem 90% of the time.
Fossilized Bird Not Working in Cobblemon Troubleshooting
What the fossilized bird is supposed to do in Cobblemon

Cobblemon's fossilized bird is an item you obtain by brushing suspicious sand or gravel at fossil dig sites. It represents a fragment of an ancient bird-like Pokémon, and the whole point of finding it is to eventually revive it into a living creature through the Resurrection Machine. Specifically, the fossilized bird revives into either Dracozolt or Arctozolt, depending on which second fossil you pair it with. Think of it the same way paleontologists piece together partial fossil records to reconstruct an extinct animal: the game requires you to combine two fossil halves to get a complete Pokémon.
This design mirrors the real-world idea that fossil evidence is rarely complete. Just as scientists studying extinct birds often work from fragmentary remains, the fossilized bird in Cobblemon is only half the picture. You need the right companion fossil to fill in the rest. That companion requirement trips up most players who report "nothing happening."
The Resurrection Machine itself is a three-block multiblock structure made from a Fossil Analyzer, a Restoration Tank, and a Data Monitor. When assembled correctly, it plays an electrical sound to confirm successful construction. You insert your fossils and organic materials into the tank, and after 12 minutes an embryo finishes growing. At that point you can right-click the tank with a Poké Ball in your main hand to add the revived Pokémon to your party, or break the tank to release it as a wild Pokémon.
Quick diagnosis: why it's probably not working
Before diving into deep troubleshooting, run through these most common causes quickly. The majority of "fossilized bird not working" reports in the Cobblemon community trace back to one of these:
- You're placing only the fossilized bird into the machine without a second fossil. It cannot revive alone.
- The Resurrection Machine isn't fully assembled. If you didn't hear the electrical confirmation sound, it's not a valid multiblock yet.
- You don't have enough organic material in the Restoration Tank. The tank needs organic materials totaling a value of 64 in addition to the fossils.
- You're on a server and you didn't start the revival yourself. Only the original player who initiated the process can immediately claim the resulting Pokémon.
- A datapack on your server or modpack overrides the fossil JSON files with incorrect item IDs or results, silently breaking the system.
- You're running the wrong Cobblemon version or loader build (Fabric vs. Forge vs. NeoForge mismatch), so the fossil mechanic doesn't load correctly.
- You're using a different mod's fossil machine, such as one from Fossilmon or another addon, instead of Cobblemon's official Resurrection Machine.
Checklist before anything else

Go through this list in order. Each item is a real failure point that has caused the exact symptom you're experiencing.
Version and loader
- Confirm your Cobblemon mod version matches the version your server or modpack expects. Check CurseForge or Modrinth for the exact file you installed.
- Confirm your mod loader matches the Cobblemon build you downloaded. Cobblemon has separate builds for Fabric and NeoForge/Forge. Installing the wrong one causes mechanics to fail silently.
- If you're on a modpack, check whether the pack has updated Cobblemon since you last launched. A version mismatch between client and server is a common source of fossil interaction failures.
Machine assembly

- Place the Fossil Analyzer, Restoration Tank, and Data Monitor in the correct configuration. When placed correctly, you'll hear an electrical sound. If you didn't hear it, the multiblock isn't valid.
- Check that no other blocks are interfering with the multiblock structure. Even a torch or a slab in the wrong spot can prevent assembly.
- If you're unsure of the layout, disassemble everything and rebuild from scratch following the wiki diagram exactly.
Fossil pairing and organic materials
- Fossilized Bird must be paired with a second fossil. It cannot be revived alone. Check which Pokémon you want (Dracozolt or Arctozolt) and confirm you have the correct companion fossil.
- Make sure your organic materials in the Restoration Tank add up to a total value of 64. Inserting only fossils without enough organics will stall the process.
- Confirm the item you have is actually cobblemon: fossilized_bird and not a similarly named item from a different mod or resource pack.
Config and datapacks
- Check your Cobblemon config for the World.maxInsertedFossilItems value. The default is 2. If this has been changed to 1 on your server, you can't insert both fossils needed for the bird.
- If you're running custom datapacks, check whether any of them override files in the data/cobblemon/fossils/ folder. A bad JSON in that folder can break the entire fossil system or cause a server crash.
- Ask your server admin whether any addon or datapack modifies fossil recipes.
How to verify you have the right item and use it correctly
The fossilized bird is obtained specifically by brushing suspicious sand or gravel found at fossil dig site structures. In Cobblemon, these structures include locations like Birch Tree sites, Mossy Ponds, Oak Tree structures, Powdered Deposits, Preserved Skeletons (sand), Spruce Tree sites, and Suspicious Mounds. If you found your item somewhere else, in a chest from a non-fossil structure or through a trade that came from a modded source, verify its item ID.
To check the item ID in-game, hold the item and press F3+H to enable advanced tooltips in Java Edition. The item's internal ID will appear in the tooltip. It should read cobblemon:fossilized_bird. If it reads anything else, you have the wrong item and the machine will either reject it or do nothing.
Once you've confirmed the item, here's the correct sequence to actually complete a revival:
- Build the Resurrection Machine multiblock (Fossil Analyzer + Restoration Tank + Data Monitor) and confirm the electrical sound plays.
- Insert the fossilized bird into the Fossil Analyzer along with its required companion fossil. The Fossil Analyzer accepts up to 2 fossils by default.
- Fill the Restoration Tank with organic materials totaling a value of 64.
- Wait 12 minutes. Watch the Data Monitor for the embryo progress bar to confirm the process is actually running.
- Once the embryo is fully grown, right-click the Restoration Tank with a Poké Ball in your main hand to claim the Pokémon into your party. Alternatively, break the tank to release it as a wild Pokémon.
Troubleshooting by symptom
Can't obtain the fossilized bird
If you can't find the fossilized bird at all, you're either brushing the wrong kind of suspicious block or looking in the wrong structures. Only specific fossil dig site structures contain it. Regular Minecraft suspicious sand from desert temples or trail ruins won't drop it. Target the Cobblemon-specific structures listed above and use a brush on the suspicious blocks inside them.
Can't insert into the machine

If the machine won't accept the fossilized bird at all, first confirm the multiblock is assembled correctly (the electrical sound is the tell). If the machine is assembled but still rejecting the item, check whether a datapack has overridden the fossil item IDs incorrectly, causing the machine to not recognize cobblemon:fossilized_bird as a valid fossil. Also check that you aren't inserting unsupported items as organic material: the machine rejects incompatible items like mushrooms, and if you've been trying to stuff in invalid organics, the tank may appear unresponsive.
Inserted the fossil but nothing happens
This is the most common report. You put the fossilized bird in, and the machine just sits there. The answer is almost always that you haven't added the second required fossil. The fossilized bird is a Galar-style fossil that requires a companion fossil to define which Pokémon gets revived. Without the pairing, the machine won't start the process. Add the companion fossil and make sure your organic materials total 64, then check the Data Monitor for the progress bar.
Machine runs but produces the wrong Pokémon
If you're getting a Pokémon you didn't expect, the companion fossil you paired with the bird determines the result. Swapping that second fossil will change the output. If you're getting something completely unexpected (a non-fossil Pokémon, or nothing at all), a datapack is likely overriding the fossil JSON for the bird and mapping it to an incorrect result. Check the data/cobblemon/fossils/ folder in any active datapacks.
Machine finishes but you can't claim the Pokémon
If the 12 minutes passed and right-clicking the tank with a Poké Ball does nothing, check two things. First, make sure you have a Poké Ball in your main hand, not your offhand. Second, if you're on a multiplayer server, confirm you were the player who initiated the revival. Another player who didn't start the process cannot immediately claim the resulting Pokémon. There's a timing restriction that only applies to the initiating player at first. Also be aware that attempting to claim Pokémon from multiple fossil machines at the same time can cause disconnects, so don't rush through several machines back to back.
Server vs. single-player: permissions, sync, and datapacks
Single-player and server environments can behave very differently with the fossil system. In single-player, if the machine isn't working it's almost always a setup mistake, a version/loader mismatch, or a missing fossil pairing. On a server, there are additional layers that can break things.
| Issue type | Single-player | Multiplayer server |
|---|---|---|
| Wrong fossil pairing | Common, easy to fix yourself | Common, same fix |
| Machine assembly | Rebuild and listen for sound | Same, but check admin-placed machines |
| Datapack conflicts | Check your own mods folder | Ask admin to audit datapacks |
| Config changes (maxInsertedFossilItems) | Edit your own config | Admin must change server config |
| Claiming restriction | Not an issue | Only the revival initiator can claim first |
| Disconnect on claim | Can still happen | More common, especially with multiple machines |
| Version/loader mismatch | Check your own install | Server and client must match exactly |
On servers, datapacks are the biggest wildcard. Many Cobblemon community servers run custom datapacks that modify loot tables, fossil spawns, and even fossil-to-Pokémon mappings. If the fossilized bird works in single-player but not on a specific server, the server's datapacks are the prime suspect. Ask the server admin whether the fossils datapack folder has been modified, and compare the server's Cobblemon version against your client version.
Also worth knowing: some servers restrict which Pokémon can be revived or adjust loot tables so that certain fossil structures don't appear or don't contain the fossilized bird. If you can't find the item at all on a server, that's likely a loot table or structure spawn configuration, not a bug on your end.
Reading logs, debugging, and when to ask for help
If you've gone through everything above and the fossilized bird still isn't working, it's time to look at logs. Cobblemon errors related to fossil interactions usually show up as packet handling errors, interaction failures, or datapack loading warnings. Here's how to gather useful information:
- Reproduce the problem in a clean single-player world with only Cobblemon installed (no other mods). If it works there, the issue is a conflict with another mod or a datapack on your main world or server.
- Open your Minecraft logs folder (usually .minecraft/logs/latest.log) and search for 'cobblemon', 'fossil', and 'packet'. Any errors near those terms are directly relevant.
- If you're on a server, ask the admin for the server log around the time you attempted the fossil revival. Network packet decode failures and interaction errors appear in server logs and won't show on your client.
- Check whether the Fossil Analyzer, Restoration Tank, and Data Monitor are all the same Cobblemon version (i.e., not one block from an older cached chunk and the others from a freshly generated area).
- If you suspect a datapack issue, temporarily remove all non-Cobblemon datapacks and test again in a new world.
- Note your exact Cobblemon version, your mod loader and its version, whether you're on Fabric or NeoForge, and the companion fossil you're pairing with the bird. You'll need all of this when asking for help.
When you're ready to ask for help, the Cobblemon Discord and the r/cobblemon subreddit are the most active places to get a response. When you post, include your Cobblemon version, loader type, whether the issue happens in single-player or only on a server, the exact symptom (nothing happens, wrong output, disconnect, etc.), and your log snippet. A clear bug report with that information gets resolved much faster than a general "it's not working" message.
If you believe you've found a genuine bug rather than a configuration issue, the Cobblemon GitLab issue tracker is the right place to file it. Known issues like disconnect errors when claiming multiple fossil Pokémon back to back, or packet handling failures during fossil interactions, are already tracked there, so search before filing a duplicate.
The fossilized bird mechanic connects to something that naturally draws people to this corner of biology and game design: the idea that extinct creatures can be reconstructed from fragments. If you want the bigger historical picture, a dinosaur bird evolution timeline helps explain how birds evolved from earlier dinosaur lineages extinct creatures can be reconstructed from fragments. Bird extinction timeline resources can help you place those real-world examples (like the moa) into a broader historical context extinct creatures. If you came here asking whether the erosion bird is real, the answer depends on how this fossil system is set up in Cobblemon, not on any real-world creature fossilized bird mechanic. Real paleontologists studying birds like the moa or the various giant flightless species that vanished over the past few centuries face exactly that challenge, piecing together scattered fossil evidence into a complete picture. Cobblemon borrows that intuition directly. And just like in real fossil science, having only half the evidence, one fossil instead of two, gets you nowhere. If you're wondering whether you can find real bird fossils, the answer is yes, and they are often preserved as partial remains much like the game’s mechanics. Complete the pairing, confirm your machine, and the revival will work. If you’re wondering is the erosion bird extinct in the real world or lore, the fossil theme here is about reconstructing vanished creatures from fragments, which is why pairing and completion matter in Cobblemon. If you are asking whether the “erosion bird zaza” rumor is real, it is not connected to how Cobblemon fossilized birds and the Resurrection Machine work is the erosion bird zaza real.
FAQ
My fossilized bird goes into the tank, the progress starts, but no Pokémon ever appears. What should I check?
Confirm the full 12 minutes elapse after the embryo growth begins, then try claiming immediately with a Poké Ball in your main hand. If you remove the fossils, break the tank early, or swap dimensions while it is processing, the revival can fail silently or reset.
What counts as the “organic materials” requirement, and do the totals have to be exact?
Use the exact organic item(s) the Resurrection Machine accepts, and make sure the combined count totals 64 as required for the process. If you add multiple stacks that sum to a different total, the machine may not reject the item outright, but it can stall or not complete the growth.
I paired the bird with a second fossil, but I get the wrong revived Pokémon. Can datapacks cause only the mapping to change?
Yes. Even if the machine starts correctly, datapacks can alter only the fossil-to-Pokémon mapping. Double-check the second fossil type you used, then verify the active datapack settings are not overriding the fossils JSON for that specific bird and companion pair.
Does the fossil pairing order matter, bird first then companion?
In normal setups it should not matter, but some modpack or datapack changes can make the acceptance logic stricter. If you suspect order issues, test by inserting only the required two fossils and correct organic count, then try again with the reverse insertion order.
I’m on a server and the machine works for me sometimes, but other players cannot claim the revived Pokémon. Why?
Claim permissions are tied to who initiated the revival and an initial timing window. If someone else tries to right-click the tank immediately after you start it, they may see no effect. Have the initiating player claim, then wait briefly before other players attempt to claim.
Can I revive multiple fossils at once in the same Resurrection Machine?
Avoid stacking multiple revival attempts back-to-back or attempting parallel activations in the same machine. Some servers and versions have disconnects or packet handling issues when rapidly claiming from multiple fossil machines, so stagger attempts and claim one revival fully before starting the next.
The machine plays the electrical sound during assembly, but still won’t accept the fossilized bird. What’s a common setup mistake besides missing parts?
Check the placement and block orientation of the multiblock components, especially the Fossil Analyzer, Restoration Tank, and Data Monitor positions. If one block is slightly misaligned or replaced after assembly, the machine may appear built but fail item validation logic.
I’m sure the item is correct, but F3+H shows a different ID sometimes. Is there a way to confirm the item is actually the Cobblemon fossil and not a similar one?
Look at the namespace portion of the ID and the displayed item name. If the tooltip ID is not exactly cobblemon:fossilized_bird, do not use it even if it looks similar, since the machine’s fossil validation is typically strict and will ignore the mismatch.
Where do I find the logs that mention fossil or datapack problems, and what should I paste when asking for help?
Use the server console or client log output at the moment you insert fossils and attempt to claim the tank. Include the lines that mention datapack loading, fossil JSON overrides, interaction failures, or packet handling errors, not just the general crash summary.
If I can’t find the fossilized bird in any fossil dig sites on a server, is it always because the loot tables were changed?
Not always. It can be structure spawn configuration or fossil dig site generation settings, not just loot tables. Ask the admin whether fossil structures spawn as expected at your world settings, then compare the server’s Cobblemon version and datapack fossil configuration.
Bird Extinction Timeline: Events, Evidence, and Causes
Bird extinction timeline with key events, evidence, and causes, plus how to use dates to assess today’s extinction risk.


