NME (Native Media Engine) is a cross-platform game and multimedia framework for the Haxe programming language. It provides a native runtime that compiles Haxe code to C++ via hxcpp and links against platform-specific backends for iOS, Android, Windows, macOS, Linux, and Web (Emscripten). The engine includes a 2D/3D rendering pipeline with both software and OpenGL backends, an audio subsystem with multiple backends (SDL, OpenAL, PulseAudio, ALSA, WebAudio), input handling (keyboard, mouse, touch, joystick), font rendering, and a build toolchain. The architecture is a library/framework with a core set of common components and platform-specific implementations selected at compile time. Key entry points include the `nme` CLI tool for building and running projects, the Haxe library under `src/nme/`, and the C++ engine under `project/src/`. External dependencies include Haxe, hxcpp, platform SDKs, and vendored libraries (LZMA, Clipper, Poly2Tri, FreeType, JPEG, Ogg, SDL, etc.). The codebase is large and contains both high-quality reusable components and some aging third-party code.
Polymod is a Haxe library that enables modding for games and applications by intercepting asset loading and providing a runtime scripting system. It supports multiple game engines (OpenFL, Lime, HEAPS, NME, Flixel, and custom backends) through a clean abstraction layer of backends and file systems. The core API (Polymod.init, scan, loadMod) allows developers to define mod root directories, load mod metadata, and apply asset replacements, text merges (XML, JSON, CSV, TSV), and script modifications. A notable feature is the integrated HScript interpreter (a fork of the language) that allows mods to define classes, override methods, and extend game logic at runtime. The codebase is well-structured with clear separations of concerns (backends, file systems, format parsers, utilities) and includes extensive sample projects demonstrating integration with various frameworks. However, it lacks a formal test suite, contains some debugging artifacts (trace calls), and relies on heavy macro metaprogramming for scripted class generation, which increases maintenance risk across Haxe compiler versions. The dependency on Lime/OpenFL internals and platform-specific conditionals makes the code somewhat brittle, though the core abstractions remain reusable.