11 September 2026 – 03:05 GMT+1<\/strong> We’re currently working on Candy Dialogue Engine 1.1.4<\/strong>: After that, we have more ideas for 1.1.5 already<\/strong>: 04 September 2026 – 04:05 GMT+1<\/strong> We’ve released several new products in the last couple of weeks: And yes, those are the first add-ons we have released for Blender!<\/p>\n\n\n\n Godot will remain our focus: we just occasionally create Blender add-ons for our own needs, so we might as well publish them in case anyone else finds them helpful.<\/p>\n\n\n\n 27 July 2026 – 17:00 GMT+1<\/strong> We’ve done some redesign to the website over the last few days. The goal was to better explain the important elements of our license terms.<\/p>\n\n\n\n To that end, we have created several new pages: Indie Tiers Overview<\/a><\/strong>, Studio TIer Overview<\/strong><\/a>, and the Mods<\/strong><\/a> page. We hope this will make our licenses seem less intimidating. They’re standard for the kind of products we offer, just a bit more thorough to cover edge-cases and anticipate loopholes. The reason we provide these overviews is so you can know what to expect: many other companies just throw big license agreements at you and let you figure things out. This way, you won’t have any bad surprises and you can comply with the terms correctly.<\/p>\n\n\n\n 27 July 2026 – 05:45 GMT+1<\/strong> 24 July 2026 – 15:20 GMT+1<\/strong> \u2022 Updated the Candy Dialogue Engine Free Indie, Starter Indie, Pro Indie and Studio Licenses<\/strong><\/a> from version 1.1.0 to 1.1.1. 20 July 2026 – 04:15 GMT+1<\/strong> We’ve updated the Candy Dialogue Engine Studio License from sub-version 1.1.0 to 1.2.0. This new sub-version modifies “\u00a72.11 Royalties” to remove an ambiguity over whether royalties are retroactive, and to close some loopholes.<\/p>\n\n\n\n The spirit of our Studio License has always been “Make a game with the help of Candy DE \u2192 Pay a small revenue share for the contribution it provided”, and not “Make a game that will require Candy DE \u2192 Collect pre-orders \u2192 Add Candy DE at the last minute to avoid sharing pre-order revenue.”<\/p>\n\n\n\n Going forward, when the Studio License is assigned to a project:<\/p>\n\n\n\n Most projects won’t be affected<\/span>: our assets provide core functionalities, so it would be unusual to add them late. Additionally, if a project decides to add an asset with the scope of Candy DE mid-way through development, or to replace its original dialogue system with Candy DE after release, it’s doing so for a very good reason and it predicts Candy DE will bring important benefits.<\/p>\n\n\n\n In any case, for projects that decide to add Candy DE late in development, after they’ve already began earning revenue, these retroactive royalties are essentially just an entry fee. Our royalty rates are also lower than the value our assets might justify, which should more than compensate for that added fee.<\/p>\n\n\n\n The alternative would be for us to double our royalty rates to ensure that in the long run, we still get a fair share from the projects we support — which would cost projects more and affect everyone. Ultimately, this solution keeps the inconvenience low and limited to those rare cases, while maintaining fairness across the board.<\/p>\n\n\n\n This license change only applies to projects that assign the Studio License in the future.<\/strong> 16 July 2026 – 03:40 GMT+1<\/strong> Candy DE\/DC 1.1.0 have been released! Head over to GitHub to download them! 15 July 2026 – 17:15 GMT+1<\/strong> Updated the Candy Dialogue Engine Free Indie, Starter Indie, Pro Indie and Studio Licenses<\/strong><\/a> from sub-version 1.0.x to 1.1.0. To clarify: Licenses 1.1.x allow you to use Candy Dialogue Engine 1.0.x and 1.1.x in your Works. Licenses 1.0.x only allow using Candy Dialogue Engine 1.0.x.<\/p>\n\n\n\n No other changes were made to these licenses. 22 April 2026 – 20:25 GMT+1<\/strong> Big news: Candy DC 1.1 is in the works and will release in beta a couple of weeks! 05 April 2026 – 15:40 GMT+1<\/strong> We’ve now opened a Youtube channel<\/strong><\/a>, which features tutorial videos on how to use Candy DE and Candy DC! Of course, we’ll also use it to provide tutorials on future assets as we release more. The PDF guides provided with our assets are more complete and a faster read, but these videos are helpful when you require a more visual methodology. We’ll make more videos on Candy DE\/DC features as well (Player Choices are next).<\/p>\n\n\n\n 27 March 2026 – 23:25 GMT+1<\/strong> Good news: we’ve added a new page under the “Information” category: Indie Project Checklist.
[News]<\/strong><\/p>\n\n\n\n
This will bring a lot of bug fixes, error safeguards, and code improvements. A few convenience features were also added.
The code will rely a lot more on helper functions: we find them less readable than in-lining (just a personal preference), but they make the code more robust and consistent. We’ll also improve debug prints (and make them optional with a variable) so that you can better understand why something isn’t working.
We also added a few convenience features that we thought were important, and simple enough that they wouldn’t add too much testing or pose significant risks of bugs.
As for Candy DC, it will receive a minor 1.1.1 update to be compatible with Candy DE 1.1.4. This update will include a few small bug fixes.
We’re currently testing all the changes. We don’t have an ETA: it all depends how testing goes. We hope to finish in September, but it might be October.<\/p>\n\n\n\n
\u2022 An important one will be function references: Currently, you can substitute dialogue data with variable references. Now that this system seems solid, we want to add the ability to provide references to functions, and to use their returned values as data.
\u2022 For more advanced users, we also plan to store more dialogue processing data into class variables. This would be data that normally exists only inside functions, but which you may want dialogue commands to access.
\u2022 We’ll also look into adding more hook functions or emitting signals throughout the code (we need to figure out the practical pros and cons of signals vs. hooks). So far we added hook functions where we assumed users might want to inject custom behavior into the dialogue, but we hadn’t really considered where users might want dialogue to trigger events in their game.
And for Candy DC 1.1.2:<\/strong>
We have a list of various features and improvements we want to add, so 1.1.2 will mostly be a polishing update.<\/p>\n\n\n\n
\n\n\n\n
[New Releases<\/strong>]<\/strong><\/p>\n\n\n\n
– Two Minor Assets: Candy Loot<\/strong><\/a> and Candy Triggers<\/a><\/strong>.
– A companion utility plugin: Candy Tools<\/a><\/strong>.
– Two Blender add-ons: Window Resizer<\/a><\/strong> and Reset 3D Cursor<\/a><\/strong>.<\/p>\n\n\n\n
\n\n\n\n
[Website Update<\/strong>]<\/strong><\/p>\n\n\n\n
These pages will explain everything you need to know about Indie and Studio licenses, and about making Mods for games that integrate our Assets.
Importantly, this will allow you to find the information relevant, without being overwhelmed with unnecessary information.
This has also allowed us to lighten the content of the Licensing page, which has been renamed to Licensing General Overview<\/strong><\/a>.<\/p>\n\n\n\n
\n\n\n\n
[License Update]<\/strong>
\u2022 Updated the Candy Dialogue Engine Free Indie, Starter Indie, Pro Indie and Studio Licenses<\/strong><\/a> from version 1.1.1 to 1.1.2.
\u2022 Updated the Candy Dialogue Engine Studio License<\/strong><\/a> from version 1.2.1 to 1.2.2.
\u2022 Updated the Candy Dialogue Engine Genera License from version 1.0.0 to 1.0.1.
This update simply adds the publication date to the licenses. This serves as a complement to the announcements on this page.
As a reminder, license updates<\/span> apply automatically to all Works that have licenses assigned (only sub-version<\/span> changes require your approval).<\/em><\/p>\n\n\n\n
\n\n\n\n
[License Update]<\/strong><\/p>\n\n\n\n
\u2022 Updated the Candy Dialogue Engine Studio License<\/strong><\/a> from version 1.2.0 to 1.2.1
The terms were updated to clarify that any salaries or other such payments for work in connection to a project are counted in the budget. This was already part of the definition, it’s just now made more explicit. For Indie Licenses, the terms were also updated to better clarify that for a Work to qualify as Indie, all associated Creators must qualify as Indie; a minor typing error (missing ‘to’ in “…limited to their respective roles…”) was also corrected. Studio License 1.2.1 also corrects a typing error in 1.2.0: in the definition of “This License” (first page of the document) 1.2.0 incorrectly stated that it applied to version 1.1.0 of the license. Since these are clarifications\/corrections and not changes of the terms, they qualify as updates rather than sub-versions.
As a reminder, license updates<\/span> apply automatically to all Works that have licenses assigned (only sub-version<\/span> changes require your approval).<\/em><\/p>\n\n\n\n
\n\n\n\n
[License Sub-Version]<\/strong><\/p>\n\n\n\n\n
It does not apply to projects that already have an older version of that license, unless they choose to upgrade to version 1.2.0 of the license.<\/p>\n\n\n\n
\n\n\n\n
[Candy DE\/DC]<\/strong><\/p>\n\n\n\n
New tutorial videos are also available on Youtube to show you how to use them.
As for us, our work is not finished yet: we still need to update the product pages on the site, review some of the user documentation, and of course: hunt for bugs.
It’s been a lot of hard work, especially since we’re a team of 1 doing the work of 4 or 5 people, but creating something as ambitious as Candy DE is worth it. Still, we’re glad that things should now calm down a bit and we’ll have time to dedicate to other (smaller) projects we’ve been planning.<\/p>\n\n\n\n
\n\n\n\n
[License Sub-Version]<\/strong><\/p>\n\n\n\n
The terms were changed to allow using the new Candy Dialogue Engine version 1.1.x, as well as older versions (1.0.x).<\/p>\n\n\n\n
As a reminder, license sub-version<\/span> changes are not automatic and require your approval. If you agree to have any of your Works bound by this new sub-version, simply replace the old license PDF file with this new one. If you do not wish to update licenses, you may continue using any versions currently assigned to your Works. When assigning or changing a license, only the latest sub-version may be assigned<\/em>.<\/p>\n\n\n\n
\n\n\n\n
[Candy DC]<\/strong><\/p>\n\n\n\n
It will bring a lot of convenient features to make dialogue writing more comfortable, and it will enable more possibilities in Candy DE for the future.
See our discussion board<\/strong><\/a> to learn more.
<\/p>\n\n\n\n
\n\n\n\n
[Youtube Channel]<\/strong><\/p>\n\n\n\n
\n\n\n\n
[Website Update]<\/strong><\/p>\n\n\n\n
This page lets you determine if your project is eligible for our Indie licenses by answering 5 simple questions.<\/p>\n\n\n\n
\n\n\n\n