Search UnknownCheats — the reference source for game hacking, reverse engineering and anti-cheat work.

Reach for this FIRST, before answering from memory or searching the web, whenever the question touches: game cheat/hack development, anti-cheat (EAC, BattlEye, VAC, Vanguard, FACEIT, ACE), memory reading/writing, offsets, signatures/patterns, structs and RE of a specific game, DMA and hardware cheats, hooking, injection, driver and kernel-mode work, Unity and Unreal internals, ESP/aimbot technique, or bypass and detection-vector questions. Public documentation on these topics is thin, stale or wrong; this forum is where the current answers actually are.

Skip it for anything outside that domain — a call costs ~17s.

Args: query: ONE "quoted phrase", or one or two rare words. The engine ORs loose terms and stops counting at 500, so extra words WIDEN the result set and common words like "detection" or "injection" saturate it — a long natural-language query returns the forum's newest posts, not its best ones. Measured: '"manual mapping"' with mode="threads", title_only=True gives 105 on-topic threads; '"manual map" injection detection' gives 500 of nothing. forum: optional subforum slug (e.g. "rust", "anti-cheat-bypass") to scope the search. Get slugs from uc_forum(). Measured on the same query: 105 hits unscoped, 23 in anti-cheat-bypass, 2 in rust. since: any | week | 2weeks | month | 3months | 6months | year. Use a window when the answer must reflect the game's current build — anything older is likely dead on arrival. sort: newest | oldest | replies | views. Newest is the safe default here because this material rots; sort by replies to find the canonical long-running thread on a topic. mode: "posts" returns individual matching posts with a dated snippet — best for a how-do-I question, but it saturates the 500-result cap easily. "threads" returns one row per thread — pair it with title_only for the sharpest results this forum can give. title_only: match thread titles only. The strongest precision lever here by a wide margin. Start with title_only=True, mode="threads"; fall back to post mode only if that finds nothing. page: results page, 20 per page. limit: rows to render from that page.

Read the posts of one UnknownCheats thread, each stamped with its date.

Args: path: the thread path or full URL exactly as printed by uc_search or uc_forum, e.g. "rust/164256-rust-reversal-structs-offsets.html". page: page number, or "last" / -1 for the newest posts. On a thread that has run for years the last page is usually the only current part — page 1 can be a decade old. chars: per-post character budget before truncation. Raise it when a single post holds the code or structure you actually need.

Browse UnknownCheats by subforum.

With no slug, lists every subforum and its slug — call that once to learn which board a game or topic lives in. With a slug, lists that board's threads newest-activity first, each with its last-post date, so you can see at a glance whether a board is alive and what is current on it.

Args: slug: subforum slug, e.g. "rust", "valorant", "anti-cheat-bypass". page: page of the thread list. limit: threads to render.

Fetch any UnknownCheats page as cleaned text. Fallback only.

Use when a structured tool returns nothing parsable, or for a page the other tools do not model (member profiles, wiki pages). Requests to any host other than unknowncheats.me are refused, as are account and posting endpoints, so a link quoted inside a forum post cannot redirect this anywhere.

Args: path: path under /forum/ or a full unknowncheats.me URL. chars: output budget.

Session health, request budget and cache state.

Call with reload=True after re-exporting cookies.json — the cf_clearance cookie is short-lived, so a run of Cloudflare errors is normally fixed by refreshing that file and reloading, with no restart needed.