Jump to content

BotReSpawn 1.2.9

$40.00
   (39 reviews)

10 Screenshots

  • 333.8k
  • 10.9k
  • 320.89 kB

Recommended Comments



In the prior versions, the bots that I equipped with a kit always had individual names. That is no longer the case and now they are all just called Scientist. Did i missed something in the configuration?

  • Sad 1
Link to comment
Share on other sites
38 minutes ago, Dr.D.Bug said:

In the prior versions, the bots that I equipped with a kit always had individual names. That is no longer the case and now they are all just called Scientist. Did i missed something in the configuration?

Check your data folders, for the botprofiles you had created. They may have been reset or wiped when you updated.

oxide/data/BotReSpawn/default-Defaultprofiles.json  (or whatever profile.json you are using)
each profile within the config should have something like this "BotNamePrefix": "Botnamehere", for the custom name to appear

*Edit*  sorry it could also be your TemplateData.json too  where each monument or biome profile can also assign a "BotNamePrefix": "botnamehere" which should be just above the listed kits you have chosen.

Edited by Malkizid
Link to comment
Share on other sites
1 hour ago, Malkizid said:

Check your data folders, for the botprofiles you had created. They may have been reset or wiped when you updated.

oxide/data/BotReSpawn/default-Defaultprofiles.json  (or whatever profile.json you are using)
each profile within the config should have something like this "BotNamePrefix": "Botnamehere", for the custom name to appear

*Edit*  sorry it could also be your TemplateData.json too  where each monument or biome profile can also assign a "BotNamePrefix": "botnamehere" which should be just above the listed kits you have chosen.

Me too, after the update all "BotNamePrefix" doesn't work

  • Like 1
Link to comment
Share on other sites
15 minutes ago, Jacob Rain said:

Me too, after the update all "BotNamePrefix" doesn't work

custom Botnames are working on my test server with the updated version. Are your data folders all intact and set up? Perhaps Botrespawn is laoding the wrong ones?  Works on my Monument profiles, default profiles and Customprofiles (which I use for Bosses)

also make sure that in the config BotReSpawn.json that the   "DataPrefix": "default",   matches the prefix of your data files where the names etc. are stored.
I dont recommend copying my lazy and messy naming system, but that doesnt matter as long as this is correct.

botrspwn.jpg

Edited by Malkizid
Link to comment
Share on other sites
49 minutes ago, Malkizid said:

custom Botnames are working on my test server with the updated version. Are your data folders all intact and set up? Perhaps Botrespawn is laoding the wrong ones?  Works on my Monument profiles, default profiles and Customprofiles (which I use for Bosses)

also make sure that in the config BotReSpawn.json that the   "DataPrefix": "default",   matches the prefix of your data files where the names etc. are stored.
I dont recommend copying my lazy and messy naming system, but that doesnt matter as long as this is correct.

botrspwn.jpg

I'm pretty sure there's nothing wrong with my configuration. I've also tried the default settings and it didn't work. Just like vanilla display names, I'm not sure if it's related to the recent update of vanilla display NPC names. I'm using Carbon 2.0.139.

 

messageImage_1725728471535.jpg

messageImage_1725728578665.jpg

messageImage_1725728698925.jpg

  • Like 2
Link to comment
Share on other sites

@Jacob Rain Yes, I see your naming system is set up correctly, I had to ask though.
Damn, there does seem to be some sort of issue there because of FacePunch recent update.

I'm running oxide btw but I dont think carbon or oxide is the issue.
For now we will just have to hang on and see if there will be a patch.

@Steenamaroo have you noticed these issues, would you be able to implement a hotfix sometime soon?

Edited by Malkizid
  • Like 2
Link to comment
Share on other sites
  • Administrator

Sorry folks, I didn't get notifications for this until @Malkizid @ pinged me.
Thanks for that.

There is an issue with names introduced in the wipe update but I have since sorted it out and will be pushing a public update soon.

  • Like 2
  • Love 2
Link to comment
Share on other sites
3 minutes ago, Steenamaroo said:

Sorry folks, I didn't get notifications for this until @Malkizid @ pinged me.
Thanks for that.

There is an issue with names introduced in the wipe update but I have since sorted it out and will be pushing a public update soon.

Thanks a lot for your hasty response, always appreciate your support and work - cheers!
Looking forwards to the release when its ready

  • Like 3
Link to comment
Share on other sites

New issue.  I have all my NPC's  set up with NPCKits and my A.I. Bots with BotReSpawn, showing a "BotNames" to be announced with Deathnotes and Simple Kill Feed.  Stopped working.  When I go to the Bot, in Vanish (Hitting Reload) I can see  their name is clearly Scientist.  Even though my configs still read the same.  Not sure if the Facepunch update has anything to do with this. 

Can you check this out?  Putting this in NPCKits too, so anyone that has that plugin, but not this one can see the issue is being addressed. 

Thank you,

Papa Bear

 "APC_Kill": {
      "type": 3,
      "Spawn": {
        "AutoSpawn": true,
        "Radius": 20,
        "BotNames": [
          "Bradley ParaTrooper"
        ],
        "BotNamePrefix": "a",

Link to comment
Share on other sites

Have you read the comments before and installed the newest Version uploaded today? We all had problems with the default names "Scientist". 

  • Like 3
Link to comment
Share on other sites
  • Administrator

Confirmed fix in both BotReSpawn and NPCKits.
Papa Bear DMd me shortly after this.

Thanks again, all! 👍

  • Like 1
Link to comment
Share on other sites

Hi there, BotReSpawn NPC's cause the new Rust  TravellingVendor  (IceCream van) to shit iteself  when they encounter eachother on the roads.

a sample from console repeeated spam:
KeyNotFoundException: The given key 'Hunter Camelia[2611237]' was not present in the dictionary.

Perhaps it is also related to TruePVE, not sure. Happens with some other npc plugins we use such as ZombieHorde too

The vendor cant decide to drive past them or not and if they are hostile it will kill them but eventually bugs out with console spam.
I forgot to save my logs so I'll edit this post with more solid info as soon as I can.

Edited by Malkizid
Link to comment
Share on other sites
  • Administrator

Unfortunately it's not just BotReSpawn npcs.
I've seen the message with other npcs and, even sometimes, with real players.

I wrote a small patch plugin to make the vendor flat out ignore any hostile npcs. I'll send it to you.

  • Love 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Like 12
  • Sad 5
  • Haha 1
  • Love 25

User Feedback

1.3m

Downloads

Total number of downloads.

6.5k

Customers

Total customers served.

95.8k

Files Sold

Total number of files sold.

1.9m

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.