Skip to main content
FatekeeperWiki

Database

Fatekeeper Enemies

A working enemy index for the wiki. Threat notes stay brief until each encounter is verified in-game.

Last data audit: 2026-06-11

Quick answer

Treat this as an encounter notebook. Enemy names and rough threats can be indexed early, but health, damage, resistances, and drops require repeatable testing.

Name
Zone
Confidence
Threat
Counterplay to verify
Notes
Bloodhound
Unverified
Community index
Fast pressure
Confirm dodge timing, spacing, and whether terrain breaks line of attack.
Needs screenshot, health check, and attack-pattern notes.
Exploding Bug
Unverified
Community index
Self-destruct behavior
Verify trigger distance, delay, and whether ranged tools are safer.
Flagged as a behavior-specific enemy; verify explosion trigger and counterplay.
Heavy Groth
Unverified
Community index
Heavy melee
Compare stagger windows, recovery timing, and safe punish distance.
Needs comparison against the standard Groth entry.
Mage Guard
Unverified
Community index
Ranged or spell pressure
Track cast windup, interrupt windows, and cover options.
Track spell type, resistances, and interrupt windows.
Practice Dummy
Hub
Needs testing
Test target
Use only for controlled weapon and spell value capture.
Useful for measuring weapon and spell values once capture rules are set.

Enemy capture checklist

  • Capture enemy name, zone, patch version, and a screenshot before adding a row.
  • Record attack names only if the game names them or the label is clearly editorial.
  • Keep health, damage, resistance, and drop fields empty until repeatable tests exist.
  • When behavior changes after a patch, preserve the old note with the patch context.

Related pages

Fatekeeper Beginner GuideUse encounter notes to decide what to avoid, test, or screenshot first.Fatekeeper WeaponsEnemy drops should not be published until capture evidence exists.Patch TrackerEnemy behavior changes should be logged by patch version.

FAQ

Why are enemy zones marked unverified?

The MVP avoids publishing route claims until a screenshot or repeatable path confirms the zone.

Can counterplay notes be published before exact stats?

Yes, as practical notes, but they should stay separate from numeric health, damage, or resistance claims.

How should drops be handled?

Drops should remain blank until repeated tests or an official source support the claim.

If a row is still community-indexed, publish the screenshot or patch note that supports it before assigning health, damage, or resistances.