Jump to content

SamSites not ignoring players

Closed 1.0.44

iLakSkiL

Posted

No matter how I configure the file, SamSites continue to target players. I have it enabled in global flags, and I've tried everything with other settings for traps, turrets, and copters, but nothing seems to actually work. However, I do still want the static sam sites, the ones at launch, to target and kill people.

ChaoticStryfe

Posted

  Quote

I do still want the static sam sites, the ones at launch, to target and kill people.

Expand  

this needs to be done as there is no challenge to players at launch site

RFC1920

Posted

Verify that your config reads "SamSitesIgnorePlayers": false if you want the default behavior.  This should equate to the GUI showing that flag as gray, not green.

ChaoticStryfe

Posted

It does say false - while it does shoot at players, it causes no damage

RFC1920

Posted

So it is targeting - good.  The lack of damage is because there is no exception for it.  You will need to enable the trap_player rule, then exclude all but the samsites as source.  This should allow only SamSites to hurt players while leaving other traps safe.

iLakSkiL

Posted

I was under the expectation that turning the Flag on for "SamSitesIgnorePlayers": True, will have player built sams not target anything, but they still are for me.

ChaoticStryfe

Posted

  On 9/20/2020 at 6:29 PM, RFC1920 said:

So it is targeting - good.  The lack of damage is because there is no exception for it.  You will need to enable the trap_player rule, then exclude all but the samsites as source.  This should allow only SamSites to hurt players while leaving other traps safe.

Expand  

could you tell me what that would involve exactly - new to pve plugin  thanks

RFC1920

Posted

Click on any of the existing rules in your ruleset (e.g. player_resource) and you should be presented with a list of all rules - click on trap_player.  Now, click on the source exclusions button and select Shotgun trap, repeat for the other traps such as autoturret, etc.

  • Like 1
ChaoticStryfe

Posted

  On 9/21/2020 at 7:06 PM, RFC1920 said:

Click on any of the existing rules in your ruleset (e.g. player_resource) and you should be presented with a list of all rules - click on trap_player.  Now, click on the source exclusions button and select Shotgun trap, repeat for the other traps such as autoturret, etc.

Expand  

Either I did it wrong or  it's not working (didn't see shotgun trap) do you have a config that I could just upload with only sam sites at launch able to do damage?

RFC1920

Posted

I'd rather let that get handled by a separate plugin that manages SAM sites.  We call a hook to see if things can be damaged, and that could be used by another plugin to determine damage based on Launch Site vs. user SAMs.

 

But in general, if the trap_player rule is active (visible in the ruleset), you should see traps listed as available for exception.

  • Like 1
ChaoticStryfe

Posted

I see that it's not so much the sam sites as it is that the launch site building is flagging as a pve zone. shouldn't the entire launch area be pvp and not just where the bradley travels away from the building?

ChaoticStryfe

Posted

just looked again to double checked and the main area of launch site is not being marked as pvp as it should be it's half pve and pvp

RFC1920

Posted

What is supposed to do that?  Do you have a zone setup there?

ChaoticStryfe

Posted

  On 9/21/2020 at 11:38 PM, RFC1920 said:

What is supposed to do that?  Do you have a zone setup there?

Expand  

No, all the other monuments are 100 percent pvp.  At launch it's like 75 percent covered

Guest

Posted

Changed Status from Pending to Closed

1.6m

Downloads

Total number of downloads.

7.7k

Customers

Total customers served.

115.3k

Files Sold

Total number of files sold.

2.3m

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.