메뉴
Use when server internals behave unexpectedly on a specific Minecraft version — a reflection lookup misses, a field seems renamed or relocated, a mechanic gates differently. Gives the javap-based procedure for reading the actual server instead of guessing.
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 | nms-archaeology |
| description | Use when server internals behave unexpectedly on a specific Minecraft version — a reflection lookup misses, a field seems renamed or relocated, a mechanic gates differently. Gives the javap-based procedure for reading the actual server instead of guessing. |
When a version behaves unexpectedly, the answer is in the server's own class files, already on disk and (1.20.5+) Mojang-mapped. Read them; do not trust memory or the wiki.
# Server classes for a version (Mojang-mapped from 1.20.5+). Two sources:
# the local reference cache (always available; scripts/fetch-reference.sh):
jar=$(find reference/servers/paper/<version> \( -path '*/versions/*.jar' -o -name 'patched_*.jar' \) | head -1)
# or a live matrix run: run/paper-<version>/versions/<version>/paper-<version>.jar
# (Folia: reference/servers/folia/<version>/...) — see the reference-cache skill.
# 1. List a class's DECLARED members (superclass members need their own javap —
# a "missing" member is often inherited):
javap -p -classpath "$jar" net.minecraft.world.item.ItemStack | grep -i <term>
# 2. Disassemble the gate you care about and read which fields it consults:
javap -c -p -classpath "$jar" <fully.qualified.Class> | grep -A12 "<method>"
Pre-1.20.5 runtimes are spigot-mapped — route names through a
reflection-remapper instead of javap'ing obfuscated jars (paper-cross-version).
grep -E "boolean|int |String ") — Mojang renames freely between snapshots.ifeq chains reveal the exact boolean
composition of a vanilla gate, including server-config checks.Registry over reflection — most StarEnchants version pain is API-level
(enum→registry renames), handled by resolvers (cross-version-item-api), and
needs javap only when a resolver still misses.Reflection/remapper miss, a resolver returns null on one version, a feature works on N but not N+1, or "this field stopped existing." Confirm with bytecode before changing code; then encode the finding as a capability probe or resolver fallback, never a version-string branch.