Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
hlnd2t/find-cengineservicemgr-geteventdispatcherEngenharia reversa e fuzzing

find-CEngineServiceMgr_GetEventDispatcher

⁨Recover CEngineServiceMgr_GetEventDispatcher in CS2 engine binaries (Windows and Linux) when the find-CEngineServiceMgr_GetEventDispatcher preprocessor fails. Verify current vtable entries and function semantics rather than reusing historical addresses or signatures. Trigger: CEngineServiceMgr_GetEv⁩

v2026.11.13-dcf20203 instalações+3 em 7 dias67 EstrelasMITsincronizado há 12 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install hlnd2t/find-cengineservicemgr-geteventdispatcher

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
ZZrY24nOv1…4k8p4cDw==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote11c8039b…c6ab761d
11c8039b6851…1ef5c6ab761d1 arquivo · ⁦2.9 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/find-CEngineServiceMgr_GetEventDispatcher@dcf2020

Este item ainda não foi escrito no seu idioma, então aparece em English.

Recover the single output of find-CEngineServiceMgr_GetEventDispatcher using the assigned IDA Pro MCP database. The preprocessor ida_preprocessor_scripts/find-CEngineServiceMgr_GetEventDispatcher.py remains the normal fast path.

Realworld Function References

Read the applicable current inputs and the annotated references below. Source-owned 14192 YAMLs and stored disassembly are reference-build evidence; verify addresses, slot indices and semantics in the assigned binary. Never copy a reference target YAML into the active output directory as a substitute for analysis.

  • ida_preprocessor_scripts/references/client/CLoopModeFactory_CLoopModeGame_Shutdown.windows.yaml
  • ida_preprocessor_scripts/references/client/CLoopModeFactory_CLoopModeGame_Shutdown.linux.yaml
  • bin_artifacts/14192/engine/CEngineServiceMgr_vtable.windows.yaml
  • bin_artifacts/14192/client/IEngineServiceMgr_GetEventDispatcher.windows.yaml
  • bin_artifacts/14192/engine/CEngineServiceMgr_vtable.linux.yaml
  • bin_artifacts/14192/client/IEngineServiceMgr_GetEventDispatcher.linux.yaml

Output inventory

Module: engine. Platform scope: Windows and Linux. Analyze only the platform of the assigned database; the runner invokes platforms separately.

Platform Output filename 14192 reference entry Reference slot / offset
windows CEngineServiceMgr_GetEventDispatcher.windows.yaml 0x180213310 28 / 0xe0
linux CEngineServiceMgr_GetEventDispatcher.linux.yaml 0x37ec70 28 / 0xe0

Output metadata uses exactly vtable_name=CEngineServiceMgr; the concrete table artifact is CEngineServiceMgr_vtable.<platform>.yaml. Omit func_sig: this getter/thunk has no stable function signature under the producer contract.

Step 0. Bind the task and skip an existing output

Call idb_list and reuse the database assigned by the runner. Confirm the input path, image base and platform with IDA; do not open, switch, close or quit the runner's database. The binary is engine2.dll / libengine2.so. Resolve the active artifact module directory from CS2VIBE_ARTIFACT_DIR (also visible inside IDA's environment). If unset, stop and request the assigned artifact directory; never write YAML beside the binary. For the current platform, skip the output if it already exists there and parses as a non-empty mapping. Do not overwrite a result produced by an earlier alternative.

Load the platform-specific configured inputs named above from that active artifact root, not from the 14192 reference tree. Resolve ../client or ../server relative to the active module directory. Missing required inputs must be reported; do not open another binary to reconstruct them.

Step 1. Resolve the inherited interface entry

Use /get-func-from-yaml with func_name=../client/IEngineServiceMgr_GetEventDispatcher. The input may contain only interface call-site metadata; do not require func_va or invent a function body for the abstract interface. Check that vfunc_index and vfunc_offset agree (offset = index * 8). Read that slot in the current concrete table, and verify its live pointer against the active vtable artifact. Do not use the old target signature or reference slot as identity.

Step 2. Locate and verify the target

Read ../client/IEngineServiceMgr_GetEventDispatcher.<platform>.yaml relative to the active engine artifact directory. Use its current slot in the live CEngineServiceMgr_vtable.

The loop-mode shutdown references obtain the event dispatcher from g_pEngineServiceMgr before shutdown/event cleanup. The concrete method is an accessor for the manager's dispatcher subobject; Windows 14192 returns this+0x178. Distinguish this from getters of unrelated embedded interfaces. The stored references use offset 0xe8, while the verified 14192 interface slot is 28 / 0xe0. Prefer current slot metadata; do not reuse the old annotation or a sibling accessor's signature.

Step 3. Handle missing IDA function boundaries

A vtable YAML can exist even though IDA has not defined its target functions. For each plausible entry, verify the live 64-bit slot pointer, executable segment and decoded instruction boundary. If no function owns the entry, use conservative function definition and wait for analysis, then require the resulting function start to equal the slot pointer. Never delete bytes, split an existing function, or normalize an interior pointer to a neighbouring function's start. If a function already owns an unexpected interior entry, inspect and report the boundary conflict instead of forcing it.

Treat short adjusting thunks as legitimate vtable entrypoints. Follow their destinations for semantic verification, but preserve the slot's actual entry address in the artifact. Distinct-address candidate counts are not vtable slot counts. Confirm the target's slot by live pointer equality; use /get-vtable-index where helpful, and report multiple plausible slots rather than selecting an arbitrary duplicate.

Signatures and YAML output

Do not generate or carry forward func_sig, even if an old artifact contains one. Use /write-vfunc-as-yaml through its IDA py_eval implementation in the assigned session to write the YAML; do not substitute CLI shell or file-edit tools. Parameters:

  • artifact_name=CEngineServiceMgr_GetEventDispatcher and func_name=CEngineServiceMgr_GetEventDispatcher.
  • func_addr: the verified concrete entry in the assigned binary; emit func_va, func_rva = VA - image_base and the verified current func_size. Never emit a bodyless slot-only result for this target.
  • vtable_name=CEngineServiceMgr, current vfunc_index and vfunc_offset = index * 8.
  • vfunc_sig=None and vfunc_sig_disp=None; this target describes a concrete function, not a caller's vcall.
  • func_sig=None; ensure the field is absent in the written YAML.

Write only CEngineServiceMgr_GetEventDispatcher.windows.yaml / CEngineServiceMgr_GetEventDispatcher.linux.yaml as applicable, under the active artifact module directory. The trusted analyzer validates and canonicalizes this semantic payload. Read back the output and verify its name, fields, slot (when applicable), RVA and platform against the live database before reporting success.

Failure handling

If required inputs are missing, candidates remain ambiguous, entry recovery is unsafe, or no standalone entry can be verified, stop and report the exact missing output plus the semantic evidence examined. Do not invent a signature/address, create a placeholder YAML, disable config entries, or claim that a failed lookup proves the game removed the function. Do not run the failed preprocessor as the fallback's solution.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosSimSim
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-dcf202013 de nov. de 2026dcf202011c8039bAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login