search

Remod-org / NextGenPVE

Prevent damage to players and objects in a PVE environment
GNU General Public License v2.0
7 stars 0 forks source link

player_building (Building damage is not disabled without global settings.) #3

Open HromoiPojarnik opened 7 months ago

HromoiPojarnik commented 7 months ago

The player_building rule does not work - it only applies to the cabinet (the building is damaged, but the cabinet is not), however, when changing the global settings of the raid ban, the building begins to receive damage. At the same time, the default rules, for example, player_npc, work perfectly! What could be the matter? I have cleared the authorized list in the closet... Why does this rule not apply to buildings?

RFC1920 commented 7 months ago

Can you provide some logs from when this occurs? Run /pvedbug and /pvelog before and then again after. Logs should be in oxide/logs/NextGenPVE folder.

HromoiPojarnik commented 7 months ago

Sorry I'm stupid, I've been suffering for two days with the setup. So I made a little video about it. Only global settings are triggered for the destruction of buildings :(I can't figure out what's going on. I use these plugins (Zone Manager, Zone Manager Autozone, Dynamic PVP, Zone Domes, ZonePVxInfo, NextGenPVE). Everything works fine with murders and auto zones, the problem is only with the destruction of buildings. nextgenpve_log-2023-11-27.txt

2023-11-27_22-26-19 2023-11-27_22-26-51 2023-11-27_22-27-08 2023-11-27_22-27-35 2023-11-27_22-27-52

RFC1920 commented 7 months ago

The log says that HonorBuildingPrivilege is set to false. Are you sure the config above is what you are using? Checking a boolean value like that is not a mystery so I don't see how it could get it wrong.

HromoiPojarnik commented 7 months ago

I don’t understand anything anymore, in the house that my son built, the global settings work, but in the house that a friend from STEAM built, they don’t work at all. In the second case, I had nothing to do with the construction of the house and was not authorized in the closet. Moreover, as I wrote earlier, when changing the default set of rules, player_building only works on furniture but does not work on buildings, the player_player parameter works perfectly. I thought that there was a conflict with other plugins and yesterday I specially disabled them, leaving only 5 (DynamicPVP,NextGenPVE,ZoneManager,ZoneManagerAutoZones,ZoneDomes,ZonePVxInfo) related to zones, but the problem was not solved. Maybe the problem is in privileges or in the settings of the DynamicPVP,ZoneManager,ZoneManagerAutoZones,ZoneDomes,ZonePVxInfo plugins? video

Set it up like this: Registered in Server\rustds\server\my_server\cfg\server.cfg server.pve false

Added the line //Requires: NextGenPVE to DynamicPVP.cs.

In Server\rustds\oxide\config\NextGenPVE.json changed "useZoneManager": false to true

In oxide\config\ZoneManagerAutoZones.json I enabled "Enable NextGenPVE to allow Rule Sets": true There I also included the zones I needed for PVP so that in NextGenPVE exclude/lookup there were only these monuments...

In the ZonePVxInfo.json file, I only changed the location of the button, but to make it work, I changed all the lines in the ZoneManagerAutoZones.CS plugin monument.displayPhrase.english; on monument.displayPhrase.english + "[PVP]"; so that the indicator changes from green to red PVP/PVE

Well, I translated some buttons and messages.

oxid.zip