Large monster index

Monsters

A field guide built around what changes the hunt: states, parts, terrain, positioning and reward conditions—not a single misleading weakness icon.

Read the hunt as a sequence of states

A weakness table is only the starting hypothesis. The usable plan also needs the body part you can reach, the monster's current state, the opening created by terrain or a wound and the reward condition you are trying to satisfy.

Before the questDuring the huntAfter the result
Confirm quest access, region, rank and the exact targetRecord the part and state where safe damage actually landsSeparate a failed plan from failed execution
Choose one defensive answer and one item planUse wounds, breaks and readable recoveries as conversion windowsCheck the reward pool before repeating the quest
Match the weapon to reachable parts, not a theoretical maximumReset position when the target changes area or elevationChange one loadout job and compare matched hunts

Use specific field files when the evidence is complete

The location index resolves region, environment, migration and map-layer questions. Individual files such as Arkveld, Rey Dau and Gogmazios publish direct answers only where the version and evidence support them. The broader drops framework remains outside search until current-client reward rows are attached.

Araketa is documented separately in the Ascendance field file because Capcom has confirmed its type, locale and pack-flight behavior but has not published a weakness or drop table.

If a monster changes form, coating, charge or exposure state, record that state beside the part and damage type. Combining all states into one label produces a tidy table and a bad hunt plan.