RFC1920

Changed Status from Pending to Closed Changed Fixed In to 1.4.0

Yeah, that's another problem. Thanks. For now you can comment out line 1040: //ownsItem = false;

The way your pvp ruleset is set, players cannot damage anything but buildings. You have excluded BasePlayer as a source (attacker), so they can't even do that. For pvp, I would remove that exclusion for BasePlayer, which should allow players to damage buildings, but nothing else. If you are using version 1.3.8 from github/remod, note that there was a major issue which has been fixed. If you were using that version, that might have been the source for the confusion.

I have reached out to the maintainer. Testing my changes locally does actually update the list automatically, so hopefully he'll oblige.

I can work on that error. In NextGenPVE, DynamicPVP should manage it's own zone collection name, typically called "exclude". This should manifest in NextGenPVE as a ruleset called exclude. Since DynamicPVP calls out specifically to NextGen and the other pve plugin, it does not try to work with LootProtect or any other plugin afaik. So, in LootProtect, I think you should set EnabledZones back to null. I am not sure if DynamicPVP now names its zones as you specified in your config. But, I think having both EnabledZones and DisabledZones configured is not going to work. For where to disable it (DisabledZones), we would have to know the zones that DynamicPVP sets for each monument, etc. I can check with the current maintainer to see if they agree that the logic of calling specific plugins for those functions is no longer importatnt. This would allow us to automate the population of DisabledZones.

I am investigating this, but find it hard to believe this has been the state of things for the life of the plugin. I would recommend starting over with a new db and config.

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

Changed Status from Pending to Closed Changed Fixed In to 1.4.6

Thank you. Fixed in 1.4.6.

Changed Status from Pending to Not a Bug

I suspect that the elevation on your custom map may be other than default. I might be able to add a Y correction value for use in these cases, but unless you knew what that number was it would be hard to set. That said, I don't think this is a bug.

I rolled back the change requiring the sandbox adjustment in 1.3.8 - no version change.

Two different sources and errors. The first may be caused by the Oxide sandbox being enabled. Either disable manually or install the DisableSandbox plugin. The second error could be a plugin conflict, but probably isn't. This particular error is what 1.3.8 was for. But, there are still issues.

You don't need to create any rules for building privilege (TC) as this is handled explicitly. When in doubt, unload the plugin and remove the config file and database then reload.

Changed Status from Work in Progress to Closed Changed Fixed In to 1.4.5

It's getting better but I am not sure when this will be done.

The whole cooldown system is a real pleasure to maintain. This needs a rework.

Please try the pre-release 1.3.8 from https://github.com/Remod-org/NextGenPVE Let me know...

Changed Status from Pending to Work in Progress

This may be a map issue so I assume it's a custom map. This is definitely not normal and nothing has changed much in the art of teleportation to cause this. (I closed your other ticket. One is enough.)

Changed Status from Pending to Closed

Changed Status from Pending to Closed Changed Fixed In to 1.4.4

This may be a map issue so I assume it's a custom map. This is definitely not normal and nothing has changed much in the art of teleportation to cause this.

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

Indeed - fix in 1.4.3.