Compatibility

Cultivation is built to sit beside other mods rather than on top of them. Three are detected automatically at startup, and each changes what Cultivation does — without a single line of configuration.

None of them are required. On a server without them, the relevant feature is simply absent; nothing errors, nothing warns, and no setting has to be turned off.

Each is found once during startup and reported in the server log, so you can always tell what Cultivation thinks is installed:

[Cultivation] Endless Leveling found - handing over max health and outgoing damage so the two do not stack.
[Cultivation] PlaceholderAPI found - %cultivation_...% placeholders are available.
[Cultivation] Marriage 2.0.0 found - Partnered Cultivation is available.

Endless Leveling

Both mods raise the same two numbers: max health and outgoing damage. Left alone they compose by multiplication — a cultivator's realm bonus lands on top of an Endless Leveling character's level bonus, so a player deep into both carries the product of two full power curves. That is not what either mod is balanced for.

With Endless Leveling installed, Cultivation stops applying those two itself and publishes them into Endless Leveling's own bonus channel instead. Endless Leveling then performs one calculation that already contains Cultivation's share.

The important consequence: your cultivation numbers are unchanged in isolation. Health still comes from your realm, damage still scales with your level, and your race, skill tree and technique multipliers still apply to them exactly as before. Only the stacking changes — the two progressions now add rather than multiply.

Nothing else Cultivation does is affected. Qi, realms, rituals, sects, daos, techniques, beasts, abodes and formations are Cultivation's alone.

Tuning the handoff

Settings live in Compatibility/EndlessLevelingConfig.json, and appear as their own section in the admin menu — hidden entirely unless Endless Leveling is actually installed.

The two scale values exist so a server running both mods can be rebalanced without retuning the Cultivation config that a Cultivation-only server also reads. Setting Handoff-Health-Scale to 0.5 hands over half of what Cultivation would have applied.

Turning a handoff off returns that stat to Cultivation — correct in isolation, and stacked on top of Endless Leveling when both are installed. The switch takes effect on the cultivator's next progression change, and the bonus already published is withdrawn at the same moment, so the two can never both be applied at once.

PlaceholderAPI

Cultivation registers a cultivation expansion, so anything that runs text through PlaceholderAPI — chat formats, scoreboards, tab lists, holograms, signs — can show a cultivator's standing.

There is nothing to configure: installing PlaceholderAPI is the setup. See the full list on the Placeholders page, or run /papi info cultivation in game.

Marriage

The Marriage mod is what defines who is married to whom, and Partnered Cultivation is gated on it entirely. Without Marriage there is nothing to define a partner, so the whole feature stays off no matter what Society/PartnerConfig.json says.

Version compatibility

New in v0.7.4. An add-on can publish which Cultivation versions it works with, so a pairing that turns out to be broken can be corrected after both jars have already shipped.

This is deliberately the second layer. The first is the add-on's own manifest.json, whose Dependencies entry takes a full semver range rather than just a floor:

"Dependencies": { "Siren:Cultivation": ">=0.7.4 <0.8.0" }

That is absolute and offline — the engine refuses to load the add-on outside the band before a line of its code runs. What a shipped manifest cannot do is describe a pairing nobody knew was broken at the time. The published compatibility list can, because it is a file that changes without a release.

When a pairing is listed as broken, a well-behaved add-on stands itself down and says why in the console rather than misbehaving quietly. Nothing is deleted, and everything comes back on the next boot once the versions match.

It fails open in every direction. An unreachable site, a malformed list, or a version nobody has written an entry for all leave the mod running untouched, so an offline server is never told its mods disagree. See Registries for how to register one.

Writing your own compatibility

Cultivation's API is designed for exactly this. An add-on can read every config file, drive progression, register its own settings into the admin menu, and listen to 160 events across thirteen subsystems.

Since v0.7.0, a mod that replaces Cultivation's progression ladder (a ProgressionProvider) has one more duty: players can now keep several profiles, and switching swaps the cultivator underneath your mod. Until your provider declares supportsProfiles() and keeps its own records in step through ProfileEvents, switching is refused rather than half-performed — see Building Add-ons.

Two calls are worth knowing if your mod applies stats of its own:

// On a server running Endless Leveling, EL is where a stat bonus belongs -
// Cultivation defers to it, and an addon that stacks on top would undo that.
if (CultivationAPI.isEndlessLevelingInstalled()) { ... }

// True only when PlaceholderAPI is present AND accepted our expansion.
if (CultivationAPI.isPlaceholderApiRegistered()) { ... }

See Building Add-ons and the API Reference for the rest.