// the find
JasonXuDeveloper/JEngine
The solution that allows unity games to update in runtime. 使Unity开发的游戏支持热更新的解决方案。
JEngine is a Unity hot-update framework that lets you push C# code and asset changes to shipped games without a new app store build. It wraps HybridCLR (the best current approach to C# hot update in Unity) with asset encryption, a one-click build pipeline, and asset management via YooAsset. Aimed at studios — particularly Chinese mobile developers — who need to patch live games fast.
HybridCLR as the runtime is a genuinely good choice: it runs standard compiled C# rather than forcing you into Lua or TypeScript, and the performance gap over ILRuntime is real and significant. The built-in DLL and asset encryption (XOR, AES, ChaCha20) plus Obfuz code obfuscation is actually rare in this space — most hot-update solutions leave protection entirely to you. The one-click build pipeline that chains compile → AOT metadata generation → obfuscation → encryption → YooAsset packaging is a real time saver once it's working. Dependency choices are solid: YooAsset handles large-scale asset delivery well, Nino (same author) is a proven zero-allocation serializer.
The project is heavily oriented toward the Chinese mobile market — a significant portion of issues, community discussion, and historical docs are in Chinese, which creates real friction if your team isn't. HybridCLR itself still has AOT generic restrictions that bite people in non-obvious ways (certain generic patterns require manual AOT hints), and JEngine doesn't surface these limitations prominently in onboarding. The 'ultralight core' framing undersells the setup cost: getting HybridCLR configured correctly across platforms, especially iOS with its AOT-only runtime, is non-trivial work that falls on you before JEngine's one-click button does anything useful. The Claude Code plugin is a marketing badge, not a technical feature — it's a CLAUDE.md with usage patterns, not something that meaningfully changes what the framework can do.