메뉴
Use when writing or changing code that must run across StarEnchants' whole Paper range (1.17.1 → 26.1.x) — API selection, version-gated features, reflection, the 1.20.5 mapping flip, enum→registry breaks, or Java toolchains.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when running or verifying StarEnchants' test gate — which commands to run, the Paper+Folia version matrix, concurrency rules for booting many servers, and how to read results honestly instead of trusting a success banner.
Use when implementing or modifying the runtime engine — stateless systems, the activation pipeline and gate order, effect/condition/trigger/selector kinds, the Ability record, the Sink, declared Affinity, the dispatch plan, or how one activation executes.
Use when working on item state, the PDC codec, the ItemView content-hash cache, the stable-key to dense-id map, component stores, the WornState resolver, lore/name rendering, or legacy item migration.
Use when writing or reviewing ANY code in the StarEnchants repo — the design principles, engine boundaries, threading/Folia rules, config snapshot pattern, extensibility pattern, and the invariants every change must preserve.
Use when writing or reviewing code on the combat or item hot path, declaring an effect Affinity, touching the Sink/Dispatcher, the ItemView cache, interning, or anything the ArchUnit/CI lint or the JMH bench guards.
Use when working on the config schema/YAML, the DSL and ParamSpec, the compiler (resolve/typecheck/lower/erase/snapshot), diagnostics, transactional reload, catalog validation, or the EE/EA/AE and legacy-config migrator.
| name | paper-cross-version |
| description | Use when writing or changing code that must run across StarEnchants' whole Paper range (1.17.1 → 26.1.x) — API selection, version-gated features, reflection, the 1.20.5 mapping flip, enum→registry breaks, or Java toolchains. |
This skill covers the modern range (1.17.1 floor → 26.1.x ceiling). For the
1.8.9 tree — the -Pse.target=legacy overlay, JvmDowngrader, the mega-jar, and
its live gates — see the legacy-1.8.9 skill; it is a separately-compiled
tree, not a point in this range.
core compiles against the floor API (paper-api 1.17.1) so the common
path is binary-safe everywhere. Anything needing a newer API lives in a
compat-* module loaded behind runtime feature detection (a Capabilities
probe), e.g. compat-folia, compat-brigadier.api-version: '1.17' in
plugin.yml.nms-archaeology, never guess.nms-archaeology.DAMAGE_ALL→sharpness,
PROTECTION_ENVIRONMENTAL→protection, CONFUSION→nausea,
FAST_DIGGING→haste, VILLAGER_HAPPY→happy_villager). EE/EA configs use the
OLD names — resolve by name with legacy aliases. See cross-version-item-api.Attribute changed from an enum with GENERIC_* constants to a
registry-backed interface with unprefixed constants — a break in BOTH
directions. Resolve constants by name once at class load (modern spelling
first, then legacy).Enchantment became an abstract
class (registry-backed) at 1.20.5; Attribute and Sound became
interfaces at 1.21.3 (Attribute also dropped its GENERIC_ prefix).
Particle was RENAMED at 1.20.5 but is still a plain enum. Never store
any of these as a compile-time constant in a field — resolve by name through
the platform resolver (cross-version-item-api).PersistentDataContainer) has existed since 1.14 — present
across our entire 1.17.1+ range and the item-state storage of record. Avoid
the ItemMeta enchant helpers whose signatures shifted at the 1.20.5 flip;
go through PDC + the Enchantment resolver.Update integrationTestVersions in gradle.properties, check the Java boundary
in core/build.gradle.kts, and expect the gradle task to download/cache the
paperclip jar the integration matrix reuses. See matrix-gate.