01 / From the live worlds · Baylee’s report

The world doesn’t stop
when you step away.

Thousands of characters on autofarm, over 50,000 NPCs, and smooth operation reported by Baylee.Operator-reported experience, not a measured player limit.

Characters
Thousands

On autofarm, not standing idle.

TargetFightLoot
NPC population
50,000+

A populated world, under load.

Spawned NPCsAutofarm active
A recorded deployment

One snapshot. Real context.

Online players
1,200
Spawned monsters
50,000
Autofarm
On
22GBReported memory at this workload

Reported by the L2JBaylee team. This snapshot is separate from the broader workload report above and the idle-memory comparison below.

CPU / Under loadAwaiting measurements

A closer look at CPU.

—Average CPU
—Peak CPU
Processor
Not supplied
Logical cores
Not supplied
Observation window
Not supplied
Capture tool
Not supplied

No CPU capture supplied yet. Average, peak and hardware stay unreported until a profile is available; smooth operation alone is not a CPU measurement.

02 / Compare the builds

The worlds people return to.

Operator estimates of average online populations. These are observations, not player limits.

Select a build to explore Hatching shows a reported range
What these numbers mean

Online players. Population figures are operator estimates. Source and server sample size appear in each build’s details; observation periods have not been supplied. These are not a controlled capacity test or a maximum player count.

Startup and idle memory. Same machine · full NPC spawn · out-of-the-box configs Chronicle, configuration and workload can change results. The CPU panel describes the reported deployment only, not a cross-build comparison.

Chart scale. Every bar starts at zero. The hatched end of a population bar preserves the supplied range instead of turning it into a precise average. Missing data stays unplotted.