RFC1920

Changed Fixed In to Next Version

Please let me know what you find with 1.4.0/1.4.1.

Changed Status from Pending to Closed Changed Fixed In to 1.4.1

I should be able to post another update either later tonight or in the morning.

I think I see why that's happening. Odd that this is the first time someone mentioned it.

I haven't had much time to look. However, it appears that as written, you should set the values to false.: if (configData.Rules[prefab]) { DoLog($"Rule found for type {prefab}. Access BLOCKED!"); return false; } So, if in your config you have "fluid.switch": true, then access would be blocked.

Changed Status from Pending to Closed

Changed Status from Pending to Work in Progress

I hope 1.4.0 fixes this. Even with full debug enabled this can still happen with no obvious logging thus far.

Changed Status from Pending to No Response

Changed Status from Pending to Closed

Changed Status from Pending to Closed Changed Fixed In to 1.4.0

1.4.0 adds (hopefully now working) check for item ownership if item is a deployed item.

Changed Status from Pending to Closed Changed Fixed In to 1.4.0

Changed Status from Pending to Closed Changed Fixed In to 1.4.0

Changed Status from Pending to Closed Changed Fixed In to 1.4.0

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.