1. A note to new members who are making their first purchase

    Once you have made your first purchase you will be unable to instantly download. Due to the recent influx of fraudulent purchases we now need to verify your account before we can grant access to download.
    To verify your account/purchase please email admin@chaoscode.io from the email address your PayPal account is registered to and state your ChaosCode username and the name of the plugin you have purchased.
    Once this is done access to your download your purchase will be granted.

    Please be aware that the verification process may take up to 24 hours!

    We apologise for any inconvenience this may cause
    Dismiss Notice

AlphaLoot 2.4.17

Provides complete control on loot contents of each available lootcontainer

  1. AlphaLoot

    - Featurelist overview -
    • Each Loot-Container type has a separate Item list
    • Each Loot-Container type has its own settings for item counts, scrap amounts, number of possible blueprints, and a lootfraction-switch
    • For Heli- and Bradley-Loot exists a special loadout option
    • Full FancyDrop droptypes support by separate lists (currently 5)
    • Supports all approved WorkShop skins to be available for random skinning
    • Per each item category its able to spawn items randomly skinned
    • The presets are adjustable by each item category (more info below)
    • It will remove stacked Loot-Container often found in towns
    • It makes sure every Loot Container is populated with stuff
    • It prevents the spawn of multiple equal items per Loot-Container
    • Most needed configuration steps can be done by console commands
    - First Install -
    Once you installed the plugin the first time, you get the folllowing files created:
    • \config\AlphaLoot.json
      The plugin main config with the functional config switches, LootCategorys and WeaponSpawnSetup
    • \data\AlphaLoot\LootTables.json
      holds the generated container-settings for the common in game used lootcontainer types;
      holds the lootcontents for each of these containers types
    • \data\AlphaLoot\BradleyLoot.json
      both files contain the same type of dedicated loot-setups for heli- and bradley(apc)- crates
    • \data\AlphaLoot\FancyDropLoot.json
      would hold dedicated FancyDrop lootcontents, but not yet used at clean install
    • \data\AlphaLoot\ItemRaritys.json
      holds 2 generated lists for Item- and Blueprint- rarities, which the plugin uses for different weighting purposes between low-end & high-end stuff.
    • \data\AlphaLoot\LootFractions.json
      Holds an export of item-(health)-fraction defaults to change item spawn-healths
    • \data\AlphaLoot\NamesList.json
      Complete game-item overview to be used as reference (read-only-export)
    You get initially prompted by AL with this message:
    This is the time to make your personal flavored changes to the plugin loot-tables.
    Technically the initial generated loottables/itemlists are strictly vanilla matched, the same is valid for the different container settings like item-counts or like scap values.

    Many people need initially a quick option to multiply the default loot, done by:
    Usage Examples:
    Code (Text):
    al.lootmultiplier 5 all // multiplies all tables/files by 5 based on vanilla amounts
    al.lootmultiplier 4 tables // multiplies LootTables.json by 4 based on vanilla amounts
    al.lootmultiplier 3 bradley // multiplies BradleyLoot.json by 3 based on vanilla amounts
    Followed by this:
    Code (Text):
    And you got it up and running with your set multipliers. Example output after being enabled:
    - Managing "LootTables.json" -
    This file is autofilled with ALL common used container-types being used inside procedural maps.
    It's divided in two sections:
    • LootContainer > holds all container specific settings
    • LootData > contains per each container all related items taken from the server-defaults
    Each LootContainer has these varying switches, shown by example below:
    Code (Javascript):
      "LootContainer": { // << begin of the LootContainer section
        "crate_basic": { // << begin of settings for crate_basic
          "Enabled": true, // TRUE to be used for lootpopulation, FALSE would ignore this type on the map
          "Items": 1, // basic amount of Items to spawn
          "ItemsVariance": 1, // second amount option to vary/randomize; Can be negative, zero or positive
          "LootFraction": true, // TRUE lets the container spawn items with reduced health; based on "LootFractions.json"
          "MaxBlueprintSpawns": 1, // defines the max possible amount of Blueprints per each lootpopulation
          "ScrapAmount": 3, // basic amount of scrap to spawn; get spawned into extra slot, counts not towards the set Item-amount
          "ScrapVariance": 1, // second amount option to vary/randomize; Can be negative, zero or positive
          "UsedMultiplier": 1, // this multiplier will be used in combination with the lootreset command
          "UseMultiplier": true // TRUE to use the above multiplier; FALSE would consume the LootCategorys from the main-config for category-based multipliers
    The final Items-amount can be defined in multiple ways:
    (the same principle is valid for ScrapAmount & ScrapVariance)
    Running the plugin with itemAmountMinMax FALSE does generate for each container also a MinAmountDivider value, with 1 as default.
    This can be taken, on values greater than 1, to reach a simple item.amount randomization across all ranges. Examples:
    The divided result gets always rounded up to the next full number.
    Therefore its never 0 or something like 0,333

    Each LootData is mainly structured like this:
    Code (Javascript):
      "LootData": { // << begin of the LootData section
        "crate_basic": { // << begin of items for crate_basic
          "barricade.stone.blueprint": { // a Blueprint for the Item barricade.stone;
            "Max": 1, // blueprints got always 2 values like items, but these are ignored
            "Min": 1 // blueprints are always limited to 1, regardless of Min|Max
          "barricade.wood": { // the Item barricade.wood
            "Max": 1, // maximum amount to spawn this item
            "Min": 1 // // minimum amount to spawn this item
    Items can be marked as Blueprints with a trailing ".bp" or ".blueprint" after the shortname.
    Each Item can exist in every list as Item & as BluePrint. These Blueprint functions do work inside every loottable/itemlist across the plugin.
    The Min|Max configuration style can also be switched into a simple-value variant by changing "itemAmountMinMax" in the mainconfig to FALSE

    To manage the LootTables.json manually it's highly recommended to use an input and edit-assisted service like http://jsoneditoronline.org/#/
    The plugin does also provide several console-commands to assist you on managing items across all containers inside the LootTables.json:
    • al.itemlimit > Sets the maximum item limit for an item across all containers
    • al.itemremove > Removes an item complete across all containers
    • al.itemfind > Shows the entries for a specific item
    • al.itemadd > Adds an item to one or multiple containers
    • al.searchitems > Search any game item(s) by name, partial name, Id's, descriptions
    • al.shownewitems > Lists ANY new game-items since last protocol update
    Furthermore are the container-types being manageable by command support:
    • al.containertypes > Overview of all added container types and their settings
    • al.containeradd > Adds a not yet included-but-available containtertype to the file
    • al.containerreset > Resets a specific containtertype complete to the defaults
    • al.containerremove > Removes a specific containtertype from the file
    To manage the loot also simply by multiplication needs, you can use:
    • al.lootmultiplier > needs as arguments the desired multiplicator and the tables argument
    Code (Text):
    al.lootmultiplier 3 tables // multiplies all items of  LootTables.json (based on vanilla amounts) by 3
    This does also set the UsedMultiplier for each container to 3.

    There's also the option to manage multiple factors inside one container, based on the ItemCategories of each item. This is done by the LootCategorys located inside the main-config.
    Switching UseMultiplier in LootTables.json for one or multiple container-types to FALSE does activate the usage of this function.
    This part is working as described below:
    Code (Javascript):
      "LootCategorys": { // begin of the section
        "Limits": { // begin of the section
          "Ammunition": { // category Ammunition
            "DropSkinned": false, // TRUE enables skinned loot (in case of available skins per each item)
            "LootMultiplier": 1 // the multiplier preset for this category
          "Attire": {
            "DropSkinned": false, // TRUE enables skinned loot (in case of available skins per each item)
            "LootMultiplier": 1 // the multiplier preset for this category
    To use this now functions now, you can set inside LootTables.json different UsedMultiplier values, change also some containers to UseMultiplier FALSE, manage inside LootCategorys the different LootMultiplier value's, and do finally reset the loot by:
    Code (Text):
    al.lootreset tables
    This has then recreated all item-amounts based on all the different multiplicators.
    NOTICE: This method by resetting the tables does revert any before made changes to unique items. Do fine-adjust only after the base is made. Also take care of al.lootmultiplier command running on tables, it would instant revert any of these different adjustments.

    - BradleyLoot | HeliLoot -

    Each of these files is dedicated to one container-type only:
    • BradleyLoot.json > bradley_crate(s) spawned by destroyed APC
    • HeliLoot.json > heli_crate(s) spawned destroyed PatrolHelicopter
    They contain this header used as container-settings area:
    Code (Javascript):
      "CrateSettings": {
        "CratesToSpawn": 3, // the number of crates being spawned on destroy (APC|Heli)
        "LootFraction": false, // TRUE lets the container spawn items with reduced health; based on "LootFractions.json"
        "ScrapAmount": 0, // basic amount of scrap to spawn;
        "ScrapVariance": 0, // second amount option to vary/randomize; Can be negative, zero or positive
        "UsedMultiplier": 1 // this multiplier will be read in combination with the lootreset command; gets also changed by lootmultiplier
    These files do contain multiple "Item-Sets", arranged in a array.
    To manage these arrays with ease, it's highly recommended to use an input and edit-assisted service like http://jsoneditoronline.org/#/

    When the APC|Heli gets destroyed, it will spawn an amount x of crates.
    Each of these crates gets populated with exactly one of the Item-Sets.
    As long the number of Item-Sets is larger then the number of crates, every crate gets a different set populated. This usually the case based on the given defaults.
    There's no further command-support beside the already mentioned al.lootmultiplier command.
    Code (Text):
    al.lootmultiplier 3 heli // multiplies HeliLoot by 3
    al.lootmultiplier 4 bradley // multiplies BradleyLoot by 4

    ...not yet completed...

    Example of ItemRaritys.json:
    • None = 0
    • Common = 1
    • Uncommon = 2
    • Rare = 3
    • VeryRare = 4

    NOTES for Blueprint handling (shortly taken from update 2.0.0)
    • Blueprints are now fully integrated into the configs in same way like items already are.
    • The default loot-table exports, initially or re-created, do hold now additionally any blueprints of those items which are marked by default to spawn as blueprint
      These entries do have a trailing ".blueprint" extension for their shortname to mark them noticeable as blueprint. You will notice these already in the created defaults.
    • Own changes to the loot tables or itemsets can be filled by the known shortnames including a traling ".bp" or ".blueprint" text extension. Both are being accepted.
      These entries do still need the min/max parts, even when the blueprint is always spawned as "1".
    • The new system lets you therefore spawn the item and it's bluprint in the same loot type.
    • The "ItemRaritys.json" does now also hold the "ItemBlueprintRaritys", to be managed by own personal needs.
    • The former implemented "SpawnAsBlueprint.json was obsolete now and removed again.
      (The file might still be there, but without function)
    • Each container type got added a "MaxBlueprintSpawns" option to limit the max possible spawned BP's per each type.
    • for every loot handled by or from the "LootTables.json" the plugin got added in the mainconfig the global valid "blueprintProbability" with a default of "0.11". This value ranges somewhere at ~10% chance to spawn a blueprint into a container. Possible Lowering f.e. "0.05".
    • In the "FancyDropLoot.json" you will find the equivalent option "BlueprintProbability", to be used for the same approach on FancyDrop loot contents.


    1. Screenshot_3.jpg

Recent Updates

  1. 2.4.17
  2. 2.4.16
  3. 2.4.15

Recent Reviews

  1. Filth
    Version: 2.4.17
    Great plugin just wish it had presets for special server types like a primitive loot table preset
  2. BadonkaNae
    Version: 2.4.17
    Very nice loot plugin, and skins?!
    Thank you!
  3. Black_demon6
    Version: 2.4.17
    That's a Freaking good plugin ! Great job !
  4. FredSanchez
    Version: 2.4.17
    Excellent plugin and the best one for changing your loot tables. Super easy to use and easy to configure.
  5. kripto420
    Version: 2.4.16
    Hands down a necessity for server owners! If you are driving your self crazy trying to perfect your loot tables with other plugins your doing it wrong.
  6. Adrian Perez
    Adrian Perez
    Version: 2.4.15
    Best plugin to manage your server loot! You have to use it, because it let's you to manage all the server loot ;) Really useful.
  7. michiel marcelis
    michiel marcelis
    Version: 2.4.14
  8. Weszz
    Version: 2.4.14
    Really good plugin, im only missing the loottable for scientists tho. other then that, good job on this ;d
  9. snetzer
    Version: 2.4.14
    best Loot Plugin ever.. thx
  10. BoomInYourFace85
    Version: 2.4.14
    Best Loot plugin I've used. Time consuming but so easy to change things up and know exactly what's in each container.