From e58c59071435f7900c944cb41dcedcb5b2bc7a5c Mon Sep 17 00:00:00 2001 From: Paul Fenwick Date: Wed, 26 Feb 2020 22:49:55 -0800 Subject: [PATCH] =?UTF-8?q?ammo=5Fpouch.json:=20Tac=20vests=20now=20have?= =?UTF-8?q?=20a=20max=20encumbrance=20of=205=20(was=2030)=20=F0=9F=A6=BA?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I lived in fear of using my tac-vest storage, as encumbrance 30 was much higher than anything else I wear. This change maxes the encumbrance at 5, using the rule of thumb that 1L storage = 1 encumbrance for well-designed storage. The tac-vest has a base encumbrance of 2, and 3 litres of storage. I'm not sure how the max encumbrance was showing as 30, as reading `item::get_encumber_when_containing` uses 1 encumb per 250ml, so 3L should only add 12 encumbrance, not 28. ‾\_(ツ)_/‾ Closes #34768 --- data/json/items/armor/ammo_pouch.json | 1 + 1 file changed, 1 insertion(+) diff --git a/data/json/items/armor/ammo_pouch.json b/data/json/items/armor/ammo_pouch.json index e20e75e3b3e8e..98cd5e8c5b024 100644 --- a/data/json/items/armor/ammo_pouch.json +++ b/data/json/items/armor/ammo_pouch.json @@ -537,6 +537,7 @@ "covers": [ "TORSO" ], "coverage": 20, "encumbrance": 2, + "max_encumbrance": 5, "material_thickness": 2, "storage": "3 L", "use_action": {