Change Rust Stack Size Controller without losing inventory

Stack Size Controller changes how many items fit in a stack. It does not add storage slots or guarantee compatibility with every container plugin. Trial one ordinary resource before applying large limits across a live server.

Protect existing inventories

Record the plugin version and retain its current configuration. Make a consistent backup of the active world, player state and related inventory-plugin data before changing stack behaviour. Save a second copy outside the live server. Choose a quiet test window, tell administrators what will change and avoid using valuable player items for experiments.

Count the test items and record where they are stored. Use a test container with spare slots and a normal player account. Keep special items, modified weapons and containers with custom rules out of the initial trial.

Edit the current configuration format

The author identifies IndividualItemStackSize in the configuration as the place for individual item sizes. Do not follow old advice to edit a vanilla-defaults data file. Check the installed version's generated configuration and current author instructions before changing a field.

Individual and category multipliers can affect the final result. The documented calculation uses the configured individual stack size as the base, not necessarily Rust's vanilla size, and individual multipliers take precedence over category multipliers. Record every applicable field for your chosen test item so an unexpected size can be traced.

Apply one bounded change

Copy the configuration to a local JSON-aware editor.
Change one non-critical resource to a modest limit suitable for your rules.
Validate the JSON locally and upload it to its original path.
Use the author's documented o.reload StackSizeController command from the server console.
Read the reload result before moving any items.

Do not jump to extreme integer limits. A configuration accepted by the plugin can still produce awkward inventory behaviour or conflict with another plugin. A larger stack does not increase the number of slots available to the container.

Test movement and persistence

Merge and split the test resource, move it between inventory and the test container, and compare the total quantity before and after. Reconnect the player and check again. In a planned maintenance window, verify persistence across a normal save and restart. Watch for errors from backpack, furnace or other storage integrations.

If only one container differs, investigate that container's plugin rules before changing the global stack setting. Keep a record of which actions work and which fail; “stacking is broken” does not identify the affected path.

Plan the downward change

Reducing a limit may leave existing stacks larger than the new value. Before rollback, provide sufficient empty slots and test how the installed plugins handle those stacks. Do not assume they will split safely by themselves. Restore the original configuration if necessary and ask support for a controlled conversion plan rather than deleting items.