MPackages

Packages

Every Deki Engine capability beyond the bare core lives in a standalone package DLL. Browse the catalog.

The package model

The engine core ships only base types: Deki::Object and Deki::Component, the lifecycle manager, the asset system, and the provider interfaces. Everything else (rendering, sprites, tweens, input, peripherals, networking) is a separate package with its own git repo under github.com/orgs/dekiengine.

Each package:

  • Builds as its own shared library (e.g. deki-2d.dll), never linked into the engine core.
  • Exports DekiPlugin_* functions discovered at runtime by PackageLoader via LoadLibrary / GetProcAddress.
  • Auto-registers its components and inspector editors at DLL load time through static initializers.
  • Is installed by the in-editor Package Manager from a registry, or added manually by GitHub URL.

Packages can depend on other packages. deki-2d, for example, requires deki-rendering and deki-input. The loader sorts them so deki-rendering is up before anything that draws.

Catalog

Gameplay & graphics

M.01 deki-2d 2D content components: sprites, text (BitmapFont + TTF baking), animations, gradients, buttons, scrolling, clipping, and rollers. M.02 deki-fsm Visual state machines. States, groups and transitions on a canvas, with an action flow inside each state. M.03 deki-input Input dispatch and collision detection. Routes pointer / touch / key events to interested components. M.04 deki-nodegraph The node graph canvas: an editor window, undo, domains and node registration, with no opinion about what the nodes mean. M.05 deki-particles Modular particle system: point/circle/rect emission shapes, gravity, drag, initial velocity, and lifetime/size/color/rotation modifiers. M.06 deki-rendering Core rendering pipeline: camera, render system, standard 2D renderer, QuadBlit, render passes, and sorting. M.07 deki-tween Tweening with 30+ easing functions. Use TweenComponent in the inspector or TweenManager in code.

Platform setup

M.08 deki-desktop-integration Desktop platform HAL: memory and filesystem providers for desktop builds. M.09 deki-esp32-integration ESP32 platform HAL: SD card via ESP-IDF SDMMC, FATFS filesystem, serial commands, memory and filesystem setup. M.10 deki-lovyangfx-integration Embedded display and touch via LovyanGFX 1.2.19. Drives common SPI/parallel TFTs and an FT6336U capacitive touch panel. M.11 deki-sdl3-integration Desktop display, input, and filesystem backed by SDL3 (3.2.8).

Hardware buses

M.12 deki-ble Bluetooth Low Energy abstraction. Engine-side interface for BLE peripherals and centrals. M.13 deki-i2c I²C bus support. Configure the bus once on the board; peripheral packages (RTC, IMU, touch) share it. I²C M.14 deki-i2s I²S bus support for digital audio peripherals such as the MAX98357 class-D amplifier. I²S M.15 deki-sdcard SD card support. Mounts the card so the asset manager can stream from it at runtime. M.16 deki-uart UART support for serial peripherals such as GPS receivers. UART M.17 deki-wifi Wi-Fi abstraction. Connect, disconnect, and report status; concrete backends supplied by platform integration packages.

Hardware peripherals

M.18 deki-audio Audio playback peripheral. MAX98357 class-D amplifier over I²S. MAX98357 · I²S M.19 deki-gps GPS peripheral. NMEA-over-UART backend (u-blox NEO-6M class receivers). u-blox NEO-6M · UART M.20 deki-imu 6-axis IMU (accelerometer + gyroscope) with hardware pedometer. LSM6DS3 over I²C. LSM6DS3 · I²C M.21 deki-rtc Real-time clock peripheral. Read and write wall-clock time from a scene component, with a DS3231 (I²C) backend. DS3231 · I²C

Networking & data

M.22 deki-http HTTP client. WinHTTP-backed synchronous GET on desktop. Embedded boards use their own network stack. M.23 deki-json JSON parsing for packages that need it at runtime. Wraps ESP-IDF cJSON on embedded; equivalent on desktop. M.24 deki-tiledmapeditor-integration Tiled Map Editor integration. Drop a .tmj file in your project; the editor bakes it to a streamable binary tilemap.