菜单
Use when server internals behave unexpectedly on a specific Minecraft version — a reflection lookup misses, a mechanic gates differently, a field seems renamed or relocated. Gives the javap-based procedure for reading the actual server code instead of guessing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a change claims 1.7.10/1.8.9 authenticity or could affect combat feel — the era ground truths, what is client-side and therefore untouchable, the known myths, and the anti-features the community history warns against.
Use when changing the knockback engine, profile schema, presets, or config files — the profile system's resolution model, engine order of operations, preset provenance, and the checklist for adding a knob without breaking era exactness.
Use when reasoning about knockback, velocity, trajectories, player movement, or any motion math in Mental — the exact Minecraft motion model (identical 1.7.10 → modern for knocked players), its constants, integration order, and the traps that produce block-scale errors.
Use when writing or debugging integration suites in tester/ — FakePlayer's NMS bootstrap and its clientless-player pitfalls, suite timing rules, assertion patterns, and the client-emulation model trajectory tests require.
Use when running, verifying, or debugging Mental's verification gate — which command to run locally vs CI, the matrix shape / per-entry native-era JDK & bytecode tier / suite tiers, how to read results honestly, and the concurrency rules that keep the concurrent Paper servers stall-free.
Use when touching the packet layer — the parse rim (PacketTap/BurstSender/ProbeRim/ValveListener), FeedbackPlan/pre-send behavior, reach validation, PacketEvents usage, or anything that runs on the netty thread.
| name | nms-archaeology |
| description | Use when server internals behave unexpectedly on a specific Minecraft version — a reflection lookup misses, a mechanic gates differently, a field seems renamed or relocated. Gives the javap-based procedure for reading the actual server code instead of guessing. |
When a version behaves unexpectedly, the answer is in the server's own class files, already on disk and Mojang-mapped (1.20.5+):
# The live server classes for a matrix version:
jar=run/<version>/versions/<version>/paper-<version>.jar
# 1. List a class's fields/methods (declared members ONLY — superclasses
# need their own javap; a "missing" member is often on the parent):
javap -p -classpath "$jar" net.minecraft.server.level.ServerPlayer | grep -i <term>
# 2. Disassemble the gate you care about and read which fields it consults:
javap -c -p -classpath "$jar" net.minecraft.server.network.ServerGamePacketListenerImpl \
| grep -A12 "public boolean hasClientLoaded"
Pre-1.20.5 runtimes are spigot-mapped — route names through reflection-remapper instead of javap'ing obfuscated jars.
isInvulnerableTo) to find the true
backing state.placeNewPlayer builds its OWN ServerGamePacketListenerImpl —
state you set on a listener you constructed yourself is dead; read the live
listener back off the player's connection field.ifeq 62 chains tell you the exact
boolean composition of a vanilla gate, including Paper-added config checks.grep -E "boolean|int "), not
just name guesses — Mojang renames freely between snapshots.JarFile
boundary at 1.12.2 (⇒ predicted bytecode tier v52). The live tester assertion
caught it: 1.12.2 on Java 21 actually loaded v61 — its loader DOES honor MR,
exactly like 1.9.4–1.11.2. The static read was of ONE class and missed a
delegation path; the boot report's bytecode tier: line (self-inspected from
the plugin's own class bytes, asserted per entry) is the ground truth. Static
disassembly narrows the hypothesis; the running server confirms it.