TruePVE

@ignignokt84,

If I wanted to stop damage to foundations only in a zone. How would I need to configure that? do I use shortname or prefab name? or.... ?? lol

"Raid Zone B": {
"Foundation": {
"name": "Zone",
"description": "Foundation Damage",
"prefabs": [foundation.prefab],
"types": [],
"links": {
"player": false
},
"enabled": true
},

This is an example of what it would look like ? Not sure what I would do next. I haven't really messed with mappings too much.

 

@Krazy J, That's close. If you use the chat command /tpve_prod while looking at a foundation it will tell you the prefab name that should be used for the mapping. Then in the mapping for foundation, you don't need any links. Links define what can and cannot be damaged BY the group, so if you say "foundation" links to "player": false, like above, then you're saying foundations can't hurt players It should look something like the below mapping, then add "foundation": false to the player links...

Code:

"Raid Zone B": {
  "foundation": { // this is a reference to the name of the group below, so it must be the same
    "name": "foundation", // must match previous row
    "description": "Foundation Damage",
    "prefabs": [
      "foundation", // this is your foundation prefab name you get from /tpve_prod
      "foundation.triangle" // triangle foundations (just guessing at the name), also from /tpve_prod
    ],
    "types": [],
    "links": {},
    "enabled": true
  },

By the way, almost done with 0.7.0, which simplifies the config quite a bit, and should make setting up rules much easier...

 

ignignokt84 updated TruePVE with a new update entry:

0.6.8

 

So will this fix the problem I've been having?

 

Yes it should - I was seeing the same issues on my side (using your same config), and this resolved all of the issues.

 

"Raid Zone B": {
"Foundation": {
"name": "Foundation",
"description": "Foundation Damage",
"prefabs": [
"foundation",
"foundation.triangle"
],
"types": [],
"links": {},
"enabled": true
"player": {
"name": "player",
"description": "Foundation damage from player",
"prefabs": [],
"types": [],
"links": {
"foundation": false,
"foundation.triangle": false
},
"enabled": true
},

Something like this im guess. IF I use the data for player on the outside of the zone, wont that make foundations non damageable globably ? even though they are already. Im just trying to keep it all in 1 zone.

 

BWAHAHAHA IT WORKS!

 

That's close, but it looks like your "player" is inside your "foundation", so make sure your bracketing is correct.

Yes that's correct, but the rules aren't recognized outside of their ruleset, so if the "default" ruleset would see "foundation" (from "Raid Zone B") it would not have any idea of what to do. When TruePVE processes the rules for a specific ruleset they're completely independent of every other ruleset, so you are correct that you need to have a "player" inside your rules for your zone.

 

Yeah, that's what I thought. I'm having a problem with it resetting to default .json again. Cant get the mappings I want in "raid zone B" to stuck. LOL

I don't suppose this is Correct?

Code:

    "Raid Zone B": {
      "Foundation": {
        "name": "Foundation",
        "description": "Foundation Damage",
        "prefabs": [
          "foundation",
          "foundation.triangle"
        ],
        "types": [],
        "links": {},
        "enabled": true
      "player": {
        "name": "player",
        "description": "Players",
        "prefabs": [],
        "types": [
          "BasePlayer"
        ],
        "links": {
          "foundation",: false,
          "foundation.triangle": false
        },
        "enabled": true    
     },

 

Nope, you're missing some brackets between foundation and player. FYI, you can validate the json formatting on a site like JSONLint - The JSON Validator.. Just paste in your entire config, and it will parse and format it and tell you if it's a valid format or not and where any issues are.

 

ok, I put the brackets in copied it all into the config and it said it was a vali json file.

 

Try to validate the entire config at once - I assume that section by itself isn't a valid json.

 

yeah, I did that afterwards and then edited my post.

I just put it into the server files, it didn't seem to revert it. now I'm gonna test my work.
[DOUBLEPOST=1489005596][/DOUBLEPOST]

Ok, so the .json is right. but when I reload with this configuration and test it, it still allows damage like theres nothing blocking damage.

 

The json format is right, but that has nothing to do with whether it's set up correctly or not. Your raid zones are both incorrectly configured - your player groups need to link to the foundation group name, not the foundation prefabs. Anyway, this will be moot with the next release...

 

I tried linking "player group" to "foundation group" didn't seem to matter. It didn't change the damage. I did this a couple times. I'll try it again, when I get this right, I'm sure you're next update will be out.

This is now how I have that section set: (Which I had it this way a coup times.)

Code:

"Raid Zone A": {
"Foundation": {
"name": "Foundation",
"description": "Foundation Damage",
"prefabs": [
"foundation",
"foundation.triangle"
],
"types": [
  "BuildingBlock"
],
"links": {},
"enabled": true
},
"player": {
"name": "player",
"description": "Players",
"prefabs": [],
"types": [
  "BasePlayer"
],
"links": {
"Foundation": false << -------- links the Foundation group (My guess is I'm correct.)
},
"enabled": true
}
},

 

ignignokt84 updated TruePVE with a new update entry:

0.7.0

 

I'm gonna have to learn this one now LOL

 

@ignignokt84 Do you mind sending me a quick private message? I need some assistance on this plugin, but need to send you the configs and whatnot

 

Any chance we can get an example of a PVP enabled zone config? Please and Thank you!

 

If you're looking for default Rust PVP in the zone, you only need to add an "exclude" mapping for your zone, and of course turn on useZones:

Code:

  "Mappings": {
    "default": "default",
    "mypvpzone": "exclude"  // this skips all handling, no RuleSet needed
  }