A C++23/Lua-based platformer game engine
Levels are drawn in Tiled, enemies and cutscenes are scripted in Lua, and the engine renders them
with deferred lighting, baked ambient occlusion, water, weather and parallax. Box2D does the game
physics, SFML the rendering, SDL the game controller support.
Five platforms from one code base: Windows, Linux and macOS as native builds, the browser as WebAssembly without a plugin, and the Nintendo Switch as unsigned homebrew.
Play it in your browser on itch.io, or grab a build for your platform.
The clip is also available as an MP4 at full resolution.
Every push to master is built for all five platforms. These links always give you the newest
successful build and need no GitHub account:
| Platform | Download |
|---|---|
| Windows | deceptus-windows.zip |
| Linux | deceptus-linux.zip |
| macOS | deceptus-macos.zip |
| Web | deceptus-wasm.zip |
| Nintendo Switch | deceptus-switch.zip |
The desktop archives contain the executable next to the data/ directory. On Linux and macOS the
shared libraries come along in lib/ with a run.sh that points the loader at them, so start
those through run.sh. The web archive holds the Emscripten output and needs a server that sends
the COOP/COEP headers described under Web (WebAssembly). The Switch
archive is a single self-contained deceptus.nro with the assets embedded as romfs — it needs a
console running custom firmware, and it has to be started in title takeover mode, as described
under Nintendo Switch (homebrew).
The links resolve through nightly.link, which hands out the artifact of the latest successful workflow run. That indirection exists because GitHub only serves Actions artifacts to signed-in users. If you are signed in you can equally take them straight from the workflow runs.
Levels are drawn in Tiled. Tile layers carry the art, object layers
carry everything else: rooms, enemies, lights, doors, ropes, dialogues, conveyor belts, dust
emitters — every one of the 39 mechanisms is a rectangle with a handful of custom properties. There
is no export step: the engine parses the .tmx when it loads the level and keeps watching the file
while it runs, so saving in Tiled reloads the running game on its own.
What the engine makes of it: tile layers sorted by their z property rather than by their order
in the file, deferred lighting on top of ambient occlusion baked per level, animated water and
waterfalls, weather, and parallax layers front and back.
F1 draws the Box2D world straight over the running game: the static collision chains the level
is built from, every body and fixture currently on screen, hitboxes, the sensor rects enemies
watch through, and the room rectangles the camera clamps itself to. Each body also carries a
velocity vector that runs from red at a standstill to yellow at full tilt.
Joints are drawn as well, so a spike ball on a chain shows the anchors it swings around.
Physics and camera behaviour are not compiled in. F7 and F3 open configuration windows beside
the game; every value takes effect on the next frame, pointing at a setting explains what it does,
and the File menu writes the values back to the json the game reads at startup.
Physics (F7) |
Camera (F3) |
|---|---|
![]() |
![]() |
F10 opens the profiler: wall clock frame period, the split between update and draw, the time
spent handing the frame to the display, and the cpu side submit cost of every render section in
draw order.
F12 opens a console that teleports the player to a checkpoint, tile position or room by name,
hands out weapons, items and abilities, and drives the player event recorder. The help panel on
the right narrows down as you type, so it never lists more than you need.
The rest of the development hotkeys — debug overlays, the controller overlay, the log viewer, gravity flip, ambient light, zoom, and recording and replaying player input — are listed in development_hotkeys.md.
All of this instrumentation is compiled into the desktop builds by default. The web and Switch
builds ship without it, because it is overhead in a build meant to run fast and on the Switch
every report is a write to the sd card. -DDECEPTUS_DEVELOPMENT_MODE=ON puts it back for a
profiling run.
The complete documentation lives in doc/readme.md. The most travelled paths:
| Topic | Where |
|---|---|
| Designing a level | designing_a_level.md |
| Mechanisms, all 39 of them | mechanisms.md |
| Enemies | enemies.md |
| Visual effects, lighting and weather | visual_effects.md |
| Writing your own enemies in Lua | lua_interface/readme.md |
| Cutscenes | cutscene.md |
| Development hotkeys | development_hotkeys.md |
For the three desktop platforms, only a compiler, CMake and the platform's development headers are
needed. SFML 3, SDL 3, Lua 5.4 and GLEW are downloaded and built by CMake via FetchContent;
Box2D, ImGui, tinyxml2 and glm are vendored in the source tree.
The engine uses C++23, so the compiler has to be recent. CI builds with gcc 14, MSVC 2022, Homebrew LLVM, the latest Emscripten and devkitPro's aarch64 toolchain. Anything older than gcc 13 or Clang 15 will not do.
Web and Nintendo Switch come out of the same
CMake project as the rest, with EMSCRIPTEN and NINTENDO_SWITCH branches where the platforms
differ. Their cross compilers are not something you install next to a system compiler, so both
builds wrap a container and there is nothing to set up locally.
cmake -B build -A x64 -DCMAKE_BUILD_TYPE=Release
cmake --build build --config Release --parallelsudo apt-get install -y \
gcc-14 g++-14 cmake ninja-build \
libglm-dev \
libx11-dev libxrandr-dev libxinerama-dev libxcursor-dev libxi-dev \
libxkbcommon-dev \
mesa-common-dev libgl-dev libglvnd-dev \
libasound2-dev libpulse-dev \
libogg-dev libvorbis-dev libflac-dev libopenal-dev \
libfreetype-dev libpng-dev \
libudev-dev
cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release \
-DCMAKE_C_COMPILER=gcc-14 -DCMAKE_CXX_COMPILER=g++-14
cmake --build build --parallelbrew install llvm glm ninja
cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
cmake --build build --parallelThe web build swaps vanilla SFML for VRSFML and
renders through WebGL 2. It uses pthreads for audio worklets, which means the page has to be
cross-origin isolated —
opening the generated .html from file:// will not work.
With the Emscripten SDK on PATH:
emcmake cmake -B build_wasm -DCMAKE_BUILD_TYPE=Release
cmake --build build_wasm --parallelOn Windows, build_wasm.bat does the same inside the official emscripten/emsdk Docker image,
so no local SDK is needed.
The link step produces deceptus.html, deceptus.js, deceptus.wasm and deceptus.data, the
last of which is the whole data/ directory preloaded into the virtual file system. To play it
locally, server_wasm.bat starts a small server on
localhost:9080 that sends the required COOP/COEP
headers.
emscripten/ holds the hosting shell for the published build: itch_index.html is a
player-facing page that shows only the canvas, and coi-serviceworker.js establishes
cross-origin isolation on hosts that do not send the headers themselves, itch.io among them.
The Switch build is an unsigned .nro for a console running custom firmware. It reuses the
web build's rendering stack — VRSFML over SDL 3 — because vanilla SFML 3 renders through the
fixed-function pipeline and the Switch's mesa/nouveau driver is core profile only. The SDL
video, joystick and audio backends for the platform are carried as patches under patches/.
build_switch.batEverything runs in the official devkitpro/devkita64 Docker image, so no local devkitPro
install is needed. The result is a self-contained deceptus.nro with the whole data/
directory embedded as romfs.
It boots and plays, on a console as well as in an emulator, and audio is silent so far. On hardware it has to be launched in title takeover mode — hold R while starting a game from the HOME menu — or it runs out of memory during asset loading. doc/switch_build.md has the full setup, how to run and script it in Ryujinx, and how to work on the port itself.
If you're a musician, graphic artist, level designer or programmer, or just want to hang out and chat, please join us on Discord!
| What | Who |
|---|---|
| Artwork | dstar |
| Code | Matthias Varnholt |
The engine is released under Creative Commons Attribution-NonCommercial 4.0 International and is free to use on those terms.
The artwork is not. dstar owns it. It is in this repository so that the engine has a game to run, and it is not licensed for reuse, so ask first if you want to use any of it.








