// the find
Alex-Rachel/TEngine
Unity 商用级别开发框架，原生内置 AI 工作流支持，集成 HybridCLR 高性能热更、Obfuz 代码混淆加固、YooAssets 企业级资源管理方案，构建高效、安全、可扩展的工业化开发底座。
TEngine is a Unity game framework targeting commercial mobile and PC games, built around HybridCLR for hot-update, YooAsset for asset management, and Luban for config tables. It's aimed at small-to-mid studios that want a battle-tested stack assembled and wired together for them rather than doing that integration themselves. The AI workflow tooling in the README is a bonus for teams already using Claude Code.
The component selection is solid: HybridCLR is genuinely the best Unity hot-update solution right now, YooAsset has proven itself at scale, and Luban handles config tables better than anything else in the Unity ecosystem. The zero-GC event system with automatic UI lifecycle cleanup is a real production concern that most frameworks ignore until it bites them. The startup procedure chain (ProcedureLaunch through ProcedureStartGame) gives a structured, replaceable flow instead of burying boot logic in Awake calls. The AI development workflow—tiered skill queries with session caching—is an unusually thoughtful addition; it actually addresses the real problem of LLMs wasting context on irrelevant framework details.
The documentation is almost entirely in Chinese, which gates out most of the international developer community and limits the pool of contributors and issue reporters. The framework requires Unity 2021.3+ and .NET 4.x, so you're stuck on Mono semantics unless you also configure IL2CPP properly alongside HybridCLR—the README glosses over that friction. There's no ECS/DOTS integration despite the 'ecs' topic tag, which is misleading. The file server tool in Tools/FileServer is a Node.js script sitting inside what is otherwise a pure C# project, which is an odd dependency to carry if you just want to serve hot-update assets in a non-production setup.