From the community
This guide started with Steam player reports
Players described the same refill symptom but found different causes and recovery paths. Those discussions shaped this version-aware troubleshooter, which checks the save before suggesting a community workaround.
Quick answer
If your Silksong Plasmium Phial is not refilling, update the game first, confirm that Shell Shards are available, rest at a bench, and test the normal restocking flow. Team Cherry fixed a release-era Plasmium Phial and Flea Brew bench-restoration issue in Patch 2. If the symptom remains, upload the original save and run the Plasmium Phial Troubleshooter to inspect the reported game version and recognized refill fields without changing them.
The current tool does not apply a universal “fix now” edit. Similar symptoms appear in community threads for different reasons, so a value that helped one older save may be wrong for a later build.
Why the same Plasmium symptom can need different fixes
A Plasmium Phial that appears empty after resting can point to an old game bug, a shortage of the resource used by the normal refill flow, a station-specific interaction, or a save value left in an unexpected state. Those cases look similar from the inventory screen but do not justify the same edit.
This is also why the guide keeps the game version near the top. A release-era workaround should not outrank an official patch, and a Patch 2-or-later save should not be treated as if its only possible cause were the original bench bug. The goal is to narrow the problem before touching progression or inventory data.
1. Check the game version and update
Team Cherry Patch 2 (1.0.28650) specifically fixed Plasmium Phial and Flea Brew sometimes not restoring at benches. Update the game, reopen the original save, and test at a bench first.
If the editor can read a save version, it reports that value in the checker. A version older than 1.0.28650 is a strong reason to test the official update before considering a community field edit. If no version is detected, treat the result as unknown instead of assuming the save is current.
2. Try the normal game flow
- Confirm the Phial is equipped and Shell Shards are available.
- Rest at a bench after updating the game.
- Try a Bell Beast station if the state appeared after restocking.
- Try an official auto save made before the broken state appeared.
Test one change at a time and reopen the inventory after a normal save. If the Phial refills through the game, keep that result and avoid editing the file. Normal game recovery is easier to trust across future updates.
3. Back up before inspecting values
Copy userX.dat outside the game folder or use Download Original Backup in the editor. Do not test a community edit on your only copy.
Keep the filename and slot association with the backup. A technically valid file in the wrong Steam ID or save-slot folder can look like a failed fix even though the editor never touched the intended run.
4. Check the save
Upload the save and run Plasmium Phial Troubleshooter. It searches recognized Lifeblood Syringe / Plasmium entries and reports fields such asAmountLeft, RefillsLeft, andSeenEmptyState when present.
The checker presents the detected values as evidence, not as instructions to maximize every number. Field names can describe a remaining amount, a refill allowance, or whether the empty state has already been observed, but the full relationship can vary with the named item record and game version.
5. Understand the community workaround
One Steam thread reports that players inspected the named Lifeblood Syringe entry and changed empty refill values, including a reply that used this site. Other reports describe Shell Shards, stations, or a game update resolving a similar symptom. That disagreement is why the editor shows the fields but does not force a one-click mutation.
Community workaround · version dependent
How to use the Plasmium Phial save checker
- Close Silksong and preserve the affected
userX.dat. - Upload the file and download the exact original backup.
- Open Popular Actions and choose Plasmium Phial Troubleshooter.
- Select Check My Save to read the version and recognized item fields.
- Expand technical details and note each field path with its current value.
- Compare the result with the official patch and the normal recovery steps.
- If the state remains unclear, restore the backup rather than guessing.
How to interpret the result
Release-era version detected
Update and retest the unedited save. The official Patch 2 fix is better evidence than a community workaround created for an early build.
Patch 2 or later detected
The original release bug may not explain the current symptom. Check Shell Shards, bench behavior, station interactions, and an earlier Auto Save before mapping an old workaround onto the newer file.
Related fields found, version unknown
Save the technical details for comparison, but do not infer a safe mutation from field names alone. Confirm the installed game version and look for a reproducible in-game trigger.
No recognized fields found
The item may use a name or structure outside the current fixture, or the wrong slot may have been uploaded. The checker leaves the file unchanged.
What the current tool will do
It will check and explain. It will not force a value when the save version, progression context, and complete field set do not support a safe decision.
Official source
Team Cherry: Silksong Patch 2Plasmium Phial troubleshooting FAQ
Is this a guaranteed Plasmium Phial fix?
No. It is a version-aware diagnostic guide. It helps you test the official fix, inspect recognized save values, and avoid applying an old workaround blindly.
Will Check My Save edit anything?
No. The checker reads and explains the parsed values. It does not modify the original file or generate a new file until you make a separate edit and choose to download it.
Should I change AmountLeft or RefillsLeft in Advanced Mode?
Not from the name alone. Confirm the item record, game version, current values, and a matching community case first. If the complete relationship is uncertain, restore a backup and keep the checker result for a bug report.