Known Issues

The Map library is built on type-agnostic templates, which means it has no true Blueprint support. The Array library exposes a set of common types to Blueprint, but this is a limited convenience layer rather than a fully realistic Blueprint workflow.

Both libraries are primarily intended for C++ usage. Projects that need Blueprint-facing array or map operations should treat the exposed nodes as a starting point rather than a complete solution.

Many Core classes are intentionally non-reflected (not exposed to Blueprint) in order to comply with a no-hard-references-across-plugins requirement. This keeps Core decoupled from anything built on top of it, but it does mean some functionality is C++-only by design.

Where Blueprint access is genuinely needed, a dedicated Blueprint usage class is provided as a wrapper. Not every file has one, so check for a corresponding usage class before assuming a system is unreachable from Blueprint.

If you encounter a bug or limitation not listed here, please reach out so it can be tracked and addressed. Known issues will be documented on this page as they are identified, along with workarounds where available.