AllTheLoot 1.0.6

Where or How did you get your gear and some items to change colors on the background?

You refer to the picture I previously had in this posting? Hmmm, good question. I don't have any mod that changes the background color. The green background of the Spear gun could have been a result of the preview mod I used back then.

Raid overhaul is causing to crash too

Yes, that would be the way to go.

See the relative spawnrate as following:

If you have 1000, 1000, 1000, 1000 the summed up value will be 4000. With the amount of 4 elements and normalized to 1 it's 0.25 (i.e. 25% chance).

Same if you use e.g. 5, 5, 5, 5 or 1, 1, 1, 1,

The key tool is of type "STORAGECONTAINERS" and can only spawn in a technical supply crate. But chances are quite low

Thanks G

You can do that, yes. Though since the labs keycards can spawn in cabinets and jackets (assuming you left the default config value to true) if you change the spawn rate either via the selected items config (more precise way of tweaking) or the favorite config, you will increase the spawn rate both for cabinets and jackets.

1. that's possible but you have to go into the mod source file (AllTheLoot_Main.ts). At the bottom you see the actual assignment of categories. Just search for the category "AMMO_PACKS" and "AMMO_ROUNDS" and add the container of your liking.

For e.g. Ammo rounds go to line 1374 (case SPTLootCategoryName.AMMO_ROUNDS:)

and add below a line according to this way:

this.containerTypeYOURDESIREDCONTAINER.push({...currentItemCopy});

If you want to add it to the green weapon box (the big 5x5 I guess) it's actually already added, but it's blocked to spawn because of the item value check.

To counter this, the easiest would be if you go to line 316 and simply add

item.itemLootCategory === SPTLootCategoryName.AMMO_ROUNDS

item.itemLootCategory === SPTLootCategoryName.AMMO_PACKS

Like such - and if you have "AlwaysIncludeWeapons" set to true in the config - rounds and ammo packs will always spawn in 5x5 boxes, even if they are much below the preferred item value.

2. For this you need to go the hard way and find out the corresponding IDs and add them either to the favorite item config or you can add them to the selected items config. Latter allows you to set the spawn chance in a more detailled way (e.g. make ammo type A spawn more likely than ammo type B).

3. If the weapon mod is correctly set up, yes it is possible - and you don't need to do something specific. In the end AllTheLoot adds everything that's listed in the handbook, The only thing which could block a weapon to spawn in a container is either the size (if it's super huge, i.e. above 6x3 size) or if its value is too low/high and it will get removed by the value checker.

Hi lElwoodBluesl,

Thank you sooo much for providing extra feedback!

And thanks again for your mod! It is the best mod hands down to tweak item spawns in containers. Once you play with config, you really can adjust the spawn rates to your liking. It is AMAZING!!! And works perfectly with custom weapons and items.

Thank you very much!

I think I got myself an answear by using this mod for few raids. I only enebled drawers and jackets and I set values for "0","1" and I think I have what I wanted
I noticed that appart from this bits which I tweaked I also have the All the Loot as I got surveliance camera out of a drawer.

Good thing as I play my own rules, flea market disabled.
So only little annoying thing is the way spawn chance for specific iteam is handled in this mod.

I need to count lines for

"selectedItems_AdjustSpawnChance":[

and then go down to

"selectedItems_spawnChance":[

and set the chance for spawn for chosen item hoping I did not change spawn chance for some other item.

It should be organized better for example

"Items_Spawn_Chance"

"item id": "5af0534a86f7743b6f354284",

"name": "Ophthalmoscope",

"spawn chance": "0.5"

It would be more clear and fun to edit config.

Hey man. Great to hear you found a way. Well, the structure behind setting up the loot is not up to me/my mod. AllTheLoot simply adopts to how SPT organizes the loot spawn, i.e. for static loot via container ID, amount of possible items in one container, and chance of how many items will spawn in the container.

As you wrote, if you want to have a 50/50 chance with either 0 or 1 item, the solution is to set the container.json to 0 and 1 and assign twice the same number (e.g. since it's relative spawnrates, you could also use 1000 and 1000 )

Please tell me how it works and is there a difference in those numbers:

For example

"container_Drawer_ItemsDistributionProbabilities":[

"2000000","10000"

and if it would look like this

"container_Drawer_ItemsDistributionProbabilities":[

"20000","100"

Why such big numbers there is set like 2 milion instead of smaller numbers?

What do you mean with "new items"? If you mean to add only the items that are currently not in the loot table that would require some tweaks in the code itself.

If you want to keep the vanilla items (incl. their spawn rates) the steps would be to:

- first find out what items you want to add, i.e. which IDs

- then, to avoid doubling the spawn chances if the item is already existing in the loot table and would be added again -> check if those items (IDs) are already covered in the staticLoot.json or not

- rewrite the code in the file "AllTheLoot_FillContainers" at the section where it does the default SPT container overwrite check and instead of providing only the info retrieved in line 40 (i.e. the SPT default loot table), add to this staticLoot variable the "new" items (including hardcoded spawn chances, since filling the containers is the very last action done by the mod and setting spawn chances comes earlier)

- finally, in the "config_Containers_ID.json" set the overwrite flag for all containers to false

The mod only adds items to containers. In Marked Room you mainly have loose loot. If you want to increase/modify this, you need a mod that adjusts loose loot.

If you up the card spawn you will only have a higher chance of a card spawning in a drawer or a jacket.

Blacklisting is the way to disable certain items to spawn. For most containers, I don't add every item by hand but instead use the different categories (e.g. Barter Electronics, Barter Valuables, etc.). If I don't want to have a specific item from such category spawn in that container, I simply blacklist it.

In addition to that there's also a global blacklisting. This approach is used to mainly remove items which have no real purpose (e.g. softair ammo), are boss-specific (to avoid e.g. a Tagilla vest spawn) or some developer related items (like e.g. the dev balaclava which is listed in the handbook too and would spawn).

Thanks you, its very clear now ! have a nice day

It's not really weird, linux file system is case sensitive, while SPT is primarily on windows which uses a case insensitive file system, hence the issue had most likely slipped past the developer and most users.

Regardless, it would be nice for this to be fixed.

You can check the spawn rates by activating the option in config.json

"debugMode_showContainerInfo": true,

Then - since Keycards only spawn in drawers or jackets - set

"debugMode_containerIndex": 0,

or

"debugMode_containerIndex": 3

0 = Drawer, 3 = Jacket (if KeycardsInJackets true)

You will see that the Green Keycard (TerraGroup Labs keycard (Green)) has an extremely low spawn rate of 13 (and that you have been very very lucky )

P.S. in general the category spawnrates will adjust the calculated spawn rates, i.e. if e.g. a item has a spawnrate of 3000, having "rate_xx": 0.05, would result in 3000*0.05 = 150

Awesome! Thank you!

So the general spawnrate is tied to the map then? Because I found it on reserve which has electronic keys at 0.05 which means with a spawn rate of 13 and category spawnrate of 0.05 it would be 0.65?

No, it's not map specific. It's global.

The spawn rate of 13 already covered the 0.05 category rate.

The first thing to check are all the mods that add custom weapons or magazines (as that's causing the infinite loop once custom items are drawn by SPT to spawn in one or more containers).

Deactivate all those mods and use one after another and load into a raid.

If you found a mod causing the problem, you have 2 options. Either by manually removing and including presets (from the problematic mod) or increase (one after another) the probility rate of the custom items. I explained that already in another posting below.

Thank you for the reply. I will try this out. I'm sorry for asking the question if it was already answered like I said I'm still new to all of this.

If you leave the debug option to list a certain container content to "false", the server window will only show you the amount of globally blacklisted items. If you set the debug option to "true", you'll see all kind of info about the container, i.e. included item categories, relative probabilities, etc. and at the very beginning the amount of items initially being assigned and left after (local) blacklisting has been applied.

If you want to remove them completely from the loot pool, the easiest would be to blacklist them globally in the container config file.

Regarding keys. All keys in the game (except Unknown Key and Shturman's Stash Key which are blacklisted globally) can spawn.

If you want those 2 keys spawn too, you have to remove them from the global blacklist section in the containers config file.

The distribution is a combination of this mod (relative probability to spawn) and SPT's draw mechanism. The mod adjusts the relative probability based on the item value, i.e. a cheap item (key) will spawn more likely than an expensive one. Keep in mind, to evaluate an item being cheap or expensive it will look at the handbook price - not the value listed on the flea.

P.S. since I'm currently out for a business trip I cannot check if "Machinery Key" is locally blacklisted for Drawers and Jackets.

Whenever you get stuck while the raid loads, please check the server window. Chances are meanwhile close to 100% that another item mod (with non-properly set up items) is the reason for this behavior.

yeah, according to what i could see its trying to populate some unknown ammo type and item descriptions. I have MultiplyAll which mainly multiplies loot, and Raid Overhaul, but im not sure if that affects loot types or anything.. but i just read someone else has the same "starting local game" error with Raid Overhaul. That would suck if that's the case, only one way to find out though.

So i found after disabling, or setting value to "false" in Raid Overhaul for Custom Loot, this problem doesn't occur anymore when trying to load streets in junction with this mod. After reading some other comments, i think the "custom loot" the Raid Overhaul is trying to generate in game is causing code interference when loading maps with this loot mod installed.

Thanks for the investigation.

If the error occours during custom loot generation, what you can do is check that Overhaul mod for the parts that add custom loot. I would first check the gun presets by adding all new guns (IDs) to the "selected Items" config, set every newly added ID (except one) to 0.0. and increase the remaining one to a value of e.g. 100000, to guarantee an ~100% spawn chance. Start a raid and see if it's loading. If yes, set the its value back to 0.0 and increase the next newly added item to 100000. It could be one item, it could be multiple newly added items, i.e. so do that procedure with all newly added IDs.

They both are loot based mod, and by nature they cant be compatible with each other.

Not true, if the priority is set correctly it is fine, the only issue is with the error this mod throws itself causing the infinite loading or extremely long loading times.

Whenever you get stuck while the raid loads, please check the server window. Chances are meanwhile close to 100% that another item mod (with non-properly set up items) is the reason for this behavior.

For SVM I guess there should be no conflict. Either you load SVM first, then AllTheLoot will set the amount of loot per container, if SVM is loaded after, SVM should take care of that.

Regarding PityLoot - and since it has a loot progression - I personally don't know if the randomizer (default: on) and updating the spawn rates after each raid eventually has an impact on the way PityLoot calculates the progression.

I didn't put it in the readme. Looking at the code once more, probably would have made sense to add it.

First of all, the initial rates are calculated based on the handbook price. I wanted to avoid the very cheap (specifically weapon part) items of spawning too often, same time I had to guarantee that necessary low value items (like e.g. cheap barter quest items) still have a normal spawn rate. For this I introduced - not accessable via config - the "selectedCategories", Those categories are:

"BARTER_OTHERS",
"BARTER_BUILDINGMATERIALS",
"BARTER_ELECTRONICS",
"BARTER_ENERGYELEMENTS",
"BARTER_FLAMMABLEMATERIALS",
"BARTER_HOUSEHOLDMATERIALS",
"BARTER_MEDICALSUPPLIES",
"BARTER_TOOLS",
"BARTER_VALUABLES",
"AMMO_ROUNDS",
"PROVISIONS_DRINKS",
"PROVISIONS_FOOD",
"MEDICATION_INJURYTREATMENT",
"KEYS_MECHANICALKEYS",
"MONEY"

As soon as the initial spawn rate is assigned, the mod will check for very low value items if the item is part of one of the selected categories or not.

The Tiers are as following:

Tier7": Item value <2000 and not part of "selectedCategories"

Tier6": Item value <2000 and part of "selectedCategories"

Tier6": Item value >=2000 and <20000

Tier5": Item value >=20000 and <50000

Tier4": Item value >=50000 and <100000

Tier3": Item value >=100000 and <400000

Tier2": Item value >=400000 and <1000000

Tier1": Item value >=1000000

Hope that helps.

ohhh thanks for clarifying ^ ^
so if i understand it correctly the tiers are seperated by value and not by specific items in a pre made list?
and would it make a difference if the value is higher but in the same proportions to eachother for example would
Tier1: 1000
Tier2: 2000

have the same probabilities as
Tier1: 10
Tier2: 20

Yes, 1000 or 10 would be the same.

But there are some more steps

Once the initial spawn rate is assigned, one of the next steps is normalization, i.e. all the items in one container are checked to which category they belong, how many items of that category are in the container and how many items are in total in that container. This step is necessary to avoid e.g. only key spawns in Jackets/Drawers as there are so many more items of type "Mechanical keys" compared to other objects.

Probability or finally spawn chance is always depending on the min/max relative probabilities, the relative probability for a certain item and the total amount of items in that container type.

huh goood to know and thats a smart way of handeling that ^ ^
well thank you for the mod and the info time to become a loot goblin again

Yep, that's why the according instruction is in the code

This is the only loot mod I use and it has been working just fine with 3.8

The SPT launcher gives an error and does not load mods

change the version to 3.8 in the package file. I have also used it with equal loot mod and no problems with it.

Mod is updated.

Yes, the Glorious mask (as part of "Gear/Facecovers") should spawn in stashes but also duffle bags, dead scavs, plastic suitcase and (where I found most of them) in jackets.

Interesting, I got no clue why I don't ever see it. Is there a way I can up the spawn rate for testing purposes? Thanks.

Just for future reference or others reading: Weighing chances for specific items is practically impossible as far as I'm aware. It's more of an issue with the way the server processes game information, you can change what items and parent classes are available or not in a specific trader/container - but individual item chances for spawns, again as far as I know, isn't something that can be done.

"Weighing chances for specific items is practically impossible as far as I'm aware"

It seems you are not aware

Do you know how the loot creation actually works in SPT? I mean, not the basic assignment to containers but the actual loot drawing when the raid gets loaded?

The reason why you have e.g. much less LEDx compared to bolts in a cache container IS the weighting, which is done by relative spawn rates. For sure, you cannot set a 100% chance that item A is spawning in container A but you can adjust its chances. Finally it's a combination of relative spawn rates and amount of items being assigned to a container.

Shoreline doest work at all

upd: probably set noAmmoValueWeightingForMagazines = false fix issue

Well, AllTheLoot v1.0.5 supports only up to SPT 3.7.6.

Once you go to Ground Zero (and its new containers which aren't integrated in v1.0.5), it probably will crash with another error.

P.S. the error you mentioned is based on a magazine / magazine of a weapon that didn't spawn in your first raid, like such wasn't filled with any (custom?) ammo rounds.

noAmmoValueWeightingForMagazines shouldn't have any impact (on stacking the magazine) as it's simply setting the spawn rates for all registered ammo types to the same value.

> like such wasn't filled with any (custom?) ammo rounds.

Unfortunately no. I just changed the mod settings and tried to load into the shoreline over and over again, and got an error over and over again until I made this parameter false. I went on a raid with MPX and 50-round drums loaded with Luger, and played 3 raids in a row without an error... maybe lucker =)

upd: i also comment this lines:

_{//tables.loot.staticAmmo = staticAmmo;}

_{// Calculate the number of different calibers in staticAmmo}

_/*

_{if (this.config.debugMode_ShowAmmoCalibers) {}

_{let counterAmmoCalibers = 0;}

_{for (const caliber in staticAmmo) {}

_{this.logger.warning(caliber);}

_{counterAmmoCalibers++;}

_}

_{this.logger.info(counterAmmoCalibers.toString());}

_}

_{if (this.config.removeBackpackRestrictions === true) {}

_{const backpacks = tables.templates.items;}

_{category_Gear_Backpacks.forEach(item => {}

_{backpacks[item.Id]._props.Grids[0]._props.filters = [];}

_});

_}

and

_{if (data[i].ParentId === "5b47574386f77428ca22b33c") { // Ammo||Ammo packs}

_{category_Ammo_AmmoPacks.push(data[i]);}

_{category_Ammo_AmmoPacks_ref.push(data_ref[i]);}

_}

_{if (data[i].ParentId === "5b47574386f77428ca22b33b") // Ammo||Rounds}

_{

_{category_Ammo_Rounds.push(data[i]);}

_{category_Ammo_Rounds_ref.push(data_ref[i]);}

_{// fix for custom ammo types}

_{let probabilityAmmo = 0;}

_{if (this.config.noAmmoValueWeightingForMagazines) {}

_{probabilityAmmo = 1000;}

_}

_{else {}

_{if (data[i].Price < 100)}

_{probabilityAmmo = 1000;}

_{else if (data[i].Price >= 100 && data[i].Price < 1000)}

_{probabilityAmmo = 500;}

_else

_{probabilityAmmo = 200;}

_}

_{let currentCaliberType = tables.templates.items[data[i].Id]._props.Caliber;}

_{if (!(currentCaliberType in staticAmmo)) {}

_{staticAmmo[currentCaliberType] = [}

_{{ tpl: data[i].Id, relativeProbability: probabilityAmmo },}

_];

_}

_else

_{staticAmmo[currentCaliberType].push({ tpl: data[i].Id, relativeProbability: probabilityAmmo });}

_}

but I still got the error over and over again (more than 5 attempts to load to shoreline) until I set the parameter to false

Maybe it's luck after all...

Did you have the error with SPT 3.7.6 too?

btw, it has nothing to do with what weapon you bring into the raid, it is the magazines/weapons that spawn as loot.

I haven't checked =)

but the mod worked great at customs and the interchange, so I will continue to use it. I hope that my solution will somehow minimize the occurrence of errors, so that I can say that it is 90% compatible with the new version of SPT :D. Thank you for the great mod)

With this version you should normally only get errors with not properly set up weapon presets from mods that add custom weapons.

Once there is a faulty part in one weapon preset (a preset basically builds up the complete weapon) you will get the error.

Blacklisting doesn't work because as long as the preset is available SPT will still try to build up the weapon and if it misses certain parts you'll get another type of error

What I did instead was "fixing" the issue by actually modifying the preset, i.e. either delete the complete preset (that causes trouble) or by deleting only a specific part of it (e.g. the silencer, magazine).

To find IDs (from parts added by a mod, not the mod itself) the IDs normally can be found in config or database files. Typically the parameter is called "id", "tpl" and has a somehow random, 24 digit value. For other mods like e.g. the (awesome) mod Gilded Key Storage you will find the necessary IDs in the file config/config.json, though for this mod the item IDs use clear names, like e.g. "Golden_Key_Pouch".

v1.0.5 doesn't yet have a global blacklist - but v1.0.6, which will be released with SPT 3.8.0, will have one.

Oh okay thank you, I'll have to get rid of some of these mods preset weapons, so just making them "incomplete" be getting rid of just a suppressor or sight or something will make that mod compatible?

I basically went through every mod and deleted the magazine from every preset, but after putting the mod at the very end of load order I still got the error, is there something else I may have to do to get it to work? or is it something to do with custom ammo I may have to adjust?

What exact error (message) do you get?

P.S. what I mean with removing parts from the presets is that e.g. if you found out a certain weapon preset causes trouble, instead of completely removing that preset simply remove the part that is triggering the error.

I took silencers and magazines as examples because if they don't exist, the weapon is still usable and doesn't appear "red" during raid.

In terms of custom ammo. Ahead of v1.0.5 the error for custom ammo was triggered since SPT creates an ammo filled magazine / weapon with ammo filled magazine only with the info it retrieves from the file "staticAmmo.json" (default SPT installation). To fix that, v1.0.5 introduced the feature to create a completely new staticAmmo data file, based on default ammo types but also custom ammo types that come with mods.

For sure, if the custom ammo type of a mod initially isn't properly set up you will still get an error, yes.

I think it was just KMC so i moved it below, not entirely sure how to figure out what part would be causing issue but removing mags from everything honestly fixed 99% of my issues, I started to get an encyclopedia issue but that was an unrelated thing to another mod and I never touched it because it was bundled but yeah

TL;DR error was not an issue with your mod, removed magazines actually managed to work did the wrong formula but got the right answer

USB key (i.e. Secure Flash Drive) or USB adapter? USB keys should generally spawn in Drawers, Jackets, Safes, Duffle bags, Dead Scavs, Plastic Suitcases, Ground caches and Burried Barrel Caches - in Shturman Stash acccording to the set value limit (Secure Flash Drive is 40152 roubles).

What specific keys are you missing? Keys - except Shturman Stash Key, Machinery Key aside its jacket in dorms, Unknown Key and Hideout Backup key - aren't blacklisted.

Not the adapter. this USB for the Peacekeeper mission. I have never found one...

I would have to look again for the key. I could have made a mistake.