Chronicle, player level, rates, city & tax

Lv diff	XP/SP	Loot/Spoil	Adena
0 or higher	100.0%	100%	100%
−1	90.9%	100%	100%
−2	82.6%	100%	100%
−3	75.1%	100%	100%
−4	68.3%	100%	100%
−5	62.1%	100%	100%
−6	56.4%	83%	100%
−7	51.3%	65%	100%
−8	46.7%	47%	100%
−9	42.4%	29%	88%
−10	38.6%	11%	75%
−11	35.0%	11%	62%
−12	31.9%	11%	49%
−13	29.0%	11%	36%
−14	26.3%	11%	23%
−15	23.9%	11%	11%
−16 or lower	≤ 21.8%	11%	11%

Facing Giant Fungus · Chronicle 1 game assets

Hunting Chronicle 1

C1 Hunting Rewards: Read XP, SP, Drops and the Real Cost of a Fight

Use C1 monster records to compare base XP/SP, level gaps, party pace, drops and spoil without mistaking a catalogue value for guaranteed session profit.

L2Tools guideUpdated 2026-09-24

Start with the monster's base record

A C1 monster page reports a level, HP, defenses and base XP/SP values. Those numbers describe the target in the catalogue; they are not a promise that every character receives that amount after a party split, level difference or server rate. At level 40, Giant Fungus and Karul Bugbear offer a useful paper comparison. Karul shows more base XP and SP with slightly less recorded HP. That makes it worth investigating, but it does not settle the hunt: these monsters occupy different areas, and travel, nearby spawns and class damage still matter.

Start with the monster's base record
Level 40 monster	Base XP	Base SP	HP
Giant Fungus	1,920	124	1,576
Karul Bugbear	2,128	138	1,527

Read monster color and your actual XP/SP penalty

Monster name color is relative to your character's level, not a reward rate by itself. In the supplied C1 server, each level you exceed a monster divides your XP and SP by 1.1, starting when the monster is only one level lower and still white. Green covers monsters three to five levels below you, light blue six to eight, and dark blue nine or more. For example, a target six levels below you leaves about 56.4% of your XP/SP share. In a party, that reduction applies to your own level-weighted share; members of other levels calculate their own color and penalty. Drops, spoil and adena follow different checks. See the party XP guide for a four-player worked example.

In a party, compare pace rather than a single kill

A group's reward is experienced per member, while its value comes from how many safe fights it can finish. A support character may raise the party's kill rate without appearing as the last hitter; a tank may prevent the downtime that ruins the next pull. Do not compare one solo kill's listed XP to one party kill and conclude the party is worse. Instead, measure your own XP/SP over the same amount of active time, including healing and rests. A stable group can make a more dangerous area practical even when each kill's reward is shared.

Drops and spoil answer different questions

A drop entry is a possible result of defeating the monster; it is not a guaranteed payment. Spoil is a separate opportunity for a Dwarf with the appropriate skills and a successful collection step. Open the monster record to inspect both lists, then check the item page for what the material is used in. If the expected item is rare, judge a longer sample rather than one empty kill. A party without a spoiler should not count spoil-only materials as ordinary income. Keep adena, quest rewards and inventory value separate when recording a session.

Run a short, honest field test

Try two suitable camps for about ten active minutes each. Begin and end at the same kind of point in the loop, then record the values below. Divide the XP and SP you actually gained by elapsed minutes. For adena, subtract shots, arrows, healing and travel from the adena and sale value you actually received. Note whether a crowded spawn or a dangerous add distorted the sample. The goal is a decision you can repeat, not a universal XP-per-hour claim from one fortunate pull.

Run a short, honest field test
Record during the test	What it tells you
XP and SP gained	Observed progress after your real modifiers
Kills and elapsed minutes	Whether the camp provides steady targets
HP/MP recovery time	The cost between fights
Shots, arrows and healing spent	Running cost of your gear and skills
Deaths, adds or crowding	Risk and interruptions the base stats omit

Move when the whole loop improves

A higher-level monster can offer more base XP and still be a worse choice if it takes twice as long to kill or forces repeated rests. Likewise, a lower reward per kill can be worthwhile when the camp supports a quest, provides materials your crafter needs or keeps a party together safely. Recheck after a profession transfer, new skill or weapon upgrade: the bottleneck may change. Use the mob comparator for candidate targets, the XP curve for your next level, and your field notes for the final choice.

Keep in mind

Catalogue XP/SP and loot entries are base data, not a forecast of a particular player's received reward or hourly earnings.
Server rates, level-difference rules, party distribution and drop configuration can change the observed result.

Start with the monster's base record

Giant Fungus and

Karul Bugbear offer a useful paper comparison. Karul shows more base XP and SP with slightly less recorded HP. That makes it worth investigating, but it does not settle the hunt: these monsters occupy different areas, and travel, nearby spawns and class damage still matter.

Start with the monster's base record
Level 40 monster	Base XP	Base SP	HP
Giant Fungus	1,920	124	1,576
Karul Bugbear	2,128	138	1,527

Read monster color and your actual XP/SP penalty

In a party, compare pace rather than a single kill

Drops and spoil answer different questions

A drop entry is a possible result of defeating the monster; it is not a guaranteed payment.

Spoil is a separate opportunity for a Dwarf with the appropriate skills and a successful collection step. Open the monster record to inspect both lists, then check the item page for what the material is used in. If the expected item is rare, judge a longer sample rather than one empty kill. A party without a spoiler should not count

spoil-only materials as ordinary income. Keep adena, quest rewards and inventory value separate when recording a session.

Run a short, honest field test

Run a short, honest field test
Record during the test	What it tells you
XP and SP gained	Observed progress after your real modifiers
Kills and elapsed minutes	Whether the camp provides steady targets
HP/MP recovery time	The cost between fights
Shots, arrows and healing spent	Running cost of your gear and skills
Deaths, adds or crowding	Risk and interruptions the base stats omit

Move when the whole loop improves