Stones and Wood upgrade. I attached my JSON file. pls check. I did what Krazy J told me to do and even tried copying the text many times but still doesn't work.
TruePVE
Better PVE/PVP implementation
Total Downloads: 4,637 - First Release: Mar 25, 2016 - Last Update: Mar 7, 2018
-
here you go.. the plugins work fine tho.. it's been working great atm.. but still the "Failed to call hook 'OnServerInitialized' on plugin 'TruePVE v0.7.3' (InvalidOperationException: Operation is not valid due to the current state of the object)" message pop up when i load the plugin.. but it still works
... well after the update to 0.7.3 it doesn't work now
could it be another plugin is not compatible with TruePVE?Attached Files:
Last edited by a moderator: Mar 10, 2017 -
@Krazy J: Well, you can change whatever you like - you could even clear all the rules out... But here's the kind-of-long explanation...
Ignoring for now the name and enabled fields on the RuleSet, as those are self-explanatory - there are 3 sections of a RuleSet:
1. defaultAllowDamage - This flag is the "catch-all" of your rules. If you want a RuleSet that primarily allows damage, you set this to true, otherwise, you set it to false.
2. flags - These are flags that do some advanced damage control. Essentially, these are things that are too difficult or impossible to write a rule for, so I create a flag that handles it. For all intents and purposes, flags are built-in rules.
3. rules - Rules are essentially some specialized damage control that you want that isn't covered by the defaultAllowDamage. The rules override the defaultAllowDamage flag, making it so you don't have to define ALL of the individual entities and what they can/cannot hurt.
To start off, say you only want standard PVP behavior without any customization, then you don't need ANY flags or rules entries. But say you wish to have PVP, but don't want turrets to be able to hurt any players - first you define what entities make up "players" and "turrets" (that's what Entity Groups are). Then you use those entity group names to write out your rule: "turrets cannot hurt players".
When it comes to defining your RuleSet, start with the overall damage handling (defaultAllowDamage), then narrow down what you want to happen. If your overall damage handling is set to true to allow all damage, then normally you don't have to write rules to allow damage.
An exception to the previous assumption is when you need to override a broader rule. For example, in the "default" RuleSet we have defaultAllowDamage set to false - so block all damage. Then there's a rule "anything can hurt players", because we want players to be able to take damage overall (from falling, temperature, animals, hunger, etc). This rule is broad because it says anything can hurt players. But since we don't want to allow damage from other players, then we have to define yet another more specific rule to override the "anything can hurt players" rule, but only for players. So we say "players cannot hurt players". When TruePVE then processes the damage for a player attacking another player, it first gets the Entity Groups - attacking player is in group "players", and target player is also in group "players". Then it checks to see if there is a rule directly linking the two groups. The first rule it sees is "players cannot hurt players", which it uses as a basis to nullify the damage. If the "players cannot hurt players" rule did not exist, then TruePVE would check first if there is a "players (attacking player group) can/cannot hurt anything" rule, and then "anything can/cannot hurt players (target player group)" rule. And, assuming none of those rules existed or matched, the defaultAllowDamage flag is used - false - which will nullify the damage.
