Skip to Content
Modlock

The framework

The parts Modlock is made of.

The WebAssembly host is built on Modlock's C++ framework, which also serves native plugins:

  • Plugin host. modlock-host runs a dedicated server that loads mods and plugins.
  • Engine events. EngineHost delivers frames, chat, commands, damage, connections, respawns and worlds.
  • Entities and rendering. World text, particles, effects, player pawns, bots and ray traces.
  • Engine interop. Signature scanning, vtable hooks, schema offsets, and CEntityKeyValues construction. Every byte signature lives in one table, and modlock-sigcheck checks it against the game binaries.
  • Session content. Precache heroes and resources, and advertise content addons to connecting clients.
  • Protocols. Protobuf for mods, HUD text, chat and camera paths in C++, Go, TypeScript, Luau and Python.
  • Portable tests. Parsing, dispatch, sandbox, and fixture tests run on macOS and Linux without the game.

The game runtime is Windows x64, including Windows builds under Proton.

How mods reach the game

The protocol between a mod and the server that runs it.

Building Modlock

Build the command line, the host and the libraries from source.