菜单
Design and review Orryx station YAML mechanics for event-driven combat and passive behavior. Use for Event, Weight, Priority, Async, Actions, damage Pre/Post direction, shields, flags, cooldown handoff, accumulated damage, and Bukkit thread-safety checks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Orryx Minecraft 技能插件配置创作套件。用于生成或审查 Orryx 游戏技能、Kether 脚本、职业、经验曲线、法力精力成长、中转站、战斗状态机、控制器、选择器和多客户端 UI；也用于创建完整职业套件、检查跨文件引用和安全落盘。触发词包括 Orryx、技能配置、职业配置、经验曲线、Station、中转站、Status、Controller、Kether、选择器、DragonCore、GermPlugin。
Design deterministic Orryx ability YAML for Passive, Direct, DirectAim, Pressing, and PressingAim skills. Use when creating or reviewing ability type fields, Description/Variables/Actions consistency, passive Station companions, charging behavior, targeting compatibility, and cross-file requirements based on real Orryx examples.
Build and review Orryx combat status plus client controller pairs. Use for Condition, States, running transitions, Connection, Check and Invincible intervals, Animation mappings, general attacks, blocks, dodges, attack speed, and controller asset consistency.
Validate Orryx configuration packs without writing or reloading them. Use for basename-derived IDs, cross-file skill/job/experience/status/station references, skill Sort ordering, DirectAim and PressingAim Minecraft 1.12.2 compatibility, and reload-safety review. Produces deterministic diagnostics through the shared orryx_toolkit validator component.
Create and validate Orryx job-kit YAML using basename IDs, display Name/Icon separation, skill and experience references, attributes, mana/spirit/upgrade-point actions, and conservative second-job scaffolding. Use when assembling a job from existing abilities and curves without inventing unsupported ParentJob semantics.
Author and review Orryx Kether Actions for skill, station, state, job, and experience contexts. Use when a request needs context-aware variables, selectors, triggers, event access, deterministic script artifacts, or main-thread safety warnings. Treats the generated Actions Schema as an action vocabulary rather than a complete YAML schema.
| name | orryx-station-mechanic-skill |
| description | Design and review Orryx station YAML mechanics for event-driven combat and passive behavior. Use for Event, Weight, Priority, Async, Actions, damage Pre/Post direction, shields, flags, cooldown handoff, accumulated damage, and Bukkit thread-safety checks. |
| license | MIT |
| activation | {"command":"/orryx-station-mechanic-skill","intents":["create or review an Orryx station","wire attack or damaged events","implement passive, shield, flag, or accumulated-damage mechanics"]} |
| metadata | {"author":"NarraFork","version":"1.1.0","created":"2026-07-13T00:00:00.000Z","last_reviewed":"2026-07-13T00:00:00.000Z","review_interval_days":90} |
| provenance | {"repository":"Orryx","sources":["core/station/stations/StationLoader.kt","core/station/stations/StationLoaderManager.kt","example/Orryx/stations"],"generated_for":"orryx-creation-suite"} |
创建或审查 Orryx stations/*.yml 中转站。目标是把事件方向、执行阶段、权重、线程和 Kether 副作用写成可验证的配置，而不是仅拼接一段 Actions。
优先读取用户提供的事件名、触发方向、阶段、职业/技能 ID、Flag、伤害类型、依赖资源和现有 YAML。信息不足时采用最保守的同步、NORMAL 优先级和显式方向，并在报告中列出假设。
Player Damage * 以攻击者为脚本主体；Player Damaged * 以受击者为主体。攻击加成使用前者，护盾减伤使用后者。Pre 用于改伤、取消事件和预判；Post 用于记录已结算伤害、收集目标或后续反馈。不要在 Post 假装撤销已发生的伤害。Weight 越大越先执行；Priority 必须为 Bukkit 的 LOWEST/LOW/NORMAL/HIGH/HIGHEST/MONITOR。Options.Event 和 Actions。按需加入 BaffleAction、IgnoreCancelled、Variables、Async。&isCancelled；需要取消时在 Pre 使用 event cancelled true。参考“拳修内劲”：监听 Player Damage Pre，读取职业后修改 &event[damage]。加成公式必须说明是加法、乘法还是固定段，避免把最大生命等单位混入未标注比例。
参考“凝灵盾受击”：监听 Player Damaged Pre。护盾足够时取消事件并扣盾；不足时只扣除剩余盾值；破盾分支只执行一次，并明确 Flag 的 remove、timeout 与零值语义。反震范围必须排除 @self、盔甲架和队友。
参考“刹那冷却”：监听 Flag Change Post，在 newFlag == null 时设置技能冷却，确保持续态结束后才进入冷却。不要在创建 Flag 时提前结算。
参考“咒恶之锋”：监听 Player Damage Post，跳过取消事件，将 defender 合入容器并累加已结算 &event[damage]。容器、累计值与主 Flag 必须有一致的创建、读取和清理周期。
Options.Async: true 会把站点脚本放入插件协程作用域；它不等于所有 Bukkit API 都线程安全。涉及事件取消/改写、实体/世界、背包、声音、粒子、移动、伤害调用或 Bukkit 对象访问时保持同步。只有确认整个动作链为异步安全的纯计算或异步 I/O 时才启用 Async；数据库与 Redis I/O 由对应异步 API 处理，不能阻塞事件线程。
Options 与 Actions，保留 Orryx Kether 语法和事件字段。py -3 scripts/run_pipeline.py --input assets/request.example.json --output station-report.json。输出应包含固定组件 station、状态、错误与警告、事件方向、阶段判断、线程风险、引用 ID，以及建议的 YAML artifact。任何 error 都必须阻止 materialize。
Player Damage 与 Player Damaged 当同义词。详细字段见 references/contract.md，依据见 references/source-evidence.md。