Jump to content

About loot for some bots

Pending 1.4.1

maxalt
maxalt

Posted

Hello, and thank you always for providing such a fun server!

Previously, I received help setting up zombie loot so that they only drop skulls using CustomLoot — and it's working great!

However, I'm wondering if it's possible to add extra items to some specific bots in addition to the skulls.

For example, at the Water Treatment Plant, I have 30 zombies spawning, and one of them is a stronger zombie that I've configured through Kits to carry an L96.
I'd like this one to also carry a skull and a bluedogtag. (Both items can be sold for RP at the Shop.)

I tried giving items through Kits to its inventory, but it seems like the zombie only drops the skull — everything else disappears.

Is there any workaround or method to make this work?

  • Administrator
Steenamaroo

Posted

Hi,

If it's just single, or a few, specific items like that it's probably easiest to just add them to a customloot table for that npc profile.

Just duplicate and rename your current customloot table - the one that gives skulls,
then in /config/CustomLoot.json, apply that new name to whatever profile you're working on  as "lootTable".
While you're there, make sure minItems and maxItems are set to 2

Now open and edit that new loot table and set "Resources" category probability to 1, then search to find "bluedogtags" entry and set its probability to 1.


Alternatively you can just set all probabilities to zero and just use the AlwaysSpawnList, at the top of your /data/Customloot... loot table file.
Like this.

  "AlwaysSpawnList": [
      "bluedogtags",
      "skull.human"
    ],

 

maxalt

Posted

1時間前、Steenamarooは言った:

こんにちは、

そのような単一の、またはいくつかの特定のアイテムである場合、おそらくそのnpcプロファイルのカスタムルートテーブルに追加するのが最も簡単です。

現在のカスタムルートテーブルを複製して名前を変更するだけです - 頭蓋骨を与えるもの、
次に、/config/CustomLoot.jsonで、その新しい名前を「lootTable」として作業しているプロファイルに適用します。
そこにいる間、minItemsとmaxItemsが2に設定されていることを確認してください

次に、新しい戦利品テーブルを開いて編集し、「リソース」カテゴリの確率を1に設定し、検索して「bluedogtags」エントリを見つけ、その確率を1に設定します。


または、すべての確率をゼロに設定し、/data/Customloot...ルートテーブルファイルの上部にあるAlwaysSpawnListを使用することもできます。
このように。

"AlwaysSpawnList": [「bluedogtags」、「skull.human」]、

 

Thank you very much.

When you say to duplicate a custom loot table, do you mean the sk.json file I previously created that only drops skulls?

Should I simply copy that file and rename it?

 

By the way, I’m currently using the /botrespawn command in-game to configure settings.

I’ve set it so that for each monument or biome, I spawn 1 strong zombie using the “Edit Kits” section with Zombie29 and Hunter1.

  • Administrator
Steenamaroo

Posted (edited)

"Should I simply copy that file and rename it?"
Yes, that's right.

I mean, you can just open the /config/CustomLoot/json and enter a new (unique) loottable name for your WaterTreatment guys,
then reload the plugin and it will create a new blank table (just like previous instructions).
From there you'd set up your skull and your dog tags.

The duplicate approach just saves you a few steps, since you already have a loottable giving skulls,
and you want a new one to give skulls plus other items.

The easiest option is probably the one I described using the AlwaysSpawnList inside your customloot loot table json.

 

 

The approaches I've described are all within, and handled by CustomLoot - Nothing to do with BotReSpawn or Kits.

You could add the items you want to the npc profile's kit, if you wanted,
but then you'd have to set custom loot's "Clear Container First" to false for that profiles CustomLoot table,
and then set Allow_Rust_Loot_Percent to zero for that profile in BotReSpawn.

That's more complicated, and your'e already using CustomLoot so you might as well handle it there. 👍

 

 

Edited by Steenamaroo
maxalt

Posted

Am I editing it correctly like this?

IMG_6416.png

  • Administrator
Steenamaroo

Posted (edited)

I doubt commas are a good idea in loottable / file names.
If you're trying to apply two loot tables there, that's not a thing.

There's a few different approaches but the simplest would be to give the WaterTreatment BotReSpawn entry, in /config/CustomLoot.json, a new loot table name,
then reload CustomLoot so it creates that file,
then edit that file (in /data/CustomLoot) with the AlwaysSpawnList that as I pasted above.
That takes probability out of the equation and keeps things simple.

 If you need to refer back to previous support where I outlined creating and setting a loot table, do that. 👍

That should get you your skull and tags for that particular BotReSpawn profile.

Edited by Steenamaroo
maxalt

Posted

Sorry for the trouble.

To be honest, I’m still not entirely sure how BotReSpawn and CustomLoot work.

Would it be okay if I summarize what I’m trying to do?

 

What I want to achieve:

 

I have strong zombies (Hunter) spawning only at large monuments, and I want only the Hunters to carry one skull and one bluedogtag.

In other areas such as biomes, harbors, and rad towns, I only want regular zombies, and they should drop only skulls.

 

 

Regarding the method you mentioned—does it go like this?

 

In config/CustomLoot.json, I assign a LootTable (e.g. “Hunter”) to monuments like Water Treatment or Airfield, then reload CustomLoot.

In data/CustomLoot/Hunter.json, I set the chance for skull.human to 1, and also set bluedogtags to 1.

 

 

Is this correct?

 

However, there’s one thing I still don’t understand.

I want regular zombies to drop only skulls, and Hunters to drop skulls and bluedogtags.

But if I assign the “Hunter” LootTable to a monument, wouldn’t the regular zombies there also drop bluedogtags?

Sorry to bother you again, and thank you for your help.

  • Administrator
Steenamaroo

Posted (edited)

"To be honest, I’m still not entirely sure how BotReSpawn and CustomLoot work."

You can basically forget about BotReSpawn. No changes need to be made there.

CustomLoot can 'see' barrels, crates, and corpses.
It's written to recognise what profile any given BotReSpawn corpse is from.

All the work for managing loot is done in CustomLoot's files.

 

 

 

Regarding the method you mentioned—does it go like this?

In config/CustomLoot.json, I assign a LootTable (e.g. “Hunter”) to monuments like Water Treatment or Airfield, then reload CustomLoot.

In data/CustomLoot/Hunter.json, I set the chance for skull.human to 1, and also set bluedogtags to 1.

Is this correct?

Yes, that sounds good.
If you're using probabilities make sure the "Resources" category is set to probability 1 also, and that the profile (in config file)
is set for min/max items = 2.

 

 

However, there’s one thing I still don’t understand.

I want regular zombies to drop only skulls, and Hunters to drop skulls and bluedogtags.

Just make sure that the BotReSpawn profiles for regular zombies are using your original CustomLoot loot table - The one with skulls only.


Really, in summary, all you're doing is making a new loot table with extra stuff and assigning it to select BotReSpawn profiles.
The ones which should remain skull-only shouldn't be changed. 👍

Edited by Steenamaroo
maxalt

Posted

I tried it, but the regular zombies at that monument are also dropping dog tags.

I set the LootTable of the Water Treatment Plant to "hunter" → reloaded → adjusted /data/CustomLoot/hunter.json to drop both Blue Dog Tags and skulls → reloaded again.
Then, when I defeat the Hunter (strong zombie) on site, it drops the Dog Tag and Skull as intended — but the regular zombies are dropping them too.

What I want is for the Hunter to be a tough enemy for players, and as a reward for defeating it, they can sell the Dog Tag.
So I want only the Hunter to drop the Dog Tag — not the regular zombies.

  • Administrator
Steenamaroo

Posted (edited)

Who are the regular zombies?
They should be a different BotReSpawn profile to your hunters and, if they are, then just make sure their profile doesn't have the hunter loot table in CustomLoot config file.

I mean, you already had a customloot loot table for skulls only - Your other npcs (not hunters) should be using that.

Edited by Steenamaroo
maxalt

Posted

19 minutes ago, Steenamaroo said:

通常のゾンビとは誰ですか?
彼らはハンターとは異なるBotReSpawnプロファイルを持っているはずです。もしそうなら、CustomLoot設定ファイルでそのプロファイルにハンターの戦利品テーブルが含まれていないことを確認してください。

つまり、頭蓋骨専用のカスタム ルート ルート テーブルがすでにあるので、他の NPC (ハンターではない) はそれを使用する必要があります。

I'm really sorry for my lack of understanding.
Could you please take a look at the file?
The sk file is the one I want to assign to the regular zombies.

By "regular zombies", I mean the ones configured from /botrespawn under "Default profiles" for each monument.
During the daytime, 30 NPCs are spawned — 29 are set as "zombie" and 1 as "hunter" via "Edit Kits".

CustomLoot.json sk.json

  • Like 1
  • Administrator
Steenamaroo

Posted

"During the daytime, 30 NPCs are spawned — 29 are set as "zombie" and 1 as "hunter" via "Edit Kits"."

This is your problem. ^

Your hunters and zombies would need to be two separate profiles within BotReSpawn - Not one.



I recommend using BotReSpawn default Water Treatment profile for your 29 zombies,
then create a custom BotReSpawn profile (chat command /botrespawn add *name*) to create a new profile for your hunter.
Before you do anything else to it, set Other/ParentMonument to Water Treatment 0.
That's in the BotReSpawn UI.

That way your new custom hunter profile will always be tied to the Water Treatment location and profile.



Once that's all done you can go into CustomLoot config file and assign Water Treatment 0 one loot table, and your new hunter profile a different loot table.

maxalt

Posted

Sorry for the late reply! I’ll give it a try today.

Where is the Hunter profile created/generated?

maxalt

Posted

I'm really, really sorry.
I honestly don't understand.
Please take a look at my current settings.

bandicam 2025-07-04 09-58-12-279.jpg

bandicam 2025-07-04 09-58-17-580.jpg

bandicam 2025-07-04 09-58-21-824.jpg

bandicam 2025-07-04 09-58-24-939.jpg

bandicam 2025-07-04 09-58-27-780.jpg

bandicam 2025-07-04 09-59-36-100.jpg

bandicam 2025-07-04 09-59-52-382.jpg

bandicam 2025-07-04 10-00-47-859.jpg

bandicam 2025-07-04 10-07-02-338.jpg

bandicam 2025-07-04 10-07-45-969.jpg

  • Administrator
Steenamaroo

Posted

Looks like you made a new profile for your hunters and set up Parent_Monument as Airfield.

That's great.
That now means your airfield zombies and hunters are under separate profiles,
and CustomLoot will be able to see that.

So now, using what you know from before, just set up the CustomLoot profiles for BotReSpawn-hunter and BotReSpawn-Airfield-0 to use the correct loottables.
Airfield should use the skull-only loot table, and hunter should use the skull and tags loot table.

 

maxalt

Posted

6 hours ago, maxalt said:

I'm really, really sorry.
I honestly don't understand.
Please take a look at my current settings.

bandicam 2025-07-04 09-58-12-279.jpg

bandicam 2025-07-04 09-58-17-580.jpg

bandicam 2025-07-04 09-58-21-824.jpg

bandicam 2025-07-04 09-58-24-939.jpg

bandicam 2025-07-04 09-58-27-780.jpg

bandicam 2025-07-04 09-59-36-100.jpg

bandicam 2025-07-04 09-59-52-382.jpg

bandicam 2025-07-04 10-00-47-859.jpg

bandicam 2025-07-04 10-07-02-338.jpg

bandicam 2025-07-04 10-07-45-969.jpg

I finally understood!

Does this look correct?

The file /data/CustomLoot/hunter.json does exist!

IMG_6445.png

  • Administrator
Steenamaroo

Posted

It will exist if you reload CustomLoot first.

maxalt

Posted

7 hours ago, Steenamaroo said:

It will exist if you reload CustomLoot first.

You truly are a wonderful creator.

I now completely understand the integration between CustomLoot and BotReSpawn.

Thank you so much!

  • Love 1
  • Administrator
Steenamaroo

Posted

My pleasure, and thank you for the kind words.
I'm glad you got it up and running.

CustomLoot is not intuitive - I know that.
I tried to make BotReSpawn as simple, convenient, and easy to understand as possible.
CustomLoot? not so much... 😂

If you hit any problems, just reply here and let me know. 👍

1.8m

Downloads

Total number of downloads.

8.5k

Customers

Total customers served.

127.8k

Files Sold

Total number of files sold.

2.7m

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.