{"id":5015,"date":"2026-07-22T23:59:22","date_gmt":"2026-07-22T21:59:22","guid":{"rendered":"https:\/\/candy-arts.com\/?page_id=5015"},"modified":"2026-08-17T06:22:41","modified_gmt":"2026-08-17T04:22:41","slug":"candy-loot","status":"publish","type":"page","link":"https:\/\/candy-arts.com\/index.php\/candy-loot\/","title":{"rendered":"Candy Loot"},"content":{"rendered":"\n

Coming Soon!<\/strong>
Candy Loot is scheduled for release in August 2026.
Stay tuned for updates!<\/p>\n\n\n\n

\n
\n

Candy Loot<\/h2>\n<\/div>\n\n\n\n
\n
\n

Buy Now<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

Advanced Random Outcome Generator<\/strong><\/p>\n\n\n\n

Candy Loot is a random generator algorithm.<\/strong>
Despite the name, it isn’t limited to creating random loot lists: it can be used to generate random outcomes for any purpose, such as characters, encounters, or procedural world locations.<\/p>\n\n\n\n

It works by using a nested tables design, which are simple GDScript dictionaries that possess their own, individual configuration parameters.
It’s compatible with any game made in Godot 4, no matter what kind of inventory system you use, or the items that your game features.<\/p>\n\n\n\n

Writing code that selects random values isn’t complicated, but a well-crafted random generator tool is invaluable and isn’t as simple to design.
The value Candy Loot provides is the amount of control it gives you over probabilities and potential outcomes, its computing performance, and the included testing tool:<\/p>\n\n\n\n

    \n
  1. Configure drop amounts: minimums, maximums and weighted ranges.<\/li>\n\n\n\n
  2. Make items always drop together or mutually exclusive.<\/li>\n\n\n\n
  3. Various draw options: independent\/relative weights, discard\/recast…<\/li>\n\n\n\n
  4. Multiple loot stacking options, with enforceable stack limits.<\/li>\n\n\n\n
  5. Use variable references and expressions for table parameters, to be resolved at runtime (requires Candy Dialogue Engine)<\/em>.<\/li>\n\n\n\n
  6. Write and read tables in external .txt files.<\/li>\n\n\n\n
  7. Testing tool provides helpful stats on the odds and outcomes of loot tables. Results can be exported to CSV files.<\/li>\n\n\n\n
  8. Very fast performance: tens of thousands of draws can resolve nearly instantly.<\/li>\n<\/ol>\n\n\n\n

    Note that Candy Loot is not an inventory management system.<\/strong> It only generates arrays of random data (e.g. items or character attributes). It’s your game’s responsibility to use that data for specific purposes (e.g. add the items to the player’s inventory, or create a character from the generated attributes).<\/p>\n\n\n\n

    For more information, see below!<\/p>\n\n\n\n

    \n\n\n\n
    \n

    Light & Easy<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    Adding Candy Loot to your project couldn’t be easier: drop it in your project folder, then add one script as an autoload in your project settings. That’s it.<\/p>\n\n\n\n

    Querying the algorithm is just as simple: call a function, and pass it 2-3 arguments to define which table to use and what logic to follow.<\/p>\n\n\n\n

    The only real work you’ll do is configuring the loot tables. These are just GDScript dictionaries, and they can do a lot with very little.<\/p>\n<\/div>\n\n\n\n

    \n\n\n\n
    \n

    Full Game Compatibility<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    Candy Loot can work with any game or project. It doesn’t require a specific inventory system, and it doesn’t care what type of items exist in your game.<\/p>\n\n\n\n

    This is made possible by the fact that it knows what its scope is, and it stays focused on it: to generate a list of random outcomes (items). It doesn’t overreach by trying to sort items into your inventory system, or deciding what your item database should look like: that should be fully controlled by your game.<\/p>\n<\/div>\n\n\n\n

    \n\n\n\n
    \n
    \n

    Simple Design<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    Tables work by organizing items into ‘Packs’, which are just smaller dictionaries. Packs can contain other Packs, creating a nesting hierarchy that gives the Candy Loot algorithm a lot of it power.<\/p>\n\n\n\n

    Packs also feature a small number of keys to configure how loot is drawn: drop chances, amounts, or draw method. These keys are optional, in order to keep loot tables small and simple.<\/p>\n\n\n\n

    Together, these features enable infinite possibilities.<\/p>\n<\/div>

    \"\"<\/a><\/figure><\/div>\n<\/div>\n\n\n\n
    \n\n\n\n
    \n

    Draw Modes<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    Candy Loot can use different modes for drawing loot: Independent<\/strong>, where each item has its own chances of being drawn, or Relative<\/strong>, where a limited number of items are drawn among a larger pool.<\/p>\n\n\n\n

    Further options allow you to assign weights to items or remove their entries from the pool — with customizable number of entries to remove!<\/p>\n<\/div>\n\n\n\n

    \n\n\n\n
    \n

    Adjustable Odds and Amounts<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    You can of course configure the chances of each item of being drawn, either as an absolute percentage or as a weight relative to other items.<\/p>\n\n\n\n

    You can also precisely configure the amounts items can be drawn in, using ranges or absolute values, but also the odds of each amount.<\/p>\n\n\n\n

    Lastly, you can define maximum caps to how many times items can be drawn.<\/p>\n<\/div>\n\n\n\n

    \n\n\n\n
    \n

    Join & Exclude Items<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    Need to make sure weapons drop with matching ammunition, or that defeated enemies never drop more than one piece of armor?<\/p>\n\n\n\n

    The nested tables design allows you to ensure specific items are always drawn together or can never be drawn together.<\/p>\n\n\n\n

    It’s very intuitive to setup too: just create a table for each weapon + ammo combo, or place multiple items in a table that is configured to draw only one.<\/p>\n<\/div>\n\n\n\n

    \n\n\n\n
    \n

    Dynamic Table Data<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    In GDScript, when you assign a variable as a value to a dictionary key, it gets resolved when the dictionary is initialized (i.e. when the game starts or the scene loads). That means if the variable’s value is later changed, the dictionary won’t update. This means if you want to design a table to automatically base draw chances or drops amounts on player level or luck, you’d normally need to re-initialize tables regularly or write code that updates them.<\/p>\n\n\n\n

    If your project includes Candy Dialogue Engine, it can lend its power to solve this and considerably increase the capabilities of Candy Loot!<\/strong>
    \u2022 Candy Loot tables will be able to include variable references, which will be looked up every time the algorithm draws from tables.
    \u2022 Even better: tables will be able to include expressions as values, which will also be dynamically resolved each time the algorithm runs, and these expressions will be able to feature variable references!<\/p>\n\n\n\n

    In other words, you’ll be able to do make an item’s drop chances equal to 3 * player_level, or its amount equal to 0.5 * player_luck, or anything else that variable references inside expressions enable!<\/p>\n\n\n\n

    Please note that Candy Dialogue Engine, and a corresponding license, is required for this. The features described here will work even if you don’t use Candy Dialogue Engine for dialogues: the code just needs to be present in your project so Candy Loot can access it. Candy Dialogue Engine is a big addition, but it provides a lot of powerful features that you might find invaluable. Candy Dialogue Engine can be downloaded and tested for free: payment is only required for commercial use, and it’s free for non-commercial projects.<\/em><\/strong><\/sub><\/p>\n<\/div>\n\n\n\n

    \n\n\n\n
    \n

    Outputs<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    Candy Loot’s algorithm keeps things simple: it outputs drawn items as an array, along with their amounts.<\/p>\n\n\n\n

    Stacking options that respect your defined stack limits are also available.<\/p>\n\n\n\n

    Your game code can then easily take these outputs and work with them as needed, such as assigning items to a character’s inventory, in accordance with your project’s own system or database.<\/p>\n<\/div>\n\n\n\n

    \n\n\n\n
    \n

    Not Just Loot<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    Candy Loot is called that way because it was originally designed for generating random loot, but the algorithm really is a general random outcome generator and nothing in the code constrains it to loot only.<\/p>\n\n\n\n

    Some examples of alternative uses<\/span>:
    \u2022 Generate item stats (condition, color, level, bonuses…).
    \u2022 Generate characters (name, skills, physical appearance, personality traits…).
    \u2022 Generate world location properties (terrain type, objects, buildings…).
    \u2022 Generate events\/encounters (NPC type and number, encounter type…).
    \u2022 And more — world lore, factions, quests… The algorithm should be suitable for anything that requires random\/procedural generation.<\/p>\n<\/div>\n\n\n\n

    \n\n\n\n
    \n

    Testing Tool (Table Sampler)<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    \n
    \n
    \n

    If you’ve worked with random generation tables before, you know creating them is only half of the work: the other half is testing<\/em><\/strong> the tables to make sure the drop rates and amounts are accurate.<\/p>\n\n\n\n

    Perhaps you’ve previously spent hours writing code that could read tables and calculate drop rates, or maybe you just chose to test by launching your game and looting items repeatedly, and just guessing if the rates felt right. Maybe you even took the extra step of painstakingly entering drop results into a spreadsheet editor by hand.<\/p>\n\n\n\n

    Candy Loot has you covered:<\/strong> a testing script is included, which can sample any table you designed. It simulates as many samples as you want, and it displays detailed numbers and stats so you can see the average outcomes very clearly, all from inside the Godot editor, without having to run your game!<\/p>\n\n\n\n

    It even offers an option to export the data to CSV<\/strong> files<\/strong>, so you can share the results with colleagues or import them to your favorite spreadsheet software. It includes various export options, including the ability to append new results to previous files in case you need to expand your sample size.<\/p>\n<\/div>\n<\/div>\n\n\n\n

    \n
    \n
    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
    \n\n\n\n
    \n

    Performance<\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    We’ve worked hard to optimize the algorithm and make it as fast and powerful as possible.<\/p>\n\n\n\n

    It’s hard to measure precise benchmarks since there’s many ways tables can be configured, not to mention varying hardware capabilities. But to provide a baseline, our testing on an older, low-end CPU showed the algorithm was capable of making ~200 000 to 500 000 draws per second<\/strong> even in tables that feature millions of potential drops<\/strong>.<\/p>\n\n\n\n

    The actual performance might even be much higher on a modern CPU, or when the algorithm isn’t running through our testing tool. In any case, that’s a huge number for any loot generation scenario — probably overkill.<\/p>\n\n\n\n

    And if you do need to work with such large numbers of rolls, you can hide any latency by performing rolls slightly ahead of time in the background — e.g. as soon as the player enters an area rather than when the results are actually needed.<\/p>\n\n\n\n

    To put it in less technical terms: it’s lightning-fast.<\/p>\n<\/div>\n\n\n\n

    \n\n\n\n
    \n

    Pricing<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    Indie licenses:<\/strong>
    \u2022 Candy Loot costs \u20ac10<\/strong> only.
    \u2022 This includes all Indie license tiers (Free, Starter and Pro), and no additional payment is required when upgrading tiers.
    \u2022 Indie Licenses are valid for one individual. They last a lifetime and can be used by the same license holder for unlimited projects<\/span> without additional payment.
    \u2022 Indie licenses are a special offer to support small projects, priced considerably below the value our assets provide. See the Indie Project Checklist<\/strong><\/a> to determine if your project qualifies.<\/p>\n\n\n\n

    Studio licenses:<\/strong>
    \u2022 Candy Loot is a Minor Asset. Studio projects can use our Minor Assets freely as long as they pay a minimum royalty rate of 1%.
    \u2022 To clarify: Studio projects that already pay 1% or more for the use of other Major or Minor Assets don’t have to pay additional royalties.
    \u2022 Studio Licenses apply per project and have no seat, budget or revenue limits. Royalties are calculated on gross revenue. Studio projects that earn 0 pay 0.<\/p>\n\n\n\n

    Features are identical across all<\/strong> licenses.<\/p>\n\n\n\n

    See our Licensing<\/a><\/strong> page for more details.<\/p>\n<\/div>\n\n\n\n

    \n
    Buy Now<\/a><\/div>\n<\/div>\n\n\n\n
    \n\n\n\n
    \n

    Compatibility<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

    Godot:<\/strong>
    Candy Loot is compatible with Godot Engine 4.
    \u2022 It’s officially supported for Godot 4.4+.
    \u2022 Godot 4.2 and 4.3 are not officially supported but appear to be fully compatible.
    \u2022 Godot 4.0 and 4.1 are not officially supported, but a modified version of Candy Loot is provided.
    \u2022 Candy Tools features only work in Godot 4.3+.<\/p>\n\n\n\n

    Operating System & Hardware:<\/strong>
    Dependent on Godot: hardware and operating systems that can run Godot can run Candy Loot.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

    Coming Soon!Candy Loot is scheduled for release in August 2026.Stay tuned for updates! Candy Loot Advanced Random Outcome Generator Candy Loot is a random generator algorithm.Despite the name, it isn’t limited to creating random loot lists: it can be used to generate random outcomes for any purpose, such as characters, encounters, or procedural world locations. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-5015","page","type-page","status-publish","hentry"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":7}},"_links":{"self":[{"href":"https:\/\/candy-arts.com\/index.php\/wp-json\/wp\/v2\/pages\/5015","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/candy-arts.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/candy-arts.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/candy-arts.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/candy-arts.com\/index.php\/wp-json\/wp\/v2\/comments?post=5015"}],"version-history":[{"count":89,"href":"https:\/\/candy-arts.com\/index.php\/wp-json\/wp\/v2\/pages\/5015\/revisions"}],"predecessor-version":[{"id":5904,"href":"https:\/\/candy-arts.com\/index.php\/wp-json\/wp\/v2\/pages\/5015\/revisions\/5904"}],"wp:attachment":[{"href":"https:\/\/candy-arts.com\/index.php\/wp-json\/wp\/v2\/media?parent=5015"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}