Custom Loot 1.2.2

Hi,

I think I’m following. Are you talking about the minStack/maxStack options, and setting that min to zero?
If so the plugin should just completely ignore any items where minstack, or maxstack, is zero,
so they’ll never be picked or created.

If you’re just talking about probability of zero then any category set to zero (and all of the items in it) will be ignored,
and any item set to zero, regardless of its category’s probability, will be ignored.

If there’s only one category and item (in it) with probability above 0, then that item will always be picked and created, cos there’s no other choice.

I order to give that item a chance of not being picked, there needs to be at least one other viable item which could be picked instead.

I.E. You can set the plugin up to create wood or stone, for example
but you can’t set it up to create wood or nothing.

It’s hard to describe but people usually get a feel for it.
If everything was probability zero except for

category tools 1
    item timed explosve 1

category Resources 9
    item wood 1
    item stone 1
 

Then for every item created there’s a 9 in 10 chance it’s going to be a resource,
and beyond that it’s a 50/50 whether it’s wood or stone.

1 time in 10 the item will be a tool and if it is a tool, it’s guaranteed to be c4, because there’s no other option.

When people are starting out I often suggest that they pick a handful of common items that could make up their base common loot, and set the probabilities for those items to something a good bit above zero, to allow room for other things to be less common.

Say you have wood with a probability of 10, for example,
you could then have stone at 7 so it’s less common and scrap at 3 so it’s even less common.

If the only category enabled was resources with those three items set that way,
and the profile’s asking for one item (for simplicity) then, on average, you’d get

scrap 3 time out of 20
stone 7 times out of 20
wood 10 times out of 20.

Of course I don’t expect anyone to follow the actual fractions like but you get the idea - It becomes a ‘feel’ thing.

I'll look into that and see what the problem is.
If MinStack or MaxStack is zero I ignore that item.
I guess the problem is that if it was the only item with > 0 probability I now need to ignore the category too.

I think I'll just force min+max to 1 if the user puts in 0 for either. That'll silently fix it.

For your apparent imbalance, I'lll see if I can replicate that or, better yet, maybe you'd attach or DM me that loottable json data file?
Looking at those numbers it should, I think, appear to be food heavy, as there's 4 items asked for a and a 50/50 chance of any given item being food.
 

Having 'AllowDuplicates' set to false in the global config can skew things for sparsely populated tables.
If, for example, it tries to give out raw bear meat twice, it'll just ignore the second attempt and roll again.

Be aware, though, that AllowDuplicates : true can make it look like you're getting fewer items
because if it gives Bandages : 1, Bandages : 2, raw meat 1, raw meat 3,
that's your four items but they'll stack into
Bandages :3, raw meat 4, and just look like two items.

Hey, thanks for coming back to update.
That's good to know.

Hopefully that's the answer to what was going on but if you still find anything's not quite right don't hesitate to let me know,
Forcing Min/MaxStack to 1, if 0, is a one-line fix. I actually did it at the time so it'll be in the next update.

Always nice to catch a bug.

In the config for each entry you'll find a setting called "gunsWithAmmo"
If you set that to true then any guns which spawn will be accompanied with an amount of appropriate ammunition.

To directly answer your question, though, no. You can't have multiple loot tables apply to any given container type.

If memory serves you should keep the probabilities to zero for those ammo items - gunsWithAmmo is a probability ignore/override setup,
but the settings for minstack + maxstack are taken into account
so that you can manage the amount of ammo that will spawn with each weapon.

There's API so that other plugins can make calls to CustomLoot.
RandomRaids could offer that as an option, if it doesn't already.

Oh, I see.
Yes, CustomLoot does nothing at all unless you enable profiles within the config and set up a valid loottable to go with them so, simply put,
if you just install it on the server and do nothing else, it wont change or interfere with anything.

What you'd do is install it, set up RandomRaids config to use a CustomLoot profile name (which you make up),
then the first time RandomRaids tries to ask CustomLoot for loot, CustomLoot will create a config entry, under API, of that name.

In console you'd see the following as confirmation.
                CustomLoot had a call for a profile that doesn't exist.
                Adding profile {NameHere} using loottable 'default'.

From there you can set up that new profile as if it was any other.

If you need any help beyond that, let me know.

Thanks for the answer @Luuxen
I wouldn't have known that - You saved me some time.

I can only guess, without knowing a bit more,
but if true/false is the only option I'd assume it's giving you the option to prevent CustomLoot from filling some container/corpse, in the event that you already have CustomLoot set up for that container/corpse type.

I can only really reiterate what I said before, because I don't know that plugin,
but my assumption would be that if you already have CustomLoot set up to put loot on the type of npc that plugin spawns, then the option provided would let you prevent that from happening for BossMonster npcs.

It sounds like when I had 'Allow_Alphaloot' in BotReSpawn.
I had dozens of people asking 'where do I put the loot table name' when, really, the option was preventative and should have been called 'Prevent_Alphaloot'.

Maybe the author would consider adding "CustomLoot_Profile" as a string option, and making their own call for loot to CustomLoot if that's not empty.
That would give more control.