AllTheLoot - 3.9+ 1.0.8

It appears that "Decrypted Flash Drives" and "Document's with Decrypted Data" made it past the blacklist.

Yeah those two drives and the tiny intelligence folders are in an awkward place for 3.9. While the quests you need those items for are no longer in the game on Live tarkov, the build of the game 3.9 is built upon still has those quests as active ones you can actually still do in SPT. Come 3.10 (or if a 3.9 build is pushed with a client update) they will need to be blacklisted then.

would setting

    "questItems": false,

stop them spawning?

No. if you want to remove those three items (and thus render the quest they're associated with undoable) you'd need to add their IDs to the global blacklist.

"660bbc98c38b837877075e4a",

"660bbc47c38b837877075e47",

"660bc341c38b837877075e4c"

Ah because you said BSG didn't make them proper quest items right? Tbf probs not the end of the world to keep them blacklisted 'til the quest is unlocked. Thanks

This is something that only Linux users get. I still need to publish an update with the fix (among a few others) but for now change these lines:

AllTheLoot_Main.ts, Lines 8-14 to:

import config from "../../config/config.json";
import config_Blacklisting from "../../config/config_Blacklisting_ID.json";
import config_Containers from "../../config/config_Containers_ID.json";
import config_FavoriteItems from "../../config/config_FavoriteItems_ID.json";
import config_QuestItems from "../../config/config_QuestItems_ID.json";
import config_CategorySpawnrates from "../../config/config_CategorySpawnrates.json";
import config_SelectedItems from "../../config/config_SelectedItems_ID.json";

Basically replacing the upper case /Config/ that exists in the path with a lower case one. VSC doesn't recognize this as a problem since only Linux users have this issue. I don't have easy access to any linux setups so if it doesn't work please let me know.

Sorry for the late reply. I forgot to come say thanks but yes, FUCKING CAPITALISATION got me some grey hair. Thanks man!

Quick fix is actually to just capitalise the config folder in /mods/zzBlackMamba-AllTheLoot.

I love a stupid pedantic capital vs non capital issue.

114 key can still spawn in the jacket in the back of the car by the military checkpoint on Customs--it's just a relatively uncommon spawn. In my experience going for it on live, I saw it somewhere on the order of 1:25 to 1:50 runs earlier this wipe, and that's about what it's been every time I've actually been playing live and checking for it consistently.

Changing the 114 key's spawn chances in that jacket would probably be pretty easy, since it's a specific container (I'm pretty sure it's "59387ac686f77401442ddd61"), and I don't think it's used anywhere else in the game.

Short notice on the Dorms 114 key.

The container works like this. It gets assigned items from category "MEDICATION_MEDKITS" and "MEDICATION_PILLS" + the Dorms Key 114 (as far as I remember everything summed up to 11 items). The blacklist file by default removes 3 items, so 8 items left.

To make the Dorms Key 114 spawn with a somehow "controlled" rate, all items in the container have been set the same relative probability (in that case 1), which results in a final spawn chance of ((1+1+1+1+1+1+1+1)/8) / 8, i.e. 12,5%.

If you want to increase the spawn chance of the Dorms 114 key even more, the easiest would be to add some more blacklisted medkits in the file config_Blacklisting_ID.json

Assuming you want the key with a spawn chance of e.g. 20%, you need to remove 3 additional medical items.

Shortly on "locked factory room". The problem is, this jacket isn't configured by SPT as a dedicated container (like Dorms 114, Dorms 204 and machinery key jacket). Like such it can only be treated as a normal jacket (and having only the general "jacket-container-items" assigned to it).

Thanks Elwood! - awesome info . The factory room key I think used to actually spawn on the floor under that jacket - so that floor spot might be a specific spawn point?

Yeah, it's probably a specific spawn point, though of no use for AllTheLoot.

Anything outside of a container - e.g. like a key laying on the ground - is handled by SPT internally as LooseLoot and like such not being manipulated by AllTheLoot.

Maybe you find a loose loot mod to increase / make available that spawn again. Can't name a good mod right now because relooted, what I normally used, seems to be outdated.

config_CategorySpawnrates.json

These two lines:

"rate_KEYS_ELECTRONICKEYS": 0.15,
"rate_KEYS_MECHANICALKEYS": 0.85,

The lower the number the less likely

Oh nice, it's cool how much you can tweak everything in that file. Thanks for updating this mod!

Maybe, but that can also change the internal size of jackets and drawers, so it's still useful if you're using it for that.

Thanks! I had no idea about the linux issue. This mod definitely needs a lot of cleanup and reformatting that I'm not yet going to bother doing in case the original author decides to return. If, in the future, it appears that I become the primary caretaker of this mod I'll put in that effort to clean it all up.

I will at least address this and any other issues that prevent the mod from functioning until then.

Hey Jewels. As already mentioned via DM, I would be super happy if you take over the ownership of that mod. My primary goal back then was to create a good loot mod, which you can tweak in any thinkable way (for sure, as much as it's possible because of the relative spawn principle of SPT). Currently I'm not so much anymore into SPT because of other things.

I'm excited to see how you clean the mod even more. From 1.0.5 to 1.0.6 I (as a total noob in typescript) tried my very best, to get most of the initial mess cleaned up

P.S. yeah, back then I wasn't aware of the proper spelling necessity too - actually I didn't think anyone plays SPT in a Linux environment

Woops! Cleared it out to test something and forgot to repopulate it. I'll be sure to fix that and push an update. You can just use the old one from the original mod in the meantime.

Between the two it shouldn't matter but both should be at the very bottom. ATL handles loot inside containers while LoL handles loot that spawns in the world itself. There's no crossover.

If i use SVM to modify the loot multiplier per map will it conflict with this mod ? or just load this mod after? or disable that module of SVM?

@S13NDR_M4N It shouldn't matter. I personally don't use SVM so I can't say for sure. I would load this after SVM just to be safe.

an other question, in config I set this:

  "LooseLootMultiplier": {
    "bigmap": 0.9,
    "factory4_day": 1.10,
    "factory4_night": 1.10,
    "woods": 1.10,
    "interchange": 1.10,
    "laboratory": 2,
    "rezervbase": 1.5,
    "shoreline": 1.15,
    "tarkovstreets": 1.30,
    "lighthouse": 1.30,
    "sandbox": 1.50,
    "sandbox_high": 1.50
  },

  "StaticLootMultiplier": {
    "bigmap": 0.9,
    "factory4_day": 1.0,
    "factory4_night": 1.0,
    "interchange": 1.10,
    "laboratory": 2,
    "rezervbase": 1.5,
    "shoreline": 1.15,
    "woods": 1.10,
    "tarkovstreets": 1.30,
    "lighthouse": 1.30,
    "sandbox": 1.5,
    "sandbox_high": 1.5
  },

Does it mean, default loot spawn will be multiply by this number ?
Can I change the "loot quality/rarity" per map ?

Those numbers dictate how many pieces of loot the game should generate on a given map before stopping. This mods settings affect the spawn rate of individual items within that cap. So in short, yes, spawns from this mod are affected by those numbers.