Steenamaroo
-
Posts
3,741 -
Joined
-
Last visited
-
Days Won
211
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Steenamaroo
-
Hi @maxalt There's an option in the Global config - Allow_Oilrigs. Sounds like you just need to set that to true. They're optional because there's no navmesh there and, so, having them as an enabled monument by default doesn't make sense, but some like to use them for stationary npcs regardless. -
Thank you. No, respawning is only time-based at present.
-
Hi, Thanks for reporting. I'll have to look in to that tomorrow and see what's happening. I'll update you when I know more.
-
Hi, What, specifically, were you looking for? Seems Facepunch have introduced a new npc type in certain areas, including the oilrig, which doesn't inherit from BasePlayer, use .userID, or use traditional inventory. Whether alternative approaches are developed in future I can't really say, but, for now, these npcs are fundamentally incompatible with NPCKits/Kits. -
Hi, I think you're on the wrong plugin page. This is UpdateSChecker. You're looking for UpdateChecker.- 53 comments
-
- 1
-
-
- #updates
- #steenamaroo
- (and 5 more)
-
Hi, Not exactly like that, no, but there are options to prevent Clan mates/Friends from contributing to PVPKills, so groups can't farm PVPKills by killing each other.- 458 comments
-
- 1
-
-
- #statistics
- #leaderboard
- (and 12 more)
-
Hi, I don't mark Carbon compatibility just because I don't test on Carbon myself, but if issues are reported I look in to them and, in the past, the Carbon team has made any necessary changes. That hasn't happened in some time so, realistically, everything should be good. -
Most likely, yes. I'll have to take a look at it, though.
-
lol. No problem. Glad you found it and thanks for letting me know.
-
Hi, If I had to guess, most likely a call from another plugin. If, for example, that was a BotReSpawn npc you killed, you have the choice of RustRewards managing and issuing the reward, though the value set in its UI, or BotReSpawn managing the reward through the 'RustRewardsValue' set in its own UI. It's a per-profile option under the 'Death' tab. The reason, or advantage, is that RustRewards can only see 'BotReSpawn' as one broad type, whereas using BotReSpawn UI to manage the rewards lets you have different reward values for different profiles. If both are enabled + greater than zero, you'd see two separate rewards coming through. There are other plugins which operate the same way, giving you the choice, so that's where I'd look.
-
Hi, No worries - Thanks for the info. Are you 100% sure it's happening when killing npcs? It's a client side update error, which is kind of strange. You'd expect to see that if a player was parachuting and something went wrong, I think.
-
I'm really not sure what that could be. I'd have to try to replicate it to find out. With regard to the sense/assist code, there was an issue that would just prevent nearby npcs from locking on to you. A console error was possible, but there shouldn't have been any impact on behaviour, other than failing to engage.
-
I did find an issue. I think an object I'm addressing is maybe being disposed of sooner than it used to be. I've patched it now and all seems well. NPCs shouldn't be running to nowhere, though...Not sure what that's about. Can you tell me more?
-
Ok, thanks. I'll take a look now.
-
Hi, Is global setting NPCs_Assist_NPCs set to true?
-
No problem. Have fun!
-
Hi, Yes, every profile has a Respawn Timer (in minutes) which you can increase. You'll find it in the 'Death' tab for every profile in the /botrespawn UI.
-
Hi there, It sounds like you have Peacekeeper set to true for that profile. Changing it to false in the BotReSpawn Ui should solve the problem.
-
Error at oxide.reload - file modifications
Steenamaroo replied to Lolapalooza's Support Report in Support
Glad you found the problem. Thanks for updating me and sorry for the delayed reply. Codefling no longer notifies me, again, for whatever reason, and the compose-new-message box was missing all day yesterday. -
Error at oxide.reload - file modifications
Steenamaroo replied to Lolapalooza's Support Report in Support
Hi, Can you send me the default.json file, please? I'll see if I can figure out what the problem is. -
DM sent.
-
Hi, That's not an option right now or, at least, it's not an automated set-and-forget option. There is a 'toplayer' command in BotReSpawn, though, so it's possible to set up profiles with are AutoSpawn false, just for that purpose, then periodically use the 'toplayer' command to call in npcs as you describe. A small additional plugin could do this automatically every X minutes. I could put that together for you to demonstrate, if you want.
-
Thanks for doing that. I'll test again tomorrow with the weapons you mentioned, as I only used ak47 before. I'll keep you posted!
-
Yeah, that's a solid idea. Thanks @Malkizid @Painfully Ordinary- There are commands to enable/disable profiles but be aware that disable turns the profile off but also kills off any existing npcs, so you'd probably still want to set respawn time prohibitively high, then set TimedExecute to run as late as possible during your first day. If you have a plugin automating your server restart, you could even, maybe, incorporate the profile disables in to that.
-
Thanks for the info. There shouldn't be any problem as I believe Carbon is meant to be compatible with all oxide plugins, and any time there have been issues they've updated to address them. I didn't tick the box simply because I use oxide when writing and testing so I can't personally stand over Carbon compatibility.