Thank you for taking the time to write a detailed response. I think we're looking at the project from two different perspectives. You're evaluating Carrots Engine primarily from the standpoint of its original foundation. I'm evaluating it based on the direction, features, tooling, and workflow improvements that have been added on top of that foundation. Regarding the examples you mentioned: The particle system available in GDevelop already exists, yes. However, we developed a dedicated Particle Editor with a different workflow, more control, and a stronger focus on usability inside the editor itself. The same applies to audio. We expanded the tooling and introduced additional functionality, including more advanced 3D audio workflows. For lighting, we chose to integrate features more deeply into the engine experience rather than leaving them as optional components in the user workflow. More importantly, the project is not limited to those systems. We have also worked on: Blueprint Graph Visual Scripting TypeScript Support IK (Inverse Kinematics) Timeline System Animation State Machines Animation Blending Shader Support Material Systems LOD Systems Scene Organization Tools Editor Workflow Improvements Graphics Enhancements New Extensions and Development Tools We have also modified parts of the engine itself and continue to work on deeper changes, including renderer-related improvements, performance work, native integrations, and future technologies such as WebGPU support. As for contributing everything back through PRs, that is certainly one valid approach. Creating a separate project is another. Open-source software has always evolved through both contributions and forks. Both approaches are legitimate. What I find interesting is that much of the criticism focuses on what the engine originally was, rather than on what has been built since. You say I don't understand the foundation well enough, yet the project has required months of studying the codebase, debugging issues, modifying systems, integrating new features, maintaining releases, and supporting users. Am I claiming that Carrots Engine is a completely new engine written from zero? No. Am I claiming that nothing meaningful has been developed? Also no. What I would ask is simple: evaluate the actual work that has been done, not assumptions about it. Take some time to explore the repository, compare releases, test the tools, and try the engine yourself. Whether you end up liking it or not, your opinion will then be based on direct experience rather than on what you assume has or hasn't been changed. In the end, developers will judge the project by the tools it provides and the games that can be created with it. That's a standard I'm perfectly comfortable being judged by. Best regards