PulsePrison Integration

AtomCombat is built to be PulsePrison's closest combat companion, but every integration point is optional and the plugin works fully standalone without it.

Enable/disable the whole integration in config.yml:

yaml

integrations:
  pulseprison:
    enabled: true

Two directions of integration

1. PulsePrison listening to AtomCombat

AtomCombat fires its own internal Bukkit events for every meaningful combat moment (kills, killstreaks, bounty claims, bounty placements, ability usage, milestones, combat tags — see Internal Events). PulsePrison — or any other plugin — can subscribe to these exactly like an internal module would, without ever depending on AtomCombat's internal classes. This is how PulsePrison can feed AtomCombat kills into its own skills, milestones or rewards.

2. AtomCombat calling into PulsePrison's API

When PulsePrison is installed and integrations.pulseprison.enabled is true, AtomCombat uses PulsePrison's Developer API for:

Bounty rewards — set rewards.provider: pulseprison in modules/bounties.yml to charge and pay bounties in a PulsePrison currency (rewards.pulseprison.currency). See Bounties.
Skill experience on kill — set pulseprison.experience-per-kill in modules/stats.yml to grant PulsePrison skill experience on every confirmed kill. See Stats.
Rank ability gating — each rank ability can require a minimum PulsePrison prestige or rebirth, on top of its Bukkit permission. See Rank Abilities.

Requirements

PulsePrison must be installed and enabled on the same server.
AtomCombat compiles against and ships with the PulsePrison API classes needed to call these methods; no extra setup is required on your end beyond having PulsePrison installed.

If PulsePrison isn't present, or the integration is disabled, every PulsePrison-dependent feature above falls back gracefully (bounty rewards fall back to the configured rewards.fallback, skill experience is simply not granted, and prestige/rebirth checks are skipped).