Item Tweaker 1.1.0

It seems that Realism doesn't display the actual armorClass when inspecting an armor. For Vulkan it shows "GOST 5", but the actual armorClass value is 8, so you would be lowering it. Also looks like it changes it to an actual number, instead of a string, so your "7" has to be without quotes.

You can set verbose to true in Item Tweaker's config.json, so it will show you any mistakes and also the original value and whether it was changed. This should help you confirm that any changes actually applied since you can't see them on the UI.

For reference on Realism's values you can look around in it's files, but you should probably avoid editing them unless you're sure about what you're doing. The "GOST 5" armor class for Vulkan you can find in Realism's db/templates/gear/Realism/helmetTemplates.json. The actual armorClass values seem to be in src/armor.ts.

Thank you, removing the quotes fixed it. Weirdly enough, the initial armorClass wasn't 8 but 4 in the armor.ts:

 //Vulkan-5
            if (serverItem._id === "5ca20ee186f774799474abc2") {
                serverItem._props.Durability = 25;
                serverItem._props.MaxDurability = serverItem._props.Durability;
                serverItem._props.armorClass = 4;
                serverItem._props.speedPenaltyPercent = -2.25;
                serverItem._props.mousePenalty = 0;
                serverItem._props.weaponErgonomicPenalty = -2.25;
                serverItem._props.BluntThroughput = 0.32;
                serverItem._props.DeafStrength = "High";
                serverItem._props.ArmorMaterial = 'UHMWPE';
                serverItem._props.Weight = 4.5;

And it wasn't GOST 5 but GOST 2 in helmetTemplates.json :

 "5ca20ee186f774799474abc2": {
        "ItemID": "5ca20ee186f774799474abc2",
        "Name": "item_equipment_helmet_vulkan5",
        "AllowADS": true,
        "LoyaltyLevel": 3,
        "ArmorClass": "GOST 2"

I only have realism that changes armor classes though, i don't know why it's a different armor class than yours...

Dunno, maybe the versions are different. I simply downloaded the latest version to try it and find out what's the issue, but the principle is the same anyway. Good to hear that it worked for you.

I did this :

"item_equipment_helmet_vulkan5":
    {
        "set":
        {
            "armorClass": 7,
            "Slots":[
              {
                "_name": "mod_equipment_000",
                "_parent": "5ca20ee186f774799474abc2", // Id of the                                                                                                                 // vulkan 5
                "_props" :{
                  "filters": [
                    {
                      "Shift": 0,
                      "Filter": [
                        "5ca2113f86f7740b2547e1d2" // Id of faceshiel
                      ]
                    }
                    ]
                }
                
              },
              {
                "_name": "mod_equipment_001",
                "_parent": "5ca20ee186f774799474abc2", // Id vulkan5
                "_props" :{
                  "filters": [
                    {
                      "Shift": 0,
                      "Filter": [
                        "5d6d3be5a4b9361bc73bc763" // Id LShz aventai
                      ]
                    }
                    ]
                }
              
              }
            ]
          }
    }    

I wanted to add the LShz aventail on the vulkan 5 with the face shield. I had to see how to do it in the item.json. It worked, I see 2 slots and I can place them but I don't see the faceshield and the aventail on the helmet when I place them on the slots.
But it still physically works, I have them, it's just that I don't see them.

Yeah, that might happen. When I wanted to combine Killa's faceshield(or Rys-T, don't remember which) with Vulkan it appeared on my PMC's neck or something. But on the other hand I've successfully combined Killa/Maska faceshield with Altyn and Rys-T and it looked pretty well, so it might work well for some items.

I didn't really play around with it much but I suppose such things would have to be tweaked in the assets(bundle files) or somewhere else, but that goes beyond messing with item's properties.

Try to CTRL+A, CTRL+C from selectors_example.json and CTRL+A, CTRL+V into dynamic_selectors.json. If it doesn't work, tell me what errors does your server console show.

My brain must have fried itself seeing as it actually does work now, thanks for helping anyways though i appreciate it.

Just make sure the JSON structure is correct. If you use VSCode or some other proper editor it shouldn't be a problem, since errors will be highlighted.

The cost of an item is mostly determined by it's handbook price. The "handbook" is a different database table, this mod only works with the "items" table. So it's not possible to change the price of any item with this mod.

If no other mod editing item prices exists it's possible that I could make one some time in the future, though I don't have such plans for now.

I see, that explains why I couldn't find anything on price in the item finder. Thanks for clarifying.

You can edit any properties which scopes have in their item templates, but how will that affect them in-game needs testing, since these are only server values and some things are handled client-side. To change reticles you most likely need to change/add actual assets, this mod doesn't do that. Every items seems to have a line which you could change, like e.g.: "path": "assets/content/items/mods/scopes/scope_30mm_eotech_vudu_1_6x24.bundle",

which seems to specify a bundle path, but I don't really know how assets are handled in this game.

As far as I've checked these are some scope-specific properties that scopes have in their templates and some of them don't seem to change much. I've tested "Zooms" and "CalibrationDistances". Zooms seem to only change the values in item description, zoom itself is probably handled somewhere in the client. Calibration values seem to actually work and you can zero on newly set values, but I didn't test how precise they are.

      "CustomAimPlane": "",
      "sightModType": "optic",
      "ScopesCount": 1,
      "AimSensitivity": [
        [
          0.1,
          0.6
        ]
      ],
      "ModesCount": [
        2
      ],
      "Zooms": [
        [
          6,
          1
        ]
      ],
      "CalibrationDistances": [
        [
          50,
          100,
          150,
          200,
          250,
          300
        ]
      ]

    "scope_30mm_eotech_vudu_1_6x24": {
        "set": {
            "Zooms.0.0": 32,
            "CalibrationDistances.0": [
                50,
                100,
                150,
                200,
                250,
                300,
                350,
                400,
                450
            ]
        }
    }

Thank you for the help but I remember there was a Bug/Glitch where you could use someone's distance Spotter and it would show up in your Scope Redical as the Distance you were aiming at I wanted to try and make that as a Scope in SP Tarkove

yeah i've tried this mod to change med values but i'm not good enough to understand it and make it work, but seems like the possibilities are endless!

It certainly might look overwhelming since it's more like a tool rather than a mod where you tweak a few predefined config values. But it's also not that complicated.

Perhaps I can assist you a bit with an example in the spoiler below.

    "do_some_stuff_to_medkits": {
        "query":{
            "key": "_parent",
            "values": [
                "5448f39d4bdc2d0a728b4568"
            ]
        },
        "multiply": {
            "MaxHpResource": 2,
            "effects_damage.LightBleeding.cost": 0.3,
            "effects_damage.HeavyBleeding.cost": 0.3
        }
    }

thx for the help