Manifold.AutoAssembler Module

The Manifold.AutoAssembler is a streamlined Lua module in the Manifold Framework designed to execute Auto Assembler (AA) scripts using a modular, override-friendly, and ship-ready strategy. It introduces a single entrypoint — AutoAssembler:AutoAssemble(...) — that smartly looks up and runs .CEA scripts from either local development folders or bundled table files.



What the Module Offers

  • Dual Source Lookup
    Loads scripts from:

    • DataDir (for development and personal overrides)
    • Table Files (for packed/released tables)
  • Simple One-Line Execution
    Run any .CEA script by its name — no paths or manual loading required.

  • Organized File Structure
    Uses process-specific folders like:

<DataDir>/CEA/<ProcessName>/<ScriptName>.CEA
  • Seamless Development-to-Release Flow
    Personal testing via DataDir; production use via embedded Table Files.

  • Logging and Diagnostics
    Optional message dialogs and logging for success/failure.


How to Use It

Run a Script by Name

AutoAssembler:AutoAssemble("TeleportHook")

The module:

  1. Looks for the script in:
 <DataDir>/CEA/<ProcessName>/TeleportHook.CEA
  1. If not found, looks in the Table Files (Cheat Engine’s packed files).
  2. If found in either, it will execute the AA script using AutoAssembler:PerformAutoAssemble(...), which uses the Cheat Engine autoAssemble(...)-Function as well as the autoAssembleCheck(...), to verify the syntax of the script.

File Lookup Strategy

Development (DataDir)

%AppData%\Local\Manifold\CEA\MyGame\TeleportHook.CEA

Release (Table Files)

Table Files are packaged files, directly attached to the Cheat Table.

The system prioritizes DataDir for personal overrides, then falls back to Table Files for shipped content.


Shipping Scripts

When you’re ready to ship:

  1. Add your .CEA scripts to the Table Files using Cheat Engine’s Context Menu.
  2. They will automatically be found by AutoAssembler:AutoAssemble without requiring external files.

Why This Design?

  • Supports both testing and production without changing code.
  • Keeps scripts modular and versionable.
  • Simplifies usage — just one function to call.