TruePVE

In this particular instance the workaround "worked" because the BaseResource is no longer needed. Normally this wouldn't be the case and would probably cause more problems or errors, so waiting for an official update is recommended rather than trying to fix it yourself.

 

I needed to prevent players from raiding. I checked that the plugin is working with this fix and I used it.

 

I'm running the updated version of TruePvE, and here's the issue I'm running into;

Code:

TruePVE v0.7.17: Failed to load config file (is the config file corrupt?) (After parsing a value an unexpected character was encountered: r. Path 'RuleSets[0].flags', line 25, position 7.)

This occurs anytime I try to add additional flags (which is ALL I've attempted to do so far) beyond the three that are a part of the 'default'.

 

I agree. But I needed to start the server in work and I quickly got this with this fix.

 

That website doesn't appear to be working. I'll paste my config file in case any of you helpful, kind souls want to give it a look. The ONLY thing I've done is added flags (thus far).

I've also attempted to JUST add the flag "AuthorizedDamage", and that nets the same error. Adding ANY flags causes this, and I'm not fluent enough in JSON to know what I'm doing wrong.

Code:

{
  "Config Version": "0.7.17",
  "Default RuleSet": "default",
  "Configuration Options": {
    "handleDamage": true,
    "handleLooting": true,
    "useZones": true
  },
  "Mappings": {
    "default": "default"
  },
  "Schedule": {
    "enabled": false,
    "useRealtime": false,
    "broadcast": false,
    "entries": []
  },
  "RuleSets": [
    {
      "name": "default",
      "enabled": true,
      "defaultAllowDamage": false,
      "flags": "HumanNPCDamage, LockedBoxesImmortal, LockedDoorsImmortal, AuthorizedDamage, AuthorizedLooting, LootableCorpses, LootableSleepers, HeliDamageLocked“,
      "rules": [
        "anything can hurt dispensers",
        "anything can hurt players",
        "players cannot hurt players",
        "anything can hurt traps",
        "traps cannot hurt players",
        "players can hurt barricades",
        "barricades cannot hurt players",
        "highwalls cannot hurt players",
        "anything can hurt heli"
      ]
    }
  ],
  "Entity Groups": [
    {
      "name": "dispensers",
      "members": "BaseCorpse, HelicopterDebris",
      "exclusions": ""
    },
    {
      "name": "players",
      "members": "BasePlayer",
      "exclusions": ""
    },
    {
      "name": "traps",
      "members": "AutoTurret, BearTrap, FlameTurret, Landmine, GunTrap, ReactiveTarget, spikes.floor",
      "exclusions": ""
    },
    {
      "name": "barricades",
      "members": "Barricade",
      "exclusions": ""
    },
    {
      "name": "highwalls",
      "members": "wall.external.high.stone, wall.external.high.wood, gates.external.high.wood, gates.external.high.wood",
      "exclusions": ""
    },
    {
      "name": "heli",
      "members": "BaseHelicopter",
      "exclusions": ""
    }
  ]
}

 

Actually, I may have stumbled upon the issue thanks to the handy code feature here. My text editor may have been "helpfully" adding "smart quotes", changing the character of the close quote on the flags. It loads without error now.

 

Alright, NEXT dumb question from me;

I have everything configured exactly as I did before the wipe, however the Zone exemption doesn't appear to be working. No error messages, it's configured as before; per FAQ. But, simply, users inside the zone designated as PvP aren't being damaged. Thoughts?

EDIT: The problem appears to be that it doesn't like zones created by BuildingWrapper. Hmm...

 

Not sure from where to remove these two.From entity groups or?

 

Update ZoneManager and place the code from TRUEPVE Overview inside the .cs file.
should work again.
[DOUBLEPOST=1496418665][/DOUBLEPOST]

remove them from the "entity group" called "dispensers" in your .json config file.

 

I wasn`t understanding this, to be honest.Whats the effect if I leave them there?

 

doesn't seem to affect anything. but I took mine out.

 

It doesn't affect the functionality if you leave them in the config, but it's good practice to keep the config clean of unnecessary data. It'll prevent confusion in the future, and also prevent potential issues in the unlikely chance that a new entity is added to the game that matches those unused ones.

 

Thanks for the answers.I guess I`ll just clean it, this plugin is a very heart of my setup.

 

Does AuthorizedLooting actually protect furnaces/refineries/mailboxes regardless of whether they are in cupboard radius?
[DOUBLEPOST=1496617765][/DOUBLEPOST]

Yeah I just did some testing with players.Furnaces, refineries and mailboxes do not check for cupboard, they only let their owner access them.

 

The updated "AuthorizedDamage" doesn't appear to be working; players can't damage things that aren't owned by anyone. Thoughts?

 

Both AuthorizedDamage and AuthorizedLooting look at ownership first, then if the player isn't the owner it will check for cupboard authorization.

What have you tested?