Skip to main content

game-hacking-techniques

Classify game-cheat implementation surfaces and their defensive implications. Use for authorized threat modeling of memory access, injection, overlays, input, or engine attack surfaces.

Informações da origem

Repositório
NeverSight/NeverD
Última atividade na origem
13 de setembro de 2026 às 11:12
Idioma detectado do SKILL.md
inglês
Estrelas
95
Forks
17

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
6 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
name
game-hacking-techniques
description
Classify game-cheat implementation surfaces and their defensive implications. Use for authorized threat modeling of memory access, injection, overlays, input, or engine attack surfaces.
# Game-hacking techniques Use this skill to understand offensive techniques as inputs to defensive research, detection design, or authorized lab analysis. Do not treat the catalog as permission to target third-party systems. ## Topic routing Read only the reference that matches the task: - [Taxonomy and core techniques](references/taxonomy-and-core-techniques.md) for privilege levels, manipulation, injection, and cheat categories. - [Rendering, memory, and input](references/rendering-memory-and-input.md) for overlays, access paths, driver communication, world-to-screen, and input simulation. - [Platform and evasion](references/platform-and-evasion.md) for EFI, HWID, stack behavior, and anti-detection concepts. - [Engines and workflow](references/engines-and-workflow.md) for Unity, Unreal, Source, and representative research workflows. - [Resource map](references/resources.md) for learning material and source attribution. Use `anti-cheat-systems` for defender architecture, `graphics-api-hooking` for render-pipeline details, and `game-engine-resources` for engine internals. Distinguish observed techniques from hypothetical capability and keep recommendations defensive.
Ver no GitHub