Jump to content

I'm getting Default Loot?

Pending 2.1.7

Bob Kazamakis
Bob Kazamakis

Posted

So this is ... a weird one. 
I have Boss Monsters and NPC Spawn, obviously. Then I use AlphaLoot to control the loot. 

Here is the config in NPC Spawn, showing all the Boss Monsters are going to be scientistnpc_oilrig, reskinned. I've tested this, by setting the "Which loot table..." to 2 for Alpha Loot and it's my usual NPC loot.

"Prefab path used for all NpcSpawn NPCs": "assets/rust.ai/agents/npcplayer/humannpc/scientist/scientistnpc_oilrig.prefab",

Firstly, here's the loot information from the boss I'm editing. Yes, the numbers are very weird because I've been smashing my head against this, trying to understand what's going on.

  "Which loot table should the plugin use? (0 - default; 1 - own; 2 - AlphaLoot; 3 - CustomLoot; 4 - loot table of the Rust objects; 5 - combine the 1 and 4 methods)": 5,
  "Loot table from prefabs (if the loot table type is 4 or 5)": {
    "Minimum number of prefabs": 2,
    "Maximum number of prefabs": 4,
    "Use minimum and maximum values? [true/false]": false,
    "List of prefabs": [
      {
        "Chance probability [0.0-100.0]": 100.0,
        "The path to the prefab": "assets/prefabs/deployable/chinooklockedcrate/codelockedhackablecrate.prefab"
      },
      {
        "Chance probability [0.0-100.0]": 0.0,
        "The path to the prefab": "assets/bundled/prefabs/radtown/crate_elite.prefab"
      },
      {
        "Chance probability [0.0-100.0]": 0.0,
        "The path to the prefab": "assets/prefabs/npc/m2bradley/bradley_crate.prefab"
      },
      {
        "Chance probability [0.0-100.0]": 0.0,
        "The path to the prefab": "assets/prefabs/npc/patrol helicopter/heli_crate.prefab"
      }
    ]
  },
  "Own loot table (if the loot table type is 1 or 5)": {
    "Minimum number of items": 2,
    "Maximum number of items": 2,
    "Use minimum and maximum values? [true/false]": false,
    "List of items": [
      {
        "ShortName": "scrap",
        "Minimum": 150,
        "Maximum": 300,
        "Chance probability [0.0-100.0]": 100.0,
        "Is this a blueprint? [true/false]": false,
        "SkinID (0 - default)": 0,
        "Text (empty - default)": null,
        "Name (empty - default)": ""
      },
      {
        "ShortName": "syringe.medical",
        "Minimum": 10,
        "Maximum": 20,
        "Chance probability [0.0-100.0]": 100.0,
        "Is this a blueprint? [true/false]": false,
        "SkinID (0 - default)": 0,
        "Text (empty - default)": null,
        "Name (empty - default)": ""
      }
    ]
  },

So with this, I should 100% get loot from "codelockedhackablecrate" which, based on every other plugin, should be the loot table that Alpha Loot sets for that prefab, right? If I spawn codelockedhackablecrate from the F1 menu, it's my AlphaLoot profile. Anyway, the issue is with that config, attached is what my loot looks like. I've further tested setting everything to 0% and no loot dropped. So the scrap and syringes are obviously part of the "1" loot table and aren't important [also, if I swap the 5 to 4, they disappear as I would expect]. The issue? Most of that loot does not exist in my loot table at all. Additionally, when I change it to the heli_crate prefab, it's also pulling from a default loot table rather than the table set by Alpha Loot. Normally, I would bring this up with Alpha Loot but much like I said previously, when I spawn a heli_crate, it's my correct AlphaLoot loot table for it. 

I'm really kind of at a loss for what to do. I know I'm going to be hard pressed to get an answer on the eve of a force wipe where things are definitely going to go sideways but yeah, I'm just kinda out of ideas. 



 

lootProblems.png

2.2m

Downloads

Total number of downloads.

10.2k

Customers

Total customers served.

148.1k

Files Sold

Total number of files sold.

3.1m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.