Bigger inventory: patch pages, then verify the UI

Expand inventory storage and give the interface room to show it. The author’s Bigger Inventory mod demonstrates both parts: the game’s page capacities and the UI layout that lets you reach those slots. Adjust carry weight separately if that is part of your mod.

Inspect the pages before writing a list

The native InventoryPages field is an array of structs. Each page has a SlotType and a NumSlots in the example. A copied four-element array could discard another page introduced by the game or a different mod. Instead, select the intended entries by their enum value and change only NumSlots.

Find InventoryItems by its current value rather than assuming it is always element zero. Check the class/default, inherited values, player controller’s component and the UI’s inventory-body widgets together.

Read the author's focused rules

// Selected rules from the author's installed Bigger Inventory profile.
// These four pages total 304 slots. 312 is that profile's overall capacity,
// not a total inferred from these four changes; inspect unmodified pages too.
{
  "/Game/Gameplay/Character/Components/BP_Components_Inventory": {
    "InventoryPages": {
      "$Patch": [
        {"$Match": {"SlotType": "EInventorySlotType::InventoryItems"}, "$Target": {"NumSlots": 120}},
        {"$Match": {"SlotType": "EInventorySlotType::InventoryRunes"}, "$Target": {"NumSlots": 56}},
        {"$Match": {"SlotType": "EInventorySlotType::InventoryAmmunition"}, "$Target": {"NumSlots": 56}},
        {"$Match": {"SlotType": "EInventorySlotType::InventoryQuestItems"}, "$Target": {"NumSlots": 72}}
      ]
    },
    "MaxSlotCount": 312
  },
  "/Game/Gameplay/Character/Player/BP_PlayerController": {
    "BP_Components_Inventory": {
      "InventoryPages": {
        "$Patch": [
          {"$Match": {"SlotType": "EInventorySlotType::InventoryItems"}, "$Target": {"NumSlots": 120}},
          {"$Match": {"SlotType": "EInventorySlotType::InventoryRunes"}, "$Target": {"NumSlots": 56}},
          {"$Match": {"SlotType": "EInventorySlotType::InventoryAmmunition"}, "$Target": {"NumSlots": 56}},
          {"$Match": {"SlotType": "EInventorySlotType::InventoryQuestItems"}, "$Target": {"NumSlots": 72}}
        ]
      },
      "MaxSlotCount": 312
    }
  },
  "/Game/UI/Inventory/WBP_Inventory_VerticalNavigation": {
    "InventoryBody_Items": {"RowCount": 15},
    "InventoryBody_Runes": {"RowCount": 7},
    "InventoryBody_Ammunition": {"RowCount": 7},
    "InventoryBody_QuestItems": {"RowCount": 9}
  }
}

Part	Why it exists
/Game/.../BP_Components_Inventory	Configure the inspected inventory-component defaults.
InventoryPages.$Patch	Preserve the array and edit selected existing struct entries.
$Match.SlotType	Identify the intended page semantically. Enum spelling is part of the native contract.
$Target.NumSlots	Change only that page's slot count.
MaxSlotCount	A separate overall capacity field; it is not the UI's row count.
BP_PlayerController → BP_Components_Inventory	The author's profile also applies the same page rules to this owned component path. Inspect both consumers; do not assume changing a component class alone updates every existing owner.
WBP_Inventory_VerticalNavigation → InventoryBody_*	The author's page-specific UI row counts. This does not allocate gameplay slots.

The four changed pages total 304 slots (120 + 56 + 56 + 72), while this installed profile supplies MaxSlotCount: 312. Keep those two values separate when making your preset. The snippets do not explain the remaining eight slots; inspect the unchanged pages and native capacity behavior before deciding how to account for them.

Likewise, the author's row counts correspond to an eight-column layout. If your UI uses another layout, inspect it rather than copying those row counts as universal constants. Keep any window-size/scrollbar adjustments in a separate file so you can distinguish a storage failure from a display failure.

How matching keeps the edit focused

$Match must find exactly one matching entry. A missing page or duplicated enum value causes that array patch to fail instead of silently editing a different page. Only supplied fields change; other page entries are retained. The array edit is staged before commit, not a guarantee that every other target in the file changes as one transaction. See patch operators.

Test each layer separately

1. Use a backed-up/disposable character and fully restart after enabling the mod.
2. Check Diagnostics for each class, component, SlotType and reflected field.
3. Verify the actual storage pages, not only the number of visible boxes.
4. Put disposable items in the last new slots on each page.
5. Test mouse/controller navigation, scrolling, drag/drop, sort/fill and transfers.
6. Save, quit completely, restart and verify the items and selected page again.
7. Test a second character and a matching host/client pair if you support co-op.
8. Test rollback only after removing everything from added slots.

Changing NumSlots does not change an item's stack limit or a character's carry weight. The author's separate players/00-GenericCarryCapacity.jsonc is outside this lesson; consult the players contract instead of inventing a generic Blueprint carry-weight property.

This is a readable excerpt of an author's configuration, not live certification of every new Dragonwilds build, screen size or inventory consumer. Capacity reduction can strand items; prepare the character before disabling the mod.