> For the complete documentation index, see [llms.txt](https://stellarskills.gitbook.io/stellarskills-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stellarskills.gitbook.io/stellarskills-docs/configuration/integrations.md).

# integrations

StellarSkills owns progression and skill data. Pixelmon and other installed mods own their battles, spawns, inventories, transport and primary rewards. A bridge can modify an exposed safe value; a YAML key cannot invent an event/API that the other mod does not supply.

## Built-in Pixelmon consumers

The current source includes native handling for qualifying spawn shiny/hidden-ability rolls, spawn level, size and minimum IVs; capture ball power, type capture power, critical capture and selected capture rewards; PvE move/target-type damage and damage taken; Pokemon XP/EV gain; selected hatching/evolution/capture/battle reward hooks; Apricorn/Berry yields; supported fishing/trade/healer/move/fossil events; fossil speed/results, cloning results; Dynamax/Tera raid modifiers and rewards; mint yield/growth; Zygarde cell bonus/detection.

This is not a claim that every catalogue encounter/crafting/research key has a native consumer. For example, changing general encounter tables, scanners, crafting behavior or economy discounts requires a matching implemented hook/bridge. Consult the generated catalogue's evidence label and test the specific action.

Pokemon combat damage consumers currently skip player-versus-player battles when both Pokemon owners are players. `general.effects.direct-pvp-stat-bonuses` does not override that hard guard. Minecraft attribute attack damage is a different pathway and may affect Minecraft combat; audit it separately.

Type-specific capture power is based on the target Pokemon's types. `pixelmon.move_damage.fire` means a Fire-type **move**, not every attack made by a Fire-type Pokemon. `pixelmon.damage_vs_type.fire` uses the target Pokemon type, while `pixelmon.damage_taken_from_type.fire` uses incoming move type. Dual-type consumers can apply multiple matching type contributions.

Spawn-related ownership uses the hook's associated/nearby player. Multiplayer farms with several different builds should test which player's effects apply; these are not globally shared server buffs by default.

## Built-in Minecraft consumers

The source binds movement speed, maximum health, armor/toughness, attack damage/speed, knockback resistance, luck, interaction reach, step height, safe fall, oxygen, submerged mining, and block-break speed, plus mining/event modifiers and supported PvE damage, healing, knockback, vanilla XP, item/currency/XP rewards and first-generated container loot.

These run on the server. Increased movement/reach does not replace anti-cheat policies or guarantee compatibility with every protection mod. Test against your actual permissions/protection/region setup.

## Optional bridge matrix

| Integration      | Mod ID              | Current boundary                                                                                                       |
| ---------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| StellarDreams    | `stellardreams`     | Entry roll and encounter-weight event bridge; dream spawn shiny and capture XP/currency                                |
| StellarCrates    | `stellar_crates`    | Completion/voucher event bridge awards StellarSkills XP/currency, not arbitrary crate roll changes                     |
| Stellar Safari   | `stellar_safari`    | Entry cost, duration, capture limit, supported spawn shiny and capture XP/currency                                     |
| StellarAnomalies | `stellar_anomalies` | Declared optional effect/API integration; confirm the installed mod actually produces/consumes its tasks and modifiers |
| StellarAura      | `stellar_aura`      | Declared optional catalogue/API integration; installed bridge implementation is required                               |
| Titans           | `titans`            | Soft API keys are registered; the Titans build must call the generic modifier/progress API                             |

Missing optional mods do not prevent the base server from loading. Their individual effects should remain inactive when absent. Mod presence alone is not proof of version-compatible event/consumer behavior.

Files in `integrations/` are operator references, not a universal on/off loader. For example, the `enabled` entry in the Titans reference does not itself stop an external Titans API caller. Disable unwanted graph/module effects and task definitions, or the integration's own actual settings.

## Exact effect families

* Dreams: `stellardreams.entry_chance`, `encounter_weight`, `shiny_chance`, `capture_xp`, `capture_currency`.
* Crates: `stellarcrates.open_xp`, `open_currency`, `voucher_xp`, `voucher_currency`.
* Safari: `safari.entry_cost_multiplier`, `duration_multiplier`, `capture_limit_bonus`, `shiny_chance`, `capture_xp`, `capture_currency`.
* Titans: `titans.damage`, `damage_taken`, `loot_rolls`, `kill_xp`, `kill_currency`, `dungeon_xp`.

Use the full prefixed key for every field. Integration filter names such as `dream_id`, `encounter_id`, `crate_id`, `voucher_id`, `credit_id`, `zone_id`, `mode`, `titan_id`, `titan_tier`, `dungeon_id`, and `dimension` are supplied by those producers. Their IDs come from the other mod's configuration, not this book's invented examples.

## Two different raid types

Generic `pixelmon.raid_damage`, `raid_damage_taken`, and `raid_reward_rolls` affect supported raids. Separate `pixelmon.dynamax_raid_*` and `pixelmon.tera_raid_*` keys specialize them. XP task/quest events use `dynamax_raid_win` and `tera_raid_win`; reward effect families use their catalogue names. Do not substitute a task ID where an effect key is required.