Locate BuyState::m_doneBuying, exposed as BuyState::DoneBuying, in the loaded CS2 server binary. Emit a structmember offset, never a function or vtable slot. Trigger: BuyState_DoneBuying, BuyState::DoneBuying
Scanned 9/27/2026
Install to Claude Code
npx -y skills add mrc4tt/CS2_VibeSignatures --skill find-BuyState_DoneBuying --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Find BuyState DoneBuying?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mrc4tt-find-buystate-donebuying)More formats (shields.io, HTML) on the badges page.
---
name: find-BuyState_DoneBuying
description: |
Locate BuyState::m_doneBuying, exposed as BuyState::DoneBuying, in the loaded CS2
server binary. Emit a structmember offset, never a function or vtable slot.
Trigger: BuyState_DoneBuying, BuyState::DoneBuying
disable-model-invocation: true
---
# Find BuyState_DoneBuying
Target: the one-byte BuyState member `m_doneBuying`. The configured category is
`structmember`. Keep this skill as fallback until the preprocessor is verified
in the actual Windows/Linux binaries.
Inspect verified BuyState behavior code and trace the relevant member accesses
back to the BuyState object. `BuyState_OnUpdate` is a candidate inspection point,
not a proven dependency: verify its identity and the member's behavioral role
before using it. Do not assume an old offset or infer identity from a byte-sized
comparison alone. Distinguish this flag from the other BuyState flags and timers.
Read the actual displacement and verify its base object, access size and control
flow. Generate a unique instruction signature for this access; for an anchor
before the access include `offset_sig_disp`. Check the match in the loaded binary.
Only analyze and write the requested platform. If identity or uniqueness cannot
be established, report failure without guessed output.
Replace the complete expected `BuyState_DoneBuying.{platform}.yaml` under the
caller-provided artifact directory with:
```yaml
struct_name: BuyState
member_name: m_doneBuying
offset: '<verified byte offset in hex>'
size: 1
offset_sig: '<unique signature of the verified member access>'
```
Optional: `offset_sig_disp` for a backward-expanded anchor. Never emit `func_*`,
`vfunc_*` or `vtable_*`. Central runtime validation/canonicalization is mandatory.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!