Skip to content

feat: add Python anti-cheat monitor and baseline regression tests#19

Open
reguorier wants to merge 1 commit intojavelin-anticheat:mainfrom
reguorier:codex/bounty-issue-2
Open

feat: add Python anti-cheat monitor and baseline regression tests#19
reguorier wants to merge 1 commit intojavelin-anticheat:mainfrom
reguorier:codex/bounty-issue-2

Conversation

@reguorier
Copy link
Copy Markdown

/claim #2

Summary

  • add the missing anti_cheat.py monitor so issue [Feature] Implement Basic Anti-Cheat Protection #2 can satisfy the Python acceptance criteria
  • add focused unit tests for debugger detection, suspicious-process detection, tasklist parsing, and guarded exit codes
  • fix the native AntiCheat.cpp header / exit-code issue uncovered during review
  • document the baseline anti-cheat flow and test command in the README

Why this helps

The repository currently ships only the C++ sample, so the issue cannot fully pass its own acceptance criteria for the Python monitor path. This PR closes that gap with a small, dependency-light implementation.

Verification

python3 -m unittest discover -s . -p "test_*.py" -v
python3 -m py_compile anti_cheat.py

Notes

  • Python path is fully verified in this environment.
  • C++ runtime compilation was not executed here because this machine is macOS, but the native source fix is limited to missing intrinsics include + valid exit constants.

…al path to payout

The repository shipped only the C++ anti-cheat sample, so the issues Python acceptance criteria could not be satisfied. This adds a small Python monitor with debugger and suspicious-process checks, locks the behavior with focused unit tests, and fixes the C++ exit-code/header issue that would have broken the native path during compilation.

Constraint: Keep the patch dependency-light and easy to review in a tiny repo
Rejected: Adding third-party process libraries | unnecessary for baseline Windows tasklist coverage
Confidence: medium
Scope-risk: narrow
Reversibility: clean
Directive: Keep Python and C++ detection lists aligned when adding new suspicious tools
Tested: python3 -m unittest discover -s . -p "test_*.py" -v; python3 -m py_compile anti_cheat.py
Not-tested: Windows compilation/runtime validation of AntiCheat.cpp in this macOS environment
@reguorier
Copy link
Copy Markdown
Author

Verification summary:

  • python3 -m unittest discover -s . -p "test_*.py" -v
  • python3 -m py_compile anti_cheat.py

This PR specifically closes the missing Python path in issue #2, so the repository can now satisfy the acceptance criteria across both runtimes instead of only the C++ sample.

Issue link: #2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant