Skip to main content
FatekeeperWiki

Database

Fatekeeper Alchemy

Ingredient and consumable tracking for Fatekeeper. The recipes and bombs keywords each have their own page, while this hub keeps the rest of the alchemy map visible.

Last data audit: 2026-06-11

Quick answer

Alchemy content should answer what an ingredient or consumable is for, then send readers into the recipe or bomb page if they need the exact inputs, effect, duration, or patch version.

Coatings

Community index
  • Bitterleaf Coating
  • Stoneroot Glue

Pre-fight weapon preparation

Verify duration, stacking, and eligible weapon classes.

Bombs

Community index
  • Explosive Bomb
  • Shrapnel Bomb
  • Virulent Gas Bomb

Burst damage, crowd control, or area denial depending on verified effect.

Capture damage radius, status effects, and crafting inputs.

Brews and Teas

Community index
  • Druid's Brew
  • Druid's Tea
  • Bitterstone Wine

Recovery or temporary buffs once effects are confirmed.

Record recovery, buff duration, and vendor availability.

Raw Ingredients

Community index
  • Rockflower
  • Widowhaulm
  • Yellowrath
  • Goldenglow

Recipe inputs and route-planning bottlenecks.

Map spawn locations and recipe dependencies.

Recipe verification workflow

  • Name the ingredient or consumable exactly as the inventory shows it.
  • Capture recipe input, output count, required station, and patch version.
  • Test duration or damage against the same target more than once.
  • Only then promote the recipe from community-indexed to cross-source or tested notes.

FAQ

Can recipes be added before exact formulas are known?

Recipe names can be indexed, but inputs, output counts, and station requirements should wait for screenshots.

Why separate alchemy from items?

Alchemy needs recipe and duration evidence, while the item database tracks broader gear and tooltip fields.

When is a consumable effect ready for guides?

When duration, effect, and stacking behavior have been captured on the same patch version.

Record duration, proc chance, and resource cost only after repeated tests match the same patch version.