The Pve server. I've had it set up for a long time that anyone can break straw-and none of the players can destroy the rest of the materials, but after the updates I can only break my straw-the rest seems to work. Tell me what can be done, please)

Сервер Пве. У меня было настроено уже давно что солому может ломать кто угодно-а остальные материалы никто из игроков не может разрушать, но после обновлений я могу ломать только свою солому-остальное вроде работает. Подскажите что можно сделать пожалуйста)

Same for me.

My intended and tested/working setup 'til the last update was: Everyone can break twig, regardless of a TC in place. Other materials can be damaged by TC authed players.

Since the last update with the same config: When no TC is present, everyone can break twig. But as soon as a TC is present, only TC authed players can break the twig. Other materials work like intended. My shortened config:

...
"TwigDamage (FLAG)": {
"Apply To Twig (when TwigDamage flag is not set": false,
"Apply To Wood": true,
"Apply To Stone": true,
"Apply To Metal": true,
"Apply To HQM": true,
"Require Owner Online": false,
"Log Offenses": true,
"Notify Offenders": true,
"Reflect Damage Multiplier": 0.0,
"Multiplier Allows Armor Protection": true
},

...

"RuleSets": [
{
"name": "default",
"enabled": true,
"defaultAllowDamage": false,
"flags": "AnimalsIgnoreSleepers, AuthorizedDamage, AuthorizedFarmableDamage, CupboardOwnership, HumanNPCDamage, NoHeliDamageBuildings, NoHeliDamageQuarry, NoHeliDamageSleepers, ProtectedSleepers, SelfDamage",
"rules": [...

Hey nivex,

after your (deleted) answer, I'm now testing on a server with todays facepunch updates installed and no other plugin than TruePvE. I must confirm my findings and description from last post. Could it be that you treat "Apply To Wood": true" at some points in your code as sufficient to destroy twig?

And I found an other one:

According to my config, I pair AuthorizedDamage with CupboardOwnership. So according to documentation, if a TC is present, only TC authed players should be allowed to damage buildings (I testet foundation). This works for me, with the exception that the builder/owner of a building part can damage even after deauthed at cupboard.

Hi guys,

Twig damage behavior has not changed between 2.3.5 and 2.3.7. What you are seeing is expected: the current config is explicitly blocking twig damage when there is a TC.

With the configuration you posted, the expected behavior in all versions is to:

• Allow without TC

• Block with TC

This is because CupboardOwnership requires authorization when a TC is deployed, unless you bypass it. defaultAllowDamage can block the damage too, unless bypassed (do not change defaultAllowDamage, it should remain false in PVE rulesets).

If you want twig damage to always be allowed (with or without a TC), add the TwigDamage flag to the flags list.

"flags": "AnimalsIgnoreSleepers, AuthorizedDamage, AuthorizedFarmableDamage, CupboardOwnership, HumanNPCDamage, NoHeliDamageBuildings, NoHeliDamageQuarry, NoHeliDamageSleepers, ProtectedSleepers, SelfDamage, TwigDamage",

One more thing: I did find two separate issues. The material options do not currently work as intended - when set to true, damage is not allowed. A trace confirms this (no trace output means another plugin told TruePVE to allow it instead). Also, they do not currently require the TwigDamage flag the way they should. These two issues will be fixed in the next update.

If you're seeing behavior that differs from the above, it's another setting or another plugin. Using the above configuration, attacking a wooden foundation with the Apply To Wood option set to true. I will fix this:

(23:51:07) | [TruePVE] ======================
==  STARTING TRACE  ==
==  05:51:08.01038  ==
======================
 From: BasePlayer, player
 To: BuildingBlock, foundation
 No exclusion found - looking up RuleSet...
 Using RuleSet "default"
 Initiator is player and target is Wood block, block and return
 Initiator is player and target is Wood block, with damage option set; block and return

heya, yes it is confusing! especially when the code has bugs. I've included it in the documentation as requested. Note that the documentation for this reflects the next version (2.3.8 and up). Let me know if there's any confusion still.

https://umod.org/plugins/true-pve#twigdamage-flag-twig-wood-stone-metal-and-hqm-grade-options-with-or-without-the-twigdamage-flag

Thank you so much. I will have a look at it.

Hi! I have this setting enabled (example flags below). But it doesn't work. Please tell me what exactly am I doing wrong)

  "RuleSets": [
{
"name": "default",
"enabled": true,
"defaultAllowDamage": false,
"flags": "HumanNPCDamage, SelfDamage, LockedDoorsImmortal, PlayerSamSitesIgnorePlayers, StaticSamSitesIgnorePlayers, NoHeliDamageQuarry, TwigDamage",
"rules": [

Hi @dralden1

You're right, I just tested all versions from 2.3.2 to 2.3.7 and none work properly (only partially) with only the TwigDamage flag when Require Owner Online is set to true.

This will be fixed in the next update.

Understood) Thank you very much)

hi, I have a version available for anyone that wants to try it. notes are in the top of the file

https://github.com/nivex09/TruePVE

Tried with TruePVE from github, completely without Teams, Clan and Friends.

To recap my intention: Everyone can break twig, regardless of a TC in place. Other materials can be damaged by TC authed players only. Not authed players should generate a warning message. My Idea: Someones who has building privilige can use the removertool anyway.

current config:

...
"TwigDamage (FLAG)": {
"Apply To Twig (no flag required)": true,
"Apply To Wood": false,
"Apply To Stone": false,
"Apply To Metal": false,
"Apply To HQM": false,
"Require TwigDamage Flag": false,
"Block Damage From Ally": false,
"Block Damage When Owner Is Online": false,
"Log Offenses": true,
"Notify Offenders": true,
"Reflect Damage Multiplier": 0.0,
"Multiplier Allows Armor Protection": true
},
...
"RuleSets": [
{
"name": "default",
"enabled": true,
"defaultAllowDamage": false,
"flags": "AnimalsIgnoreSleepers, AuthorizedDamage, AuthorizedFarmableDamage, CupboardOwnership, HumanNPCDamage, NoHeliDamageBuildings, NoHeliDamageQuarry, NoHeliDamageSleepers, ProtectedSleepers, SelfDamage",
...

• "TwigDamage (FLAG)": {
• "Apply To Twig (no flag required)":
• "Require TwigDamage Flag":
• and the other ruleset-flags like TwigDamage, WoodDamage, ...

hi, you shouldn't receive any messages when "Block Damage From Ally" and "Block Damage When Owner Is Online" are both disabled

I've rewritten the relevant documentation, please let me know if you understand it now

Well, I would like to inform the average new player, that bases are protected when they trying out things. Would be enough to throw one message at let's say 10 seconds. Maybe on first offend posting a message, setting a flag and fireing a timer to block consecutive offend-messages for 10 seconds.

It's documented that these options will not send any messages when they are disabled. In those cases, damage is handled by other functionality in the plugin, so any related messages must come from that functionality instead (options, rules or defaultAllowDamage) of which each pose their own issues regarding clarity of any messages. The options under TwigDamage exist only to provide functionality that is not possible through standard rules. Because of that, they only apply when enabled, not the other way around. 

Either way, your questions have become split across two different threads so any further responses belong in your thread. This thread is now closed, thank you for your understanding.

https://umod.org/community/true-pve/57665-protect-unlocked-tc-from-being-accessed-by-enemy-players-not-working?page=1#post-5