Scripting & mod integration

Types driven by a KubeJS script or by another mod. A mod-backed type does nothing when its mod is absent; see Mod Compatibility.

Fields every power accepts (name, hidden, power_condition, …) are on Power basics. See also: KubeJS Integration, Mod Compatibility.

Types on this page: js_custom · js_active · become_dragon · xeno_passive.

KubeJS bridge powers

These two types delegate power behavior to JavaScript handlers registered from a KubeJS script, either a startup_scripts/ file, whose registrations survive a script reload, or a server_scripts/ one, which has to re-register on each reload (see KUBEJS.md). They only function when KubeJS is on the mod list: the power JSON references a js_id, and the script registers the matching handler via the NeoOrigins.* bindings. If no handler is registered for the id, the power is inert.

1.21.1 vs 26.x: js_custom and js_active are registered on 1.21.1, and on 26.1 from 2.2.24. KubeJS has no 26.2 or 26.3 build to compile against, so neither type exists there and a power file naming one is dropped at load.

They are registered on 1.21.1 and, from 2.2.24, on 26.1. They are absent from the 26.2 and 26.3 builds because KubeJS itself has no release for either to build against, and a power file naming an unregistered type is dropped whole at load. See KUBEJS.md.

`neoorigins:js_custom`

A passive power whose lifecycle hooks run JS. Register the handler with NeoOrigins.registerPower(id, {onGranted, onRevoked, onTick}); any hook the JS object doesn’t supply defaults to a no-op.

Field	Type	Required	Default	Description
`js_id`	string	yes	—	ID of the JS handler registered via `NeoOrigins.registerPower`

{
  "type": "neoorigins:js_custom",
  "name": "Scripted Aura",
  "description": "Behavior supplied by the pack's startup script.",
  "js_id": "mypack:aura"
}

// startup_scripts/powers.js
NeoOrigins.registerPower('mypack:aura', {
    onTick: player => { /* runs each power tick */ }
})

`neoorigins:js_active`

A keybind-activated power whose onUse runs JS. Register with NeoOrigins.registerActivePower(id, {onUse, onGranted, onRevoked}). onUse(player) must return a boolean: true consumes the cooldown and hunger cost, false is a no-op (nothing is consumed). Cooldown and hunger cost behave exactly like every other active power.

Field	Type	Required	Default	Description
`js_id`	string	yes	—	ID of the JS handler registered via `NeoOrigins.registerActivePower`
`cooldown_ticks`	int	no	`20`	Cooldown between uses in ticks (20 = 1s), consumed only when `onUse` returns `true`
`hunger_cost`	int	no	`0`	Food/exhaustion points consumed on a successful activation (`onUse` returns `true`)

{
  "type": "neoorigins:js_active",
  "name": "Scripted Blink",
  "description": "Teleports via the pack's startup script.",
  "js_id": "mypack:blink",
  "cooldown_ticks": 100
}

// startup_scripts/powers.js
NeoOrigins.registerActivePower('mypack:blink', {
    onUse: player => {
        // return true to consume cooldown + hunger, false to no-op
        return true
    }
})

`neoorigins:become_dragon`

Soft-compat hook for the Dragon Survival mod: while the power is granted, the holder is a Dragon Survival dragon of the configured species; revoking it reverts them to human form. The power is a pure hook — Dragon Survival supplies all of the resulting traits, growth, abilities and hunters. The form is re-applied on login and respawn, so it survives relog and death.

Field	Type	Required	Default	Description
`species`	string	yes	—	Dragon Survival species id, e.g. `dragonsurvival:cave_dragon`.
`stage`	string	no	`dragonsurvival:newborn`	Starting growth stage. Blank or unresolvable ids fall back to the species default.

Notes:

Inert without Dragon Survival. The power no-ops when the mod is absent. Always pair it (and the origin that grants it) with "required_mods": ["dragonsurvival"] so the content never loads, or appears in the picker, without the target mod. The three built-in dragon origins (Cave, Forest, Sea Dragon) follow this pattern.
The bridge binds to Dragon Survival’s internals reflectively (the mod exposes no addon API): if a future Dragon Survival release renames those internals, the power logs one warning and stops transforming players rather than crashing. See COMPATIBILITY.md.

Example: cave dragon form

{
  "type": "neoorigins:become_dragon",
  "species": "dragonsurvival:cave_dragon",
  "stage": "dragonsurvival:newborn",
  "required_mods": ["dragonsurvival"],
  "name": "Cave Dragon Form",
  "description": "Take the shape of a cave dragon."
}

`neoorigins:xeno_passive`

Soft-dependency compat with the Aliens vs Predator mod (avp_alien). Emits the xeno_passive capability tag, which an @Pseudo mixin reads from inside AvP’s AlienPredicates.isHost to short-circuit host eligibility: facehuggers (and the ovomorph hatch-desire / parasite-attachment logic gated off the same predicate) stop treating the holder as a viable host, as if already infected or immune.

This only governs the facehugger host gate. The companion “xenomorphs ignore me entirely” behaviour is delivered separately via a mobs_ignore_player power scoped to the #avp_alien:aliens / #avp_alien:parasites tags. When AvP is not installed the capability simply goes unread and this power is an inert marker.

Field	Type	Required	Default	Description
(no fields)	—	—	—	Marker power.

Example:

{
  "type": "neoorigins:xeno_passive",
  "name": "Tainted Blood",
  "description": "Facehuggers find you an unfit host."
}