Origins (1.36.5)
Curse Maven Snippet
What's new
Added
origins:impact(entity condition) — compares the impact rating of the origins a player has against a value you choose, so a power can ask "is this player playing something powerful?" without listing every origin by name.compare_totakes a number or an impact name (none,low,medium,high);comparisondefaults to>=. Optionallayernarrows it to one layer, andaggregate(max,min,sum,average) decides how several layers combine when it does not.origins:impact(bi-entity condition) — the same check across two entities.subjectpicks whose impact is the left-hand value; leavecompare_toout and it is compared against the other entity's impact instead of a fixed number, so a power can behave differently punching up and punching down.offsetshifts the right-hand side, so "at least one step above them" isoffset: 1with>=. Both read the active origin, so a swapped layer reports what the player is actually playing.Grief-log attribution. With Ledger or Indexor installed, a block edit caused by an origin's power is labelled
origin/powerin the log instead of@explosion— see the Apoli 1.80.0 notes. Origins supplies the origin half; Apoli does the rest.load_conditionon origins and origin layers. Apoli's new load-time gate is honoured by the origin and layer loaders, so one data pack can carry origins for two game versions and each one only loads where it parses. Layers are gated after their fragments are merged, so a gated fragment cannot leave a half-applied merge behind./origin orb [<targets>] <layer> [<origin>]— gives an Orb of Origin bound to a specific layer, and optionally to a specific origin. Layer alone clears that layer and opens its screen; layer plus origin applies it directly with no screen. Argument order matchesset,hasandrevoke.
Fixed
- Origin
upgradescould go dead silently, two ways.- In single-player, the client's registry sync shared the server's registry, so one upgrade that failed to rebuild from the wire switched the whole feature off mid-session with nothing logged. The data-pack loader and the client sync are now separate paths.
- A typo anywhere in an
upgradesblock was swallowed by the codec and the origin loaded with no upgrades and no log line. Parse failures now name the origin.
- Failures while writing
upgradesto the network log instead of throwing inside packet encoding.

