Steenamaroo
-
Posts
3,330 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
Sorry, what version of PlayerRanks. 2.3.1 is current. 2.3.0 removed debug which was accidentally left in. -
What version? I'm pretty sure I updated for that already, although it could be another one I missed.
-
I think the {0} and {1}, name placeholders, were backwards in the PlayerRanks lang file but, if I recall, I've since corrected that. The problem is that lang files only update for new entries - not amendments, so any users who had the plugin before that fix would need to switch those around in the lang file themselves. -
You know, I forgot NPCKits is slightly different, until your post. It's the same, but different. If BotReSpawn wants inv main (or any) wiped, it does it immediately after it gives out the kit. NPCKits waits until the npc is killed, and chooses not to move those contents from npc to corpse (which are two different things). I think I'll change that, some time, so it's the same as BotReSpawn, for the reasons mentioned earlier. -
AlphaLoot custom loot profiles not applying?
Steenamaroo replied to Somescrub's Support Request in Support
Yes, that's correct ^. In terms of functionality CustomLoot is perfect for the job, using it just to handle BotReSpawn npcs, and letting AlphaLoot do everything else but, admittedly, it's no where near as easy to use/understand. Still - It's there as an option. I just looked - I may be wrong but I think AlphaLoot has new or different API since I last checked. It looks like maybe I could set up 'AlphaLootProfile' as an option per BotReSpawn profile. If I write it in would you be willing to test? -
AlphaLoot custom loot profiles not applying?
Steenamaroo replied to Somescrub's Support Request in Support
This is how it works ^. If you make a Rust Loot Source selection in BotReSpawn's UI, that npc will get vanilla rust loot of that source. It's always vanilla - It's not related to, or subject to AlphaLoot. If you want the npc to get AlphaLoot loot, then you'd need Allow_Alphaloot true, then you'd go to AlphaLoot and set up a loot table for scientistnpc_roam, as you found out. You can do both, assuming neither plugin is set to wipe inventory first, and you will get whatever Alphaloot is pushing, plus whatever vanilla loot you asked for. If you want custom/modified loot per BotReSpawn profile the only option, at least that I'm aware of, is CustomLoot. -
Is the confusion coming from the fact that these are wipe-on-death options, but I actually carry out the wipe on spawn, immediately after the kit is given? If that's it there's a few reasons I do this. One is that it's possible for other plugins to force the npcs to fall wounded, which would mean if you have some item that you want with a 1% chance of being lootable on death, players could get it 100% of the time from a wounded npc if I'm doing my wipe code at npc death time. Another is that when the npc dies, there's more going on. At that point vanilla loot is happening and third party loot plugins are likely to be doing their thing. Running wipe_main at that stage is likely to trip over what they're doing and mess up vanilla or third party loot. For those reasons I put the wipe code straight after the kit give code, so I can be confident that I'm only wiping npc vanilla gear and/or stuff that was given via kit. For people who want to control % chances of vanilla loot that is given, there's the Allow Rust Loot % chance, and for anyone who wants to control % chances for third party loot plugins, well, that should be configurable in the third party loot plugin. It's done this way so you have maximum control and minimal interference.
-
"I already do this with the Trainyard NPCs. I use a kit that has a matching M249 to the clothing it wears. I don't want this NPC using the M249 against players, but I have a 1% chance that it will drop for the player if they are lucky. I have this set by using the setting for Main set to 99 and it loads from the Kit 100% of the time. At no time does it not load." Wipe main/belt/clothing happens the moment the kit is given out, so if you have a kit with m249 in the main container and wipe main set to 99% for that profile, and you're able to peek in vanish to see that m249 100% of the time, I'd say that's the problem - Not the other scenario. Would you mind double checking that profile to make sure you don't have its wipe main option to 1 instead of 99 by mistake?
-
I'm sorry, I'm really not understanding the problem. Maybe someone else can clarify, or we can simplify down to bullet points or something? I'm more than happy to help, I just don't see where the issue is. My understanding so far is that you want to give these npcs a kit. The belt should contain x/y/z the wear should contain a/b/c and the main should contain 1/2/3 "I want the player to have a 10% chance to acquire what's in the main inventory. " so you've set "Wipe_Main_Percent": 90 to achieve that. The result is that "They always have the Wearables, They always have the Belt, but only sometimes have the Main." That's exactly what I'd expect, and what your settings are meant to do. "Now, I don't know under what situation someone would want to put something in a kit, only for it not to always be there when you spawned in the NPC, but what I want to do is have it only sometimes be lootable by the player when the NPC is killed." You don't understand why someone would want kit main items to not be there 100% of the time, but that's exactly what you want? There must be a a terminology issue or one of us is making an assumption - I'm sorry, I can't make the leap. 😂
-
You're describing what that function does. Setting "Wipe_Main_Percent" to 90 is going to erase the contents of the npcs main inventory container 90% of the time, so if you're giving npcs a kit with items in belt, items in clothing, and items in main, 90% of the time those items in main won't be there.
-
Oh, ok. I see. It's because you've got "Wipe_Main_Percent": 90. Set that to zero to preserve the contents of their main inventory all of the time upon death.
-
BotReSpawn npcs can't open doors or, at least, I didn't code them to do that. If they do it's a vanilla npc thing that I'm not aware of.
-
Hey, Sorry, I'm not sure what you mean. Are you saying the npc no longer gets it kit and, therefore, has no weapon to fight with, or that the loot you expect to see on the npc's corpse is not correct?
-
Hi, I've already got that patched for the next update. Thanks for reporting it. ðŸ‘
-
One player cannot dmg BotReSpawn NPCs - all others can
Steenamaroo replied to EmberGaming's Support Request in Support
No worries. Thanks for the back and forth on it. Can I ask, was your test server a totally fresh install or a clone of existing? I know you said no plugins but I'm thinking oxide/carbon data, player data, etc. Does it have any harmony mods or dll extensions installed? Was it running Carbon or Oxide? -
One player cannot dmg BotReSpawn NPCs - all others can
Steenamaroo replied to EmberGaming's Support Request in Support
That's a pretty important insight. I already said but for clarity, the PVE_Safe code only comes into play if hitinfo intiator is null which means Rust does not know who/what caused this damage. That's useful to me for finding things like cacti/barricade damage where it's meant to be null, but it definitely shouldn't be null for a player. I could see an exception, maybe, for some unusual weapon, but certainly for LR,AK,M249, there's no reason player should be null. I'd be pointing the finger at some other plugin altering the hitinfo but you've ruled that out so, 100% I'd be pointing at the player. The reason this is affecting BotReSpawn npcs only is because BotReSpawn is specifically saying 'Protect my npcs if the attacker is null', so at least that makes perfect sense. I'll ask around and see if anyone has any insights -
One player cannot dmg BotReSpawn NPCs - all others can
Steenamaroo replied to EmberGaming's Support Request in Support
This is baffling. I'm afraid I don't have a public test server, no. I only ever had a local dev instance for writing and testing. The only return true (to prevent damage) which comes after the headshot code is for cases where attacking player is null. That code is for handling environment damage where there's no attacker - cacti, barricades, that kind of thing. If you go in to BotReSpawn global settings and set PVE_Safe to false, temporarily, then find that this player can suddenly hurt them, that would indicate something very messed up with this player. To be honest I think it has to be something messed up about that player regardless. -
Don't worry about it. There are no predefined points for any profiles but BotReSpawn can generate random points as long as there's open terrain with navmesh and a view straight up to the sky.. The Dome can have random positions just like any other but be aware the actual Dome gets in the way so you might need to make spawning radius slightly bigger than default to allow for that. The tunnels I'm pretty sure you just need to add custom spawnpoints, as allowing random spawnpoint choice will just find points on terrain above the tunnels IIRC.. At firs that might sound pointless but they are default monuments - One you add your spawnpoints the first time, you should be done forever. The npcs will always spawn at those custom spawnpoints in future, even on different maps. You can replace/remove/modify them any time you like, but you shouldn't need to. ðŸ‘
-
One player cannot dmg BotReSpawn NPCs - all others can
Steenamaroo replied to EmberGaming's Support Request in Support
That's interesting. As I said BotReSpawn has a few conditions in its damage hook which could potentially prevent damage, but they all come before the headshot checks. That means, without doubt, it isn't BotReSpawn that's preventing the damage because, if it was, the headshot related code wouldn't run. All the opportunities to cancel/prevent damage come before that. "We did try this on the test server to make sure it wasnt related to any other items." Was your player able to kill BotReSpawn npcs on the test server? If not I'd i'd guess there's something screwed up going on with that player's client. Maybe they could try on another public server, not yours, which has BotReSpawn, to prove that? I'm really struggling to think of an explanation for this but certainly if your player has issue with BotReSpawn on other servers that would rule out issues on your, or my, end. -
AlphaLoot custom loot profiles not applying?
Steenamaroo replied to Somescrub's Support Request in Support
Hi, It sounds like maybe you're conflating two separate options? The option for Rust_Loot_Source allows you to switch from the default vanilla loot that these npcs get to vanilla loot that some other container would get so, for example, instead of vanilla scientist loot you could make it that they have the vanilla loot that you'd normally find in a barrel, or medical crate. You can disable any/all vanilla loot by setting Allow Rust Loot Percent to 0. The Allow_Alphaloot option is just a true/false allowing you to prevent Alphaloot from populating these npcs, or allow it. Whether or not Alphaloot would be trying to give loot to BotReSpawn npcs would be configured on the Alphaloot side. BotReSpawn just blocks it, or does nothing. -
Not in a batch, no, but I'm pretty sure you can paste the same info multiple times having only copied once.
-
No worries. Glad to help, if I can. Trees wont have an effect on ai.think, performance difference, as far as I know. Most likely the main contributor is going to be animals. If that proves to be the case you could reduce animal numbers by convars? If that's no use maybe there's a reasonably simple way for a plugin to disable animal AI as they spawn, whilst leaving npc ai intact? Thinking out loud here. NPCLoot is free although, as I say, the option I'm talking about isn't in the public version but I can send it over to you to see if it's any use. Discord's good. Thanks for that. ðŸ‘
-
One player cannot dmg BotReSpawn NPCs - all others can
Steenamaroo replied to EmberGaming's Support Request in Support
Hi, That's an odd one. I'm struggling to think of anything in BotReSpawn that might do that. The damage-preventing checks that I can think of are if the player, or npc, is in a safe zone and Respect Safe Zones is true, or if the player is farther away than the Immune From Damage Beyond setting. It might be worth unloading all plugins then loading BotReSpawn solo and testing with this player, to rule out pve/pvp plugins or anything else that might govern damage for whatever reasons. -
Hi, It's not something I want to add to BotReSpawn. I've spent more time than I care to count troubleshooting issues with customers only to find the problem was some scummy plugin just auto-destroying all npcs in an X radius of their thing, so that's not something I want to inflict on others, even if it is behind a true/false user option. However, there are other approaches. The most obvious one I can think of is just letting BotReSpawn npcs kill these guys? You should be able to set that up on a per-profile basis using the Target_Other_Npcs option, and setting it to Attack. If, for some reason, that's no good I have two other options. I have written a feature in to NPCLoot (for customising vanilla npcs) that lets you turn them off, by location, but it isn't public yet. Now it doesn't catch every location kind, for reasons, but it does get a lot of them. It's still in testing stage but you'd be welcome to test that out and see if it's got you covered. Another option is I could add API to BotReSpawn to return all enabled profile locations as a list, then write a small plugin, using that, to just kill any spawning npcs which aren't BotReSpawn and are within X distance of any of those locations. It'd be like 10 lines. I don't mind doing that, if you want. Essentially what you're asking me to do except not in BotReSpawn plugin itself. Going back a step, is there a reason you need ai.think false? Maybe there's another approach there?
