Steenamaroo
-
Posts
3,825 -
Joined
-
Last visited
-
Days Won
212
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Everything posted by Steenamaroo
-
It seems it has stopped working since this month's update.
Steenamaroo replied to hid333's Support Report in Support
Updated. Should be good now but please don't hesitate to let me know if you see any issues. Thanks again. -
Updated. Thanks again.
-
It seems it has stopped working since this month's update.
Steenamaroo replied to hid333's Support Report in Support
Ok, thank you. I'll get a look at this soon and hopefully have an update for you. FP did make changes relating to file storage so, hopefully, it'll be simple enough. -
Thanks for letting me know. There's a description in the UI but, incase you don't know, suicide timer doesn't apply to normal default+custom profiles. Those maintain the population you asked for in UI, but any npcs spawned by event, outside of managed populations, like 'toplayer' command, or airdrop, locked crates, apc spawn etc, are subject to suicide timer for the reasons above. -
That's your suicide timer being set to zero. It exists because if there are regular airdrops and no one killing the npcs, the numbers would just constantly increase over time. Set it to something higher, a maximum lifetime for airdrop npcs, and that should solve it.
-
It seems it has stopped working since this month's update.
Steenamaroo replied to hid333's Support Report in Support
Hi, Have you updated? I released a public update ahead of wipe. -
Thanks Mal. Should be good now.
-
Hey, Thanks for reporting. Yeah, looks like I didn't apply the check in all places where KDR is calculated. I'll update for this soon.
-
Hi, I'm sure it compiles. Sounds like maybe your file's been modified or something. Try deleting your .cs then redownloading from here.
-
Should be updating today to address that. Thanks @ZA_Machete
-
Hi, I have no idea. NPCKits, at its core, just allows you to put Kits on to npc automatically. I'm not familiar with the Custom Clothing plugin, and how it works, but it doesn't explicitly mention Kits.cs or NPCKits.cs. Best thing would be to talk to the author and find out how it's meant to work.
-
Hi, Thank you. This is resolved and there'll be an update some time before wipe.
-
Hi, I found the cause of this and fixed it recently. I haven't publicly updated since then, though, so the fix will be in the next update, which should be before wipe. I think if you just reload PermissionsManager, for now, it should work around it.- 242 comments
-
- 1
-
-
- #permissions
- #admin
- (and 7 more)
-
Not a problem. Thanks for letting me know.
-
Are you on 1.6.0? I patched for that last wipe and, as far as I know, it solved the problem. Not aware of any issues. Can you be more specific, please?
-
Update released. Thanks for letting me know about it.
-
oh, boo. Must need using Rust.Ai.Gen2; or using Rust.Ai; I'll get on it in the morning. Thanks!
-
Hi, Thanks for reporting. I won't be on an up to date server until tomorrow but I can get it sorted and update then. If you're comfortable editing, I'm pretty sure changing NavMesh.SamplePosition.... to RustNavMeshHelpers.SamplePosition.... should sort it out. Just that one word, and there's only one instance of it.
-
Hi, No, it's just governed by the global priority system.- 465 comments
-
- 1
-
-
- #statistics
- #leaderboard
- (and 12 more)
-
Hi, Yes, no problem. I'll do that soon. Thanks for the info.
-
Hi, There's nothing automatic built in, no, but there are console commands for BotReSpawn enable/disable "ProfileName" Running disable immediately removes existing npcs, so any plugin managing events could offer a config field for profile names, then toggle them off/back on as needed.
-
Hi, If you are admin (auth level 2) on the server you won't need the permission, so you should be able to just use the /perms chat command and get in to the UI, although if you're seeing "permissionsmanager.allowed doesn't exist", then it sounds like the plugin isn't loaded. do oxide.reload PermissionsManager and watch console. If it throws an error then PermissionsManager.cs isn't in your /oxide/plugins folder, or the file is damaged somehow.
-
Everything looks fine. My best guess is a timing issue when plugins are reloaded, as PermissionsManager removes, then re-adds them. I'll add a brief delay to see if that solves it.
- 242 comments
-
- 1
-
-
- #permissions
- #admin
- (and 7 more)
-
Thanks ^^. Are you on oxide or carbon? Any specific plugins it happened with, preferably free ones?
-
Are you folks on the latest version? I updated for this issue a little while ago.