-
Posts
926 -
Joined
-
Days Won
48
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by RFC1920
-
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.
-
PreventLooting also adds the share and unshare commands. It's doable, but I'm not sure why one needs the be the monolith.
-
I usually use PreventLooting for that, which is why it's not included.
-
Please set the config variable useSchedule to true if it is not. If that clears it I have a fix.
-
On restart is there anything about this in the server or oxide logs?
-
This is not setup to work with that version. You would have to use the version from remod.org.
-
Changed Status from Pending to Closed Changed Fixed In to 0.3.0
-
Disable outputMundane in your config.
-
Changed Fixed In to 0.2.9
-
cctvcontrol.admin appears to allow it, even if the user is not in the admin group.
-
Well, it definitely works for some and nothing has changed to make it stop working that I know of. If you can do the check with logging enabled it would be helpful.
-
Looks like you are building blocked, which has nothing to do with this plugin.
