It looks like it’s trying to do stuff with the 3.9.0 items that don’t exist in 3.8.3. I prevent them from trying to spawn, but if you iterate through every item on the loot table you’ll still find them (and then stuff will break when you try to do things with them because they don’t exist in the item database).

So yes, it’s incompatible, sorry.

I don’t think Keys In Loot will do anything if you have static loot enabled in Loot Update.

In current/older SPT versions, static loot uses a global table. Starting in 3.9.0, it will be different probabilities per map. Since I’m using 3.9.0 loot tables, I have to update the functions to use per-map tables.

KIL modifies the global static loot tables, which don’t get used, so its changes won’t do anything.

SVM just changes “looseLootMultiplier” and “staticLootMultiplier” config values, which are applied on top of the loot tables. I don’t touch any of that, so how it interacts should be the same way it interacts with base SPT loot tables.

Oh interesting. I do have a fairly heavily edited KIL config that basically strips it back, essentially functioning like vanilla but with added keys. Perhaps I’m mistaking it for working when it could be just that the loot changes are closer to what my version of KIL is doing. I guess I’ll keep an eye out for the yellow 1 use quest keys in loot pools as they are definitely a function of KIL. Will keep you posted. Thanks for the reply.

The only parts of KIL that will function are the prices and jacket size. If you’re familiar with basic coding, you can see what KIL does here. It gets references to the jacket, duffle bag, and dead scav containers from the global static loot table. It directly modifies the loot tables for those containers in the global static loot table.

My static loot changes don’t touch the global static loot table at all. Instead, I make the static loot generator use per-map tables that I load from json. So it doesn’t matter what KIL does with the global static loot tables because they aren’t used by loot generation.

I’m unfamiliar with coding but I understand what you’re saying, thanks for taking the time to clarify this.

I’ve removed KIL from my load order as I wasn’t using the only functioning part of that mod anyway. In your opinion would it be feasible to convert KIL to per-map tables or is there perhaps an even simpler way to add keys to the loot tables without the other changes to loot in that mod? I play SPT with no flea market and it’s been a nice way to get certain keys through loot and fence, although I have noticed keys are more common with your loot update mod on it’s own so perhaps it’s not necessary now.

Previously i was using the 0.2.0 version and updated to 1.0.2 today. Ive checked both marked rooms in Chek13 & Abandoned Factory in 20 raids and only found 1 labs access keycard in Abandoned Factory. Here is my loot order:

{ “order”: [ “aaa_Isaac-LootUpdate”, “DanW-SPTQuestingBots”, “Skwizzy-NoDiscardLimit”, “ServerValueModifier”, “DrakiaXYZ-LiveFleaPrices”, “SPT-Realism”, “zSolarint-SAIN-ServerMod”, “SWAG”, “fika-server”, “Isaac-InertiaUpdate”, “odt-iteminfo-4.0.3”, “Square-LiveBitcoinPrices-1.1.0” ] } Is there something wrong with my loot order? I didnt edit anything loot related in SVM.

Nothing changed in the loot files between 0.2.0 and 1.0.2. The only change for loose loot that happened was fixing a bug with the Giving Tree which made it spawn keycards 40%(* 2) every raid. That does not affect any spawns other than the Giving Tree.

I’ll be your guinea pig and find out. Worst case as far as I can understand prior to trying it, is that the loose loot from this will be present but containers would be pulling from ATL’s lists. Will update in an hour or two with the verdict.

Update: Loot Update runs as it should, confirms generation of various containers + contents. It’ll take a bit of looting to see how/if ATL influences containers but it at the very least doesn’t break everything.

To help with testing, if you don’t see [Loot Update] Generating static containers. in your server window when generating loot on map load, it means that another mod is overriding Loot Update’s static loot patch. If that happens, then Loot Update doesn’t affect loot inside containers at all.

(Or it means you don’t have it enabled in the config, of course)

I think alltheloot should work fine if you disable the static loot in the loot update config…

I don’t know what to tell you, there’s not even an exe or dll or anything. Here’s the VirusTotal link. You can see everything the mod does in plain text code. You can google how to make an exception so Windows (or whatever other AV) doesn’t eat it.

OK I will check it out and thanks for your job~