BetterLoot

Moved

Total Downloads: 42,621 - First Release: Feb 26, 2015 - Last Update: Mar 20, 2018

4.95699/5, 93 likes
  1. This update forced my server to wipe because after install it this happen:
    http://i.imgur.com/gYaPXHb.png

    I didnt change anything on the config I just replaced the new plugin with the older and generate a new cfg.
     
  2. The plugin itself can't force any server to wipe! dou you mean restart?
    And the update needs to delete the config file before... as described on plugin page
     
  3. I had the same issue. thankfully i only had 6 players online and one picked it up within an hour.
     
  4. I mean it forced my wipe because people were looting like 70k of c4 and rockets from crates and barrels
     
  5. Perhaps set the default to be vanilla* and make the better loot a opt-in rather than an opt out, Fujikura :)

    *or fairly close
     
  6. As the plugin description says, it will generate the default table by your current stacksize, to easy up the configuration.
    When the stacksize is high, the possible stacks will be the same between low and the maximum, ad the configuration will take those numbers and create the fefault lootTable
     
  7. Oh wow, no longer unmaintained, thank you for taking this project over!
    The stack size thing is strange though, I guess it will just take some tweaking on my stacks x)
     
  8. As BetterLoot does highly change how the server acts, you should only change the version at wipe or test it out on a dev server before. Thats why i posted the extended information on the plugins page.
    [DOUBLEPOST=1466649080][/DOUBLEPOST]
    The complete configuration needed to change to support the plugin at the current state. I decided to take the stacksize into, as this will give the server owner a quick overview on setting the right amount in the tables without the need to compare with the stacksize table.
     
    Last edited by a moderator: Jun 23, 2016
  9. Works great! Thanks for picking this up.
     
  10. Hey, I want Blueprint Fragments to be common but I don't want them dropping 1000 at a time. Default stack size is that I believe, and they are also found in almost every barrel on vanilla servers.
     
  11. Simply decrease the number in the LootTable.json, and then it will spawn lower, or remove trhem from config file, then they stop to spawm.
     
  12. Fujikura, What is the refresh rate on barrel spawns?
     
  13. default should be for barrels AND Crate at 30 mins
    Code:
      "Generic": {
        "dropWeaponsWithAmmo": true,
        "enforceBlacklist": false,
        "listUpdatesOnLoaded": true,
        "listUpdatesOnRefresh": false,
        "refreshMinutes": 30  // <<<<<<<<<<<
      }
     
  14. For some reason, there appears to be no blueprint fragments spawning anywhere.
     
  15. Check your LootTable.json for a line like this:
    Code:
      "blueprint_fragment": 1000,
    can be found in "data\BetterLoot\LootTable.json"
     
  16. So, the stacksize thing fucked up my server pretty hard over the 2 hours I was gone after installing it. I'm talking several thousand rockets just floating around, basically everyone getting raided and stuff, because a lot of my stack sizes are fairly large. It took me a good while to fix that one. Just pointing it out
     
  17. Thats the pointed i did wrote in the plugins description. the default tables are are not in every case click-use-ready....
     
  18. Is it possible to make the boxes of weapons were only weapons?
     
  19. Blueprint fragment's arent common, haven't found any. Even if it's set to 1000 none seem to be spawning, even if it is, I need it to be more common
     
  20. I'll check this.
    [DOUBLEPOST=1466660653][/DOUBLEPOST]
    Not in the current release..but as i always do, i'' remember on it for coming updates if there's a solution which not fukks up the code ;)
    [DOUBLEPOST=1466661478][/DOUBLEPOST]
    I've played around with some settings and 10 boxes with 30 items, and did not get any bp fragments...so i'll need to dive deeper, as planned anyway, into the calculation of spawn chances. Up to this version now the goal was first, to extend the configuration and to fix urgent bugs...

    So hold on ;)
     
    Last edited by a moderator: Jun 23, 2016