Consumables wiki
Fatekeeper Bitterleaf Coating
Fatekeeper Bitterleaf Coating guide with current role, player use, source status, related Fatekeeper pages, and patch-sensitive data fields.
Last data audit: 2026-06-15

Quick answer
Current answer
Community indexBitterleaf Coating is indexed as a Fatekeeper consumable, ingredient, coating, bomb, or preparation item. Effects, recipes, and pickup routes need patch-labeled proof.
Player use
Cross-sourceUse it for pre-fight setup, weapon preparation, duration, and stacking notes.
- Weapon preparation item; duration and stacking rules are unverified.
Source status
Community indexFatekeeper Bitterleaf Coating is treated as community-indexed data from public Fatekeeper databases, kept provisional until verified. Last data audit: 2026-06-15.
- Evidence to add next: Application screenshot and timer or repeatable duration test.
Tracked data fields
Needs testingBitterleaf Coating should be compared with the fields that affect real player choices. Unknown values stay visibly unconfirmed instead of being turned into fake stats.
- effect text
- duration
- eligible targets
- recipe input
- stacking rule
- Effect
- Duration
Bitterleaf Coating verification checklist
- Capture the tooltip or recipe view for Bitterleaf Coating with effect text, inputs, and output count visible.
- Run one controlled use test for duration, damage, healing, status, or target behavior.
- Separate recipe facts from combat-effect claims so alchemy and item pages stay consistent.
- Record the patch version and source date beside any value you add.
Related pages
FAQ
What is Fatekeeper Bitterleaf Coating?
Fatekeeper Bitterleaf Coating is tracked as a preparation consumable page in the Fatekeeper wiki. The page gives the current role, useful comparisons, source status, and related pages for this exact search.
How should players use Bitterleaf Coating?
Players should confirm eligible weapons and duration before building around the effect.
Where should Bitterleaf Coating updates be checked?
Check official Steam or publisher updates first, then compare community database entries and in-game evidence before changing guide recommendations.