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 Porta · Chronicle 1 game assets

Hunting Chronicle 1

Cruma Tower in C1: Group Hunting and Monster Progression

Plan a Cruma Tower party around recorded level 40 to 44 monsters, controlled pulls, travel from Dion and sustainable recovery.

L2Tools guideUpdated 2026-09-23

Start from the encounter, not a fixed entry level

Cruma Tower is a group-hunting destination near Dion. The C1 monster catalogue records Porta at level 40, followed by Excuro 41, Mordeo 42, Ricenseo 43 and Krator 44. A party can sometimes handle enemies above one member level, but the relevant question is whether it can repeat pulls without losing the next several minutes to recovery. Compare the actual group, skills and equipment against the first target before planning a long session.

Use the recorded sequence as a scouting sheet

The five entries give a progression to investigate, not a claim that every room has the same composition. Open their C1 records to check rewards, drops and individual traits. In the tower, note which doorway or section produced a manageable pull and which introduced a tougher target. A group that can clear Porta consistently has useful evidence for the next comparison; it does not automatically have the defense or recovery to keep fighting Krator.

Use the recorded sequence as a scouting sheet
Recorded C1 monster	Level	What to check
Porta	40	First recorded comparison
Excuro	41	Check the next pull
Mordeo	42	Reassess party recovery
Ricenseo	43	Watch resource use
Krator	44	Deeper progression check

Agree on party jobs before the first room

Decide who initiates a fight, who holds enemies away from vulnerable party members and who watches HP or MP recovery. Damage matters, but uncontrolled extra pulls can erase the benefit of a faster kill. A caster should use combat skills deliberately rather than relying on a weak auto attack, while support characters need room to react. After a few encounters, compare how many clean pulls the party completes before anyone needs an extended rest.

Budget the trip from Dion

Cruma Tower is linked to the Dion area in the native records, so travel and supplies belong in the plan. Bring enough shots, healing and escape options for the session the party actually intends to run. Check a teleport route before spending the remaining adena on one gear upgrade. If the group breaks up early, a clear return path prevents the savings from a good drop being lost to repeated travel or recovery.

Treat possible loot as a comparison, not a promise

A named Cruma enemy may have attractive entries in its drop record, but a listing is not a guaranteed outcome or a fixed price on your server. Compare the value of several actual runs with the cost of supplies and the time the party spends waiting. If one room is overcrowded or the next target causes frequent deaths, an alternative camp near the same level can be a better use of the evening.

Move deeper only when the loop remains stable

A level or equipment upgrade can make the next Cruma enemy realistic, but it is still worth retesting the pull. Move one section at a time, preserve an exit and note when the group starts consuming more resources than it gains. The tower also has boss-related records, which are separate objectives from ordinary monster farming. Finish a normal session with a clear comparison for the next visit rather than forcing the deepest available room.

Keep in mind

The five monster levels are native C1 records; exact room populations and player-server rates may differ.
No fixed XP-per-hour or guaranteed drop value is implied by this route.

Start from the encounter, not a fixed entry level

Cruma Tower is a group-hunting destination near Dion. The C1 monster catalogue records

Porta at level 40, followed by

Excuro 41,

Mordeo 42,

Ricenseo 43 and

Krator 44. A party can sometimes handle enemies above one member level, but the relevant question is whether it can repeat pulls without losing the next several minutes to recovery. Compare the actual group, skills and equipment against the first target before planning a long session.

Use the recorded sequence as a scouting sheet

Porta consistently has useful evidence for the next comparison; it does not automatically have the defense or recovery to keep fighting

Krator.

Use the recorded sequence as a scouting sheet
Recorded C1 monster	Level	What to check
Porta	40	First recorded comparison
Excuro	41	Check the next pull
Mordeo	42	Reassess party recovery
Ricenseo	43	Watch resource use
Krator	44	Deeper progression check

Agree on party jobs before the first room

Budget the trip from Dion

Treat possible loot as a comparison, not a promise

Move deeper only when the loop remains stable