C++ and the installed ExtensionSDK
What the C ABI provides and which C++ bindings are not shipped.
C++ implements a library; the C ABI defines its boundary with the engine. A C ABI does not imply ready-made C++ wrappers for Entity, String, or Vector3.
| File / directory | Purpose |
|---|---|
ExtensionSDK/include/reckfellextension_interface.h | Pointer types, callback structures, and C ABI functions. |
ExtensionSDK/extension_api.json | Sizes, types, and methods dumped by editor 1.0.0. |
ExtensionSDK/example/ | Native-library example and descriptor. |
Take the header and JSON from the same installed version. Retain mandatory SDK licenses. Do not invent renamed API identifiers.
The current kit does not contain a ready-made reckfell-cpp package, its class generator, or a public repository address for that package. Wrapper-cloning commands and calls such as new Entity are not working instructions here.
The checked path uses the C ABI from C or C++. The C++ example exports an entry point and registers an abstract class with two constants. It tests DLL integration rather than implementing an instantiable character.
Build the extension separately: no engine modification or rebuild is required. Measure any native-code speedup; choosing C++ does not guarantee one.