UnrealCLR alternatives and similar packages
Based on the "Game" category.
Alternatively, view UnrealCLR alternatives based on common mentions on social networks and blogs.
MonoGame9.7 8.6 L2 UnrealCLR VS MonoGameOne framework for creating powerful cross-platform games.
Stride Game Engine9.0 8.4 UnrealCLR VS Stride Game EngineStride Game Engine (formerly Xenko)
Xenko8.0 0.0 L2 UnrealCLR VS XenkoXenko is a 2D/3D cross-platform game engine featuring a scene editor, particles, physically based rendering (PBR), scripting, and much more
Nez7.2 6.5 L2 UnrealCLR VS NezNez is a free 2D focused framework that works with MonoGame and FNA
FNA7.2 7.2 UnrealCLR VS FNAFNA - Accuracy-focused XNA4 reimplementation for open platforms
Duality7.1 0.0 L2 UnrealCLR VS Dualitya 2D Game Development Framework
BEPUphysics7.1 8.0 UnrealCLR VS BEPUphysicsPure C# 3D real time physics simulation library, now with a higher version number.
osu!framework7.1 9.9 UnrealCLR VS osu!frameworkA game framework written with osu! in mind.
CocosSharp6.2 0.1 L1 UnrealCLR VS CocosSharpCocosSharp is a C# implementation of the Cocos2D and Cocos3D APIs that runs on any platform where MonoGame runs.
UrhoSharp5.6 0.0 L3 UnrealCLR VS UrhoSharpCode to integrate with the Urho3D engine
Wave Engine2.8 0.0 UnrealCLR VS Wave EngineThis repository contains all the official samples of Evergine.
https://github.com/devtodev-analytics/winstore-sdkdevtodev SDK for Windows and Windows Phone
Access the most powerful time series database as a service
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of UnrealCLR or a related project?
UnrealCLR is a plugin which natively integrates .NET host into the Unreal Engine with the Common Language Runtime for direct execution of managed code to build a game/application logic using the full power of C# 10.0, F# 6.0, and .NET facilities with engine API. The project is aimed at stability, performance, and maintainability.
API reference | Manual | Code of Conduct | Community | Roadmap | Contact
- Host loading, integration, and management during the lifetime of the engine
- Dynamic loading, unloading, isolation, and dependency resolving of user assemblies at runtime
- On-the-fly access and execution of managed functionality through blueprints
- Runtime exceptions handling and tracing
- Continuously evolving framework for access to the engine API from managed code written in idiomatic C#
- High-performance interoperability through optimized code and utilization of blittable data types
- Support of .NET facilities including hardware-accelerated math with transparent re-mapping to vector types of the engine
- Support of .NET tools for debugging and profiling such as JetBrains product line, dnSpy debugger, and others
- Full independence from the compilation pipeline of assemblies with support of NuGet packages, analyzers, and generators
- Automatic project packaging for standalone distribution
- Carefully handcrafted source code for best maintainability and performance
- Extensive unit testing to ensure the robustness and consistency
- Distributed as a plugin and doesn't require rebuilding the engine
- Documented source code
The plugin is available for Windows, Linux, and macOS (x64).
- Unreal Engine 4.25.4 or higher
- A native compilation toolchain with platform-specific dependencies
- .NET 6 SDK 6.0.101
Create a new or use an existing Unreal Engine C++ or blueprints project. Clone the repository or download a desirable version from the releases section. Navigate to
Install folder, and run
dotnet run command. Follow the installation instructions. Open the project after the installation process is complete.
Make sure that the Unreal Engine is not running. Re-run the installation process. Recompile custom code with an updated framework.
--project-path <path> Sets a path to an Unreal Engine project
--compile-tests <true/false> Indicates whether tests should be compiled
--overwrite-files Indicates whether all previous files of the plugin and content of tests should be overwritten
Create a new or use an existing Unreal Engine C++ or blueprints project. Clone the repository or download a desirable version from the releases section. Copy the content of the
Source/Native folder to
%Project%/Plugins/UnrealCLR directory. Compile the managed runtime from
Source/Managed/Runtime folder by running the following command:
dotnet publish --configuration Release --framework net6.0 --output "%Project%/Plugins/UnrealCLR/Managed". Restart Unreal Engine, open the project, and build the plugin.
To quickly start testing, open a project with the plugin in Unreal Engine, copy all folders from the
Content of the repository to
%Project%/Content directory, and wait until they loaded in the Content Browser. Compile the managed assemblies from
Source/Managed/Tests folder by running the following commands:
dotnet publish "../Framework" --configuration Release --framework net6.0 dotnet publish --configuration Release --framework net6.0 --output "%Project%/Managed/Tests"
Make sure that the Unreal Engine is not running. Delete the plugin folder from a project, and repeat all steps from the compilation section. Recompile custom code with an updated framework.
The plugin is automatically loaded at startup. To make sure that it's initialized open the console window from
Window -> Developer Tools -> Output Log, find
UnrealCLR logs using the search input.
Open the scene with tests in the editor and enter the play mode. To switch a test, navigate to
Blueprints -> Open Level Blueprint, select the
Test Systems enumeration on the left panel, and change default value on the right panel.
Design and architecture
UnrealCLR is designed to be flexible and extensible. The plugin is transparently managing core functionality of the runtime, binding and caching the engine API for managed environment. The programmer has full control over execution flow through code and blueprints that allow to dynamically weave native events of the engine and its objects with managed logic. There's no hidden states or obscured order of execution behind the lifecycle of scripts.
At runtime, UnrealCLR loading managed assemblies into a cached isolated context. It allows dynamically replace assemblies after unloading them from memory, therefore the programmer can work with code without restarting the editor for continuous development. The compilation pipeline is entirely up to a developer, it can be organized in any desirable way without any limitations and with full support of NuGet packages.
Engine application program interface
The plugin and framework are evolving all the time to utilize as much power of the Unreal Engine as possible. It's crucial to have a feature-rich API. The system is created with high-performance in mind but without trading safety. The vast majority of code is written and verified by hand to prevent any unexpected behaviors at runtime and to ensure stability.
Use your favorite IDE and .NET tools that can be attached to the process of the engine just as to a regular .NET application for profiling and debugging. It's very convenient and works out of the box without any external effort. Analyze performance, monitor CPU usage and memory consumption, debug execution, take full control over the code. Explore new possibilities and extend your toolset in no time.
The runtime redirects all unhandled exceptions to log files, the console window, and on-screen messages of the engine, however, it's highly recommended to use try-catch blocks in C# to override redirections with custom handlers. It's necessary to have an attached debugger to properly trace exceptions in the editor or standalone. Use option types in F# to avoid exceptions altogether.
Unreal Engine, as well as .NET runtime, utilizes a garbage collector for memory management. The framework is designed with consistency in mind to prevent crashes and validate memory transparently for a programmer, no matter how objects were created and freed: with C++, C#, F#, or blueprints.
The plugin is independent of the compilation routine of user assemblies. It's loading assemblies from
%Project%/Managed folder and resolving dependencies at runtime after entering/leaving the play mode. The framework of the plugin with the engine API is automatically recognized and loaded as a dependency.
The framework replicates the class hierarchy of the engine with full interoperability support. Any external C++ code, blueprints, and plugins are compatible and extensible with UnrealCLR by design through the engine API. The plugin integrated into the engine's building pipeline and ready for distribution of self-contained applications.
Thanks to @natemcmaster for a great .NET library that simplifies dynamic loading of assemblies.
Special thanks to @Doraku for an amazing documentation generator and rapid improvement of it.
These wonderful people make open-source better: