RFC1920

Changed Status from Pending to Fixed Changed Fixed In to 1.0.14

Work in progress display of current multiple purge schedules. Editing next.

Work in progress on that and on an editor. Hopefully it will allow for multiple purge schedules per month.

I could just switch this to disabling of the plugin (global disable). That might work more as expected.

Added the first pass in 1.2.8.

Nothing current. I looked at a couple of other plugins including TimedExecute, but didn't see anything immediately satisfying for this need. I will look into adding it.

You can set the following, first off: "Multipliers": null That config is not used. The working config using multipliers (lower case) seems to be set for either 0% or 10% for some items. the 0.1 == 10% and is fine if that's what you want. I see that you have usePermission = true, so make sure your players or the group has that permission, or set that to false. I would probably set "cupboardCheckEntity": true to protect entities in cupboard range. Also, just in case after each wipe, run /nodecay update as admin to ensure that all entities are accounted for. This puts doors and windows into deployables, and that file is located at oxide/data/NoDecay/entityinfo.json

Hopefully fixed (again) in 1.0.17.

If resources matching any part of the building (as shown in the TC interface) are allowed to be added to the cupboard, then they will be used in the standard decay process. The way this normally has worked, and I am not aware that it changed, is that this bypasses the plugin altogether, at least for that resource. Since you seem to want to block all resources, please also set blockCupboardResources to true. This may have changed as of the most recent update because of some discovered faulty logic in the plugin. In short, if resources are in the TC when the decay.tick fires, we can't prevent the game from consuming those resources if they match any part of the building. Also, make sure that you are using the version from this site because it is not compatible with plugins with the same name on other sites.

Changed Status from Pending to Not a Bug Changed Fixed In to Next Version

This is controlled by Zone Manager Auto Zones. All of its monument zones should use a NextGenPVE ruleset called "exclude" by default. This appears to operate exactly like DynamicPvP. If you do not have a ruleset in NextGenPVE called "exclude," you would need to add one and set its default damage to true. Then, reload Zone Manager Auto Zones. It should populate the zone list for "exclude" using the zone ids it creates.

Changed Status from Pending to Closed Changed Fixed In to 0.4.2

Looking into it, should have a fix in the morning.

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

This should be fixed in 1.2.6. If that makes life worse, please roll back to 1.2.5 and I'll take another look.

I can see where that might be a problem. Will try to look this weekend.

Generally speaking that is true. But, we do not modify the helicopter's behavior. We monitor it. If it has decided to target you for any of the normal reasons, that is what determines whether or not your base will take damage. Looking over the code again (it has been awhile), it appears that you must set HonorBuildingPrivilege to true for this check to work. The only goal here was to prevent someone from intentionally using the heli to raid your base by baiting it while hiding in or around your base. If you want more in-depth control over heli behavior I am sure there are other plugins for that. The exception here to "we do not modify the heli's behavior" is HeliTurretTargetsPlayers which, if set to false, does modify the heli to not target players with it's turrets at least.

Looks like it is set to be days + 1.

Changed Status from Pending to Closed Changed Fixed In to 1.0.75

If you were targeted by the heli for any reason then your base would be fair game (shot at it, wearing more than 2 items of clothing, holding an actual gun of some kind).

There is already a check for inactivity called protectedDays. For example, if set to 14 and the player has not been on for 14 days, it should start decaying their building regardless. My concern is that the blocking of resources is not working, which I will check in a bit. It definitely used to work. Are you sure you are using the official NoDecay from either codefling or remod? What version number? EDIT: I think I found it. I guess no one ever used this because it was not checking those config values correctly. Fix pending.

On their page they specify that you have to exclude "CustomScientistNPC". Check out the videos on the description page for more information. I think you may need to use the Rule/Entity Editor to verify that CustomScientistNPC is set as category NPC.

The default configuration allows players to damage the heli, heli to damage the players attacking the heli, and heli to damage buildings owned by a player targeted by the heli. I know this much works, so if it does not then there must be something else conflicting. Worst case there is a reset and/or you can delete the nextgenpve.db in data and the NextGenPVE.json in config and reload to get back to the default.