What Have We Added to GDevelop, and Does Using AI Mean We Don't Understand What We're Building?
Hello everyone,
Over the past months, there has been a lot of discussion about Carrots Engine, what has actually been added, and whether using AI somehow means we do not understand the technology we are working with.
We would like to clarify our position openly and respectfully.
First, Carrots Engine is built upon the GDevelop core, and we have never hidden that fact. We appreciate the work of the GDevelop team and fully acknowledge the foundation they created.
At the same time, we have spent a significant amount of time studying the engine, its architecture, and its codebase. Our goal has been to expand and improve it through new systems, workflow enhancements, and additional functionality.
Some of the additions and improvements integrated into Carrots Engine include:
(Blueprint Graph, TypeScript Support, New Animation System, Animation Blending, Animation State Machine, Timeline System, Bone Editor, Inverse Kinematics (IK), Path Tracker, Shader System, Toon Shader, PBR Materials, Material System, Physical Lighting, Water System, Normal Map 2D, FSR Support, LOD System, Graphics Upgrade, Rendering Improvements, Advanced Particle Editor, Scene Folder System, Child Object System, Built-in 3D Objects, Live Reload During Preview, Snap Transform Tools, Local / World Transform Modes, Console Log System, Git Version Control Integration, GitHub Workflow Integration, Audio Object System, Enhanced 3D Audio Workflow, MultiThreads (Web Workers Beta), Runtime Optimizations, Performance Improvements, Rendering Optimizations, New Extensions, Enhanced Editor Workflow, Improved Asset Management, Improved Object Organization, Inspector Improvements, Skew Support).
Regarding AI:
Yes, we use AI tools.
We have never denied that, and we see no reason to.
What honestly disappoints us is when people immediately assume that using AI means someone does not understand programming, engine development, or the code they are working with. We do not believe that is a fair conclusion.
AI is a tool. Like documentation, a debugger, a compiler, or any other development resource, it can help accelerate development. What matters is whether the developer understands the systems being modified, the code being integrated, and the consequences of those changes.
We study the engine, read its code, debug problems, test features, maintain the project, and continuously learn from the technology we work with. Using AI does not remove the responsibility of understanding what you build.
We also want to be honest about something else.
We are not claiming to be perfect. We have made mistakes, especially during the early stages of the project. If we have offended anyone, communicated poorly, or created a negative impression through our actions, then we sincerely apologize to those affected.
At the same time, we do not want to be treated as either heroes or villains. We are simply a group of developers trying to build a project we care about.
For anyone who has concerns, criticism, disagreements, or questions about Carrots Engine, we would genuinely welcome a calm and respectful discussion. We believe dialogue is far more productive than assumptions.
Most importantly, we would love to hear feedback from people who have actually used the project.
Positive feedback is valuable.
Negative feedback is valuable too.
Constructive criticism is often the most valuable of all.
Our entire team is genuinely interested in hearing real opinions based on real experience. If you have tried Carrots Engine, please tell us what worked, what did not work, what you liked, and what you think should be improved.
That kind of feedback helps us improve far more than arguments ever could.
Thank you to everyone who has taken the time to test, support, criticize, or discuss Carrots Engine.
We appreciate every honest opinion and every genuine conversation.
: Carrots Engine Team
