Steenamaroo
-
Posts
3,405 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
Probably should have told you what those mean... Descriptions from the upcoming UI update... Short_Roam_Range. When passively roaming, npcs choose a spot on the ground to walk to, walk to it, then choose another...and repeat. If this setting is true npcs will choose spots much closer to their current position than normal. This can be useful where npcs are in areas with a narrow river, for example, to prevent them trying to roam to the other side of it. Assist Sense Range If Global Setting 'NPCs_Assist_NPCs' is set to true then npcs can assist nearby npcs who have a target. Use this setting to adjust how far away an npc can sense other aggravated npcs. -
Hi @Rezanow, None of the profile configurable values is detailed in the description. Profile values. Each profile value and description is not listed here, but all (apart from text strings) are now configurable via UI, and have sensible default values. Most should be self explanatory, although I do intend to add descriptions/notes in the UI itself in the near future. If any specific setting/value is unclear, please just ask in CF discord, my discord, or the support section here. As it happens I did the part in bold last week so the next public release will have clickable labels and full descriptions for every profile option.
-
Hi @nivierheim I think that should be CompoundScientist. -
Yes, that should be resolved in the next version too, unless the name really is ridiculously long. I put fewer kits on the page to allow more space, and wrote in pagination so you can browse a limitless number of kits.
-
There's a global config option `NPCs_Assist_NPCs` which you can turn off, if you prefer, and also a per-profile option `Assist_Sense_Range` which you can adjust to taste. The next update of BotReSpawn will have a per-profile option `Friendly_Fire_Safe` which will prevent damage when npc's accidentally hit each other.
-
Hi, They only throw grenades if you have them placed in the kit, and they should only attack each other if you've got Ignore_Factions set to true, or set up factions such that certain profiles are aggressive to each other.
-
@RobertLeal- As it happens I added both of those last week. You're welcome to test it out before I update properly. Recommend using the `/perms data` menu to save a local back for groups + perms, just as a precaution. PermissionsManager.cs- 195 comments
-
- 1
-
-
- #permissions
- #admin
- (and 7 more)
-
No trouble at all. Thanks for coming back with more info!
-
Can't open the admin UI shown in the screenshots?
Steenamaroo replied to Bear Grills's Support Request in Support
No worries. -
Can't open the admin UI shown in the screenshots?
Steenamaroo replied to Bear Grills's Support Request in Support
Hi, The Admin button should only be visible to you if you have the permission "playerranks.admin". -
Hi, Just checked and they're working fine here. You know beancans have a chance of not exploding? Some are duds.
-
Ok, thanks for letting me know. I'll take a look at that soon!
-
@spencer cleary- I talked to Raul. Looks like it's Carbon specific but he's patched so it won't be an issue in future versions. Thanks for reporting and thanks @Raul-Sorin Sorbanfor addressing it.
-
Could be @Raul-Sorin Sorban Fix your shit.
-
Hi, Someone else reported this but I've had no issue before, or after, wipe. Are you on some non-standard build of Rust Server?
-
Hi, Most likely nav_wait is false. When it's false it means the server doesn't wait for completion of navmesh generation before starting up, so when the server goes live and BotReSpawn starts up, there's no navmesh for the npcs to spawn on. Type nav_wait into server console and if the response if False, do nav_wait True server.writecfg
-
No worries. Looks like these changes aren't necessary for current staging (downloaded yesterday) so if you update your server and shit doesn't work, go back to vanilla BotReSpawn.
-
Hey mate. I can sort this no problem. I'll send you an update later today. Thanks for pointing it out.
-
I don't think many people are doing custom SpawnGroups. If that's all they've changed it'll probably just be me. Probably Monument Addons too...
-
Ok. Looks like they've changed a few things from protected to public. Change protected override BaseSpawnPoint GetSpawnPoint... to public override BaseSpawnPoint GetSpawnPoint... and protected override void Spawn to public override void Spawn
-
@Butler NM. Yeah. Looks like you're on staging. If you edit the plugin .cs and change protected override void PostSpawnProcess(BaseEntity entity, BaseSpawnPoint spawnPoint) to public override void PostSpawnProcess(BaseEntity entity, BaseSpawnPoint spawnPoint) Hopefully it should work fine. I can do that for you and send, if you need.
-
Hi, No, I'm not sure what's happened there. Are you on a staging server?
-
Confirmed - The next update, due soon, fixes this issue. Thanks for testing and confirming @Baron Von Finchus
-
Ok, thanks for the info. There must be some combination of settings I didn't try that allows this to happen, although there were a few issues relating to event spawns and parachutes, as I've recently made changes allowing events to spawn npcs underground, when the event occurs underground, so it's entirely possible I've fixed this, even though I couldn't replicate it. I'll get you on discord and send you the pre-release copy I have here, if you're up for that.
-
Hey, Sorry man, I don't think I'm following. That mockup is identical to what PermissionsManager does. Vanilla screenshot attached.
- 195 comments
-
- 1
-
-
- #permissions
- #admin
- (and 7 more)
