Bethesda Creation Engine
ESM / ESP plugin records / Papyrus scripts / PEX hooks
Architecture Specifications
1. Runtime Architecture Reconnaissance & Loader Selection
For Bethesda Creation Engine, the AI agent inspects DLL export tables and process memory maps. The recommended loader is SKSE, F4SE, SFSE (Script Extenders), hooking into the game initialization lifecycle to load custom assemblies.
2. Symbol Recovery & Decompilation Toolchain
Headless decompilation is orchestrated via xEdit, Creation Kit, BSA Browser, NifSkope. By restoring bytecode or reflection dumps into an Abstract Syntax Tree (AST), the AI assistant locates target classes, tick loops, and internal state fields.
3. Primary Hook Route & Injection Pattern
The established modding route is: ESM / ESP plugin records / Papyrus scripts / PEX hooks. This strategy provides atomic, reversible function detours without risking memory access violation exceptions.
4. Asset Overrides & Virtual Filesystem (VFS) Packing
Novel textures, sprites, and models are packed into engine-compliant archives and mounted via virtual filesystem overrides, leaving pristine game install directories untouched.
5. Automated Single-Player Sandbox Verification
The agent boots an isolated process, issues synthetic input signals, asserts memory invariants, and collects crash telemetry to guarantee deterministic mod stability.
Games Using This Architecture (1)
Select a title for game-specific hook parameters