Your Cards. Your Next Move.
Find attackable NPCs available under your current Monster cards, whitelist, levels, completed quests, and reviewed area access, then narrow them by defence and weakness.
What belongs in the finder
The Fight Finder is intended to answer “what can I fight right now?” without filling the page with every temporary or unreachable NPC in the game. Inclusion begins with a standard Attack action in a pinned game cache. One-time quest encounters and NPCs without a direct loot table are removed; a reviewed ordinary bone or ash drop is enough to keep a normal enemy.
Repeated versions such as common chickens are shown under one useful name instead of becoming separate results. The underlying variants remain separate during evaluation, so an accessible version can pass even when another version is locked behind a quest, region, activity, or Sailing requirement.
A mapped Monster card must be owned or universally whitelisted. If the current catalogue has no Monster card for an included NPC, the result clearly says that no current card is required. Listed Slayer levels and reviewed quest, region, island, minigame, and raid access are evaluated separately.
Use combat level, boss status, attack style, attack speed, elemental weakness, or stab, slash, crush, ranged, magic, and light/heavy/standard ranged defence to narrow the list. These values help compare targets; they are not a guarantee that the player's gear, supplies, or strategy can defeat the enemy safely.
The page does not dump every item in every drop table. It shows only drop cards already present in the player's collection, universal whitelist, or GIM binders. This makes it easier to find a training target, possible upgrade, or money-making route without turning each result into a second Wiki page.
Example: filtering for low crush defence and a matched group drop shows only currently accessible targets that fit those filters. Raid enemies remain hidden by default and can be deliberately included when the player wants to review them.
Review the data and methodologyAbout this projectReport a correction