docs: EasyAntiCheat setup guide#26
Open
constripacity wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
EAC_Setup_Guide.mda short, step-by-step guide for getting EasyAntiCheat working on the UberStrike client via the EOS plugin: enabling Anti-Cheat in the Epic portal, granting team members access, downloading the integrity keys (base_private.key/base_public.cer), wiring them in Unity, building the bootstrapper, and testing.Why
Keeps the setup steps next to the code instead of in chat. Points to Epic's official docs for full detail.
Safety
Docs-only one markdown file, no code. Contains no secrets: it tells you which IDs/keys to copy from the portal, it does not embed any. The private key is explicitly flagged as never-commit.