Field entry · Monsters

Monster Drops

The right question is not only which monster owns a material. It is which reward pool, rank and break condition gives you a reliable attempt.

Check rank and reward condition first

Monster materials can appear through different reward channels, and combining those channels into one list hides the action a hunter must take. Start with the exact English item name, verify Low or High Rank, then read whether the source is a target reward, quest reward, carve, severed part or named break reward.

No guessed rates: if the current game interface does not display a percentage, the Atlas publishes the confirmed source and condition without adding a community estimate.

Keep each reward pool separate

QuestTarget rewardsRewards tied to completing the target objective.
BodyCarvesRecord body and severed-part carves separately.
PartsBreak rewardsConfirm the named part and reward condition.
TierRank poolKeep Low Rank, High Rank and event pools apart.

Normal, Tempered, Arch-Tempered and event quests may also need separate rows. A material associated with the same monster name is not automatically available from every encounter version.

Choose a reliable farming route

  1. 01
    Find the source row

    Use the current Hunter’s Notes or quest reward preview to identify rank and condition.

  2. 02
    Match the quest

    Choose an encounter that actually contains that reward pool rather than the fastest-looking hunt.

  3. 03
    Plan the part break

    If the reward needs a head, wing or tail condition, bring a weapon and route that can reach it consistently.

  4. 04
    Link the use

    Check the smithy requirement before over-farming and return from the equipment to this source.

What the final database records

FieldRequired proof
Exact item and monster nameCurrent English client
Low / High RankHunter’s Notes or quest preview
Reward channel and partReward-condition interface
Displayed probabilityCurrent game interface only
Equipment usesSmithy equipment information

The database remains a framework until those screenshots are attached. The method is usable now; exact rows will not be faked to make the table look full.