Ancient Material Synthesizer: Avoid Paldium Storage Overflow

The community report: storage filled with Paldium

A high-engagement community post reported that leaving a synthesizer active filled every open storage space in a base with stacks of Paldium. The discussion quickly shifted from surprise to practical questions: whether the resource can be converted, sold, or prevented from taking over the base.

This is a player report, not an official bug confirmation. It is still useful because it identifies a real planning risk for anyone setting up late-game resource automation.

Set a storage boundary before automating

Do not make your entire base available to an unfamiliar production loop. Start with a deliberately limited storage area, confirm where the output goes, then expand only if the resource has a planned use. Keep critical crafting ingredients in their own storage so an overflow cannot hide the materials you need.

If you are testing a new setup, use a copy or backup of a valuable save where practical. That turns a viral warning into a repeatable check instead of a surprise cleanup task.

A safer synthesizer checklist

Run this short check before leaving the machine unattended.

• Set aside a dedicated overflow storage area.
• Keep essential crafting materials in separate containers.
• Test the output route while you are present.
• Decide the resource's intended use before increasing production.
• Pause production if you cannot confirm the storage behaviour on your build.

Is it a Bug?

There is no linked official acknowledgement that classifies the reported overflow as a bug. Describe it accurately as a community-observed storage behaviour until Pocketpair publishes a fix or clarification. If your own test differs, record your platform, build and base layout before drawing a broader conclusion.