RFC1920

Is it just that typing into input boxes is not working or is there something else going on? Note that after typing into an input box, assuming you can finish without interruption, hitting enter should save it. If you can show me what's going on somehow that would be helpful.

You can't have spaces is one thing I noticed. Otherwise, I tried to disable other commands while in the gui, but it could depend on your keybinds.

The new (1.0.52) rule editor allows you to create your own rules. It needs work, but basically you should set the name as something like player_test. Set the source to player and target as test. Next, edit any of the available entities to the test collection. Note that at least currently there is no way to have entities in multiple collections. This is because, ultimately, each entity is checked for damage allow/deny at run time and in comparison to active rules in a ruleset. It might get a little messy if an entity were to be compared to multiple rules.

Changed Fixed In to 1.0.52

Changed Status from Pending to Closed

This was added to the original version on another site. Out of respect, I won't be adding that here.

Changed Status from Pending to Closed Changed Fixed In to 1.0.3

I absolutely think it's the best Anyway, I had plans early on to implement custom rules. If things are truly stabilized, I might be able to work on that.

There is a plugin I use (EntityOwner.cs) where you can own and unown (sic) surrounding entities. This was how I tested. THe same plugin has the /prod command to let you confirm who owns whatever you're looking at.

NPC Play is my plugin, currently hosted on remod.org.

Please try 1.0.48 and let me know.

What are your settings for: "useFriends": false, "useClans": false, "useTeams": false,

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

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.

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.

Changed Fixed In to Next Version

The closure is automatic. I'll look into it.

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.

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.

Changed Status from Closed to Pending Changed Fixed In to Next Version

It was autoclosed because I have been away and busy. If you can, type /pvelog in chat, try to repeat whatever you were doing that triggers the error, and type /pvelog again. Send me the log in oxide/logs/NextGenPVE/ with the current date in the filename.

The problem is quite the other way around, btw.

If you have configured "useFriends": true, you must have the Friends plugin. Likewise, if you have configured "useClans": true, you must have one of the available Clans plugins. Please verify that if you do not have one of these that the associated config is set to false.

Changed Status from Pending to Closed

On line 283, you could change if(ms > 10 to if(ms > 15 or something like that.