查找CEngineServiceMgrRegisterLoopMode

mrc4tt2026-10-25查看 765复制 355

| CEngineServiceMgr_RegisterLoopMode 的 Agent 回退(自动生成,类别:vfunc)。通过 IDA Pro MCP 在 CS2 engine 模块中定位 CEngineServiceMgr::RegisterLoopMode,并生成一个新的、最小唯一工件。确定性预处理器无法在当前 gamever 上解析该 符号——你的任务是重新签名。 触发:CEngineServiceMgr_RegisterLoopMode, CEngineServiceMgr::RegisterLoopMode

Download (.md)

📘如何使用这个技能

  1. 1
    复制技能内容·点击上方「Copy SKILL.md」复制全部内容,或 Download 下载到本地
  2. 2
    打开你的 AI 客户端·支持 Claude Code、Trae、Cursor、ChatGPT、DeepSeek、Kimi 等任意 AI 助手
  3. 3
    粘贴为系统提示/知识文件·Claude Code:放入 .claude/skills/ 目录;普通对话:作为首条消息发送并说「请严格按这份技能文档执行」
  4. 4
    直接提出你的需求·AI 会按技能定义的工作流、格式和约束来处理,无需再解释背景

💡 提示:技能生效后,每次对话只需一句需求,AI 会按 SKILL.md 的流程执行。

SKILL.md2148 chars
---
name: find-CEngineServiceMgr_RegisterLoopMode
description: |
  Agent fallback for CEngineServiceMgr_RegisterLoopMode (auto-generated, category: vfunc). Locate
  CEngineServiceMgr::RegisterLoopMode in the CS2 engine module via IDA Pro MCP and emit a fresh,
  minimal-unique artifact. The deterministic preprocessor could not resolve this
  symbol on the current gamever - your job is the re-sign.
  Trigger: CEngineServiceMgr_RegisterLoopMode, CEngineServiceMgr::RegisterLoopMode
disable-model-invocation: true
---

# Find CEngineServiceMgr_RegisterLoopMode

Target: `CEngineServiceMgr::RegisterLoopMode` (vfunc) in the module loaded in THIS session.

> The old artifact/preprocessor anchors no longer match this build. Use anchors
> only to *locate* candidates; derive the artifact from the ACTUAL bytes you read.
> Produce ONLY this session's platform output. NEVER open another binary.

## Method

Resolve the owning class vtable via RTTI (typeinfo-name string -> _ZTI object
-> vtable). Identify the slot by xrefs from expected call sites. Slots commonly
differ between platforms - never assume identical indices.

## Mandatory self-check before emitting

The pipeline re-reads the bytes at your `func_va` and regenerates `func_sig` from
them - a mismatch aborts the run. Therefore: read the real bytes via IDA MCP,
derive the artifact FROM those bytes (wildcard relocated operands as `??`), start
at the TRUE function head, and only then write the YAML. A mismatch is always a
bug in YOUR output.

## Output schema (STRICT)

Write `CEngineServiceMgr_RegisterLoopMode.{platform}.yaml` with EXACTLY these fields:

```yaml
func_name: <TASK>
func_va: "<hex virtual address>"
func_rva: "<hex rva>"
func_size: "<hex size>"
vtable_name: <owning class RTTI name>
vfunc_offset: "<hex vtable byte offset>"
vfunc_index: <decimal slot index>
```
NEVER include func_sig.

## Verification

1. Decompile and confirm the behavior matches the symbol's semantics.
2. Uniqueness: the pattern must match exactly ONE location in the loaded binary.
3. If no candidate can be confirmed, report the shortlist - a skipped symbol is
   safer than a wrong signature.
来源:skillsdirectory

评论0

登录后参与评论

还没有评论,来抢沙发吧