`sar_hud_precision` > 2 should be cheat protected if `vm_debug` is being banned
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 122
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
title :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no implementation file, test, or reproduction steps beyond sar_hud_precision and vm_debug. Start by searching SourceAutoRecord for both identifiers and tracing how their settings are handled. Clarify what “cheat protected” means when vm_debug is banned, then define the expected behavior and a verification path before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100