Home · Skills · Bestiary

Hunter: requirements, training and loot eligibility

Historical Minecraft 1.12.2 / AoA 3.3.6. These are released configuration defaults and selected callback rules. A server configuration or inter-mod registration can change them. No live game test is claimed.

Start training

1. Check your Hunter level and choose an accessible target at or below it from the catalog below.
2. Open its creature card to inspect the available biome/dimension evidence, combat statistics and ordinary loot table. Location tags are evidence categories, not guaranteed spawn coordinates.
3. Defeat the target with player-linked kill credit. The selected death callback requests its registered positive Hunter XP.
4. For ordinary drops, use a player-attributed kill and meet the separate recently-hit and level checks. A pet kill can follow a different reward path.
5. Treat the listed XP as a base request. Shared XP settings and modifiers can change the final award. Do not infer the fastest training route from XP per kill alone.

Three separate checks

Check	Released behavior	Practical consequence
Attack permission	Registered exact entity classes use the player’s Hunter requirement; a player-owned tameable resolves to its owner. Creative bypasses the level gate.	An owned pet does not automatically bypass its owner’s level.
Death XP	The server death callback accepts a player or a tameable with a player owner, then requests positive registered Hunter XP.	Pet credit can qualify for XP independently of ordinary drops.
Ordinary drops	For a Hunter creature, the selected drop callback clears and cancels drops unless recently hit, the damage true source is a player, and that player is Creative or meets the requirement.	A tameable true source fails this ordinary-drop player check even when death XP has player-linked credit.

The selected attack helper allows a null attacker and unregistered targets through its own gate. For a registered target with a non-null attacker that cannot resolve to a player, it rejects the attack. These helper rules do not certify every damage path, event order or external mod interaction.

The shared level helper returns true when skills are disabled. This bypasses that level comparison; it does not remove the separate recently-hit and player-source requirements in the inspected drop callback. The shared XP system must still be evaluated separately.

Ordinary LivingDropsEvent contents are the scope of the drop rule. This is not a claim that every custom reward, direct item spawn or other mod’s reward system uses the same event.

Default Hunter catalog

All 71 entries below were matched to exact released entity-registration class bindings. Levels and decimal XP text come from the released default configuration constructor. Portraits are the existing bestiary’s scoped visual references; some use later-version reference models, so follow the card for provenance rather than treating every thumbnail as a native 1.12.2 render.

Visual reference	Creature and detailed card	Default level	Base XP
	Anemia	1	23.1
	Bloodmist	1	9
	Dark Beast	1	11.2
	Host	1	19
	Irkling	1	9.9
	Linger	1	10.8
	Modulo	1	11.9
	Night Watcher	1	9.5
	Rammerhead	1	10.8
	Roloscope	1	9
	Scrubby	1	7.6
	Skellox	1	7.6
	Terrestrial	1	13.4
	Urka	1	8.8
	Vertebron	1	9.5
	Void Walker	1	6.4
	Walker	1	6.6
	Death Hunter	3	11.4
	Headless Destroyer	3	12.1
	Reaper Twins	3	9
	Triclops	3	7.6
	Mother Void Walker	5	9.9
	Ice Giant	9	8.6
	Leafy Giant	9	7.4
	Sand Giant	9	10.2
	Stone Giant	9	15.5
	Wood Giant	9	12.4
	Amphibiyte	12	8.1
	Skeletal Cowman	13	12.8
	Kaiyu	17	10.5
	Zhinx	19	17.8
	Exohead	23	15.2
	Nethengeic Beast	24	16.3
	Diocus	27	29.9
	Paravite	28	21.4
	Spinoledon	28	21.4
	Iosaur	29	24.2
	Mushroom Spider	29	21.6
	Rawbone	30	24.6
	Enforcer	31	26.4
	Undead Troll	32	28.4
	Jawe	33	30.5
	Banshee	34	39.1
	Nightmare Spider	34	26.6
	Dawnlight	35	35.4
	Nightwing	39	47.8
	Flesh Eater	40	51.6
	Jumbo	42	90.2
	Phantom	44	70.3
	Cane Bug	47	88.9
	Gingerbird	50	112.8
	Gingerbread Man	53	143.6
	Pod Plant	56	183.1
	Vine Wizard	59	233.9
	Spectral Wizard	64	353.3
	Runic Guardian	66	417.2
	Mermage	67	453.5
	Amphibior	69	536
	Faceless Floater	71	634
	Zorp	75	888.4
	Zarg	76	966.9
	Baumba	78	1145.8
	Refluct	79	1247.6
	Inmate-X	81	1443.4
	Inmate-Y	81	1640.8
	Merkyre	83	1755.3
	Crusilisk	84	1912.2
	Arkzyne	86	2270.2
	Shyre Troll	90	3203.6
	Lightwalker	94	4527.5
	Luxocron	97	5873.8

Configuration and compatibility

• Default registration text has the form aoa3:anemia lvl:1 xp:23.1.
• The parser clamps required levels to 1–100 and XP to a nonnegative float range. It resolves the entity registry ID and requires an EntityLivingBase class.
• The Hunter registry keys exact classes. Subclass inheritance is not assumed.
• The selected registration method keeps the first registration for a duplicate class. Configuration and inter-mod registration order therefore matter when diagnosing competing entries.
• A mob missing from this default catalog is not proof that a customized server cannot register it as a Hunter creature.
• The Hunter armor class declares level 100 and a 0.3 Hunter XP modifier in its full-set callback. That declaration is not a live certification of every equipment or XP interaction.

Troubleshooting checklist

• Cannot hit a target: compare the effective server registration and your Hunter level, then inspect the attacker or pet-owner identity.
• XP but no ordinary drops: check the death damage’s true source, recently-hit state and the separate drop callback. Pet credit is a particularly important case.
• Different XP from the table: check server overrides, XP settings and active modifiers before assuming the table is wrong.
• Different mobs require Hunter on your server: compare configuration and inter-mod registrations, including duplicate-class ordering.
• Test level one below / equal to / above the requirement, Creative, skills disabled, owned and unowned tameables, environmental kills, projectiles and multiplayer credit.
• Test event cancellation and custom direct-spawned rewards separately from ordinary drop-list behavior.

Evidence and limits

Released method and registration evidence contains 16 selected methods, 71 configuration entries and 71 class-registration windows. Java/game code was not executed.

Pinned official source context. Released bytes determine the inspected defaults and gates. AoA assets and designs belong to Tslat and contributors.

Combat pickups and Rage · Skill Crystal targeting · Runtime acceptance

Target-native policy acceptance — October 21

These target-native checks apply to the canonical skill core, not to the entire original creature, armor or natural-survival family. Current native XP rounding and vanity boundaries take precedence for new saves; exact historical compatibility remains explicitly identified.

• Retain every released configuration default, with missing current actors explicitly reported.
• Verify every current native progression threshold through level 1,000 and complete progression/save/client-sync cases.
• Verify all 57 currently available later exact-class reward owners and their complete level/creative gate domain.
• Retain the complete earlier float, integer Snapshot, save, existing-skill and gate regression domains.
• Complete fourteen unresolved later actors, original-only Hunter identities, armor and acquisition.
• Verify the new candidate in the native rendered client, production/Hari environment, old saves and multiplayer.
• Certify the whole Hunter family through natural survival and the full AoA living union.