Data Driven Stack Sizes 0.10.7-1.21.4

Changelog

Features

New TAG: Max_Stack_Size_0

Datapack now includes item tag Max_Stack_Size_0. Unlike other max_stack_size, where overloaded stacks maintain their current count: MSS_0 reduces tagged item's stack counts to 0 automatically.

USE OF THIS FEATURE CAN, WILL, AND IS INTENDED TO RESULT IN PERMANENT LOSS OF ITEMS!!!

Any item tagged with max_stack_size_0 will be automatically emptied any-time their max_stack_size is checked. Which happens, when a stack is validated, moved, used, saved, or looked at funny. You will not see them disappear: They will simply be gone

USE OF THIS FEATURE CAN, WILL, AND IS INTENDED TO RESULT IN PERMANENT LOSS OF ITEMS!!!

This behavior can be bypassed using the previously established DDS-ignore: DDS will intentionally ignores any item which a non-empty custom_data component. That option has been reproduced here.

USE OF THIS FEATURE CAN, WILL, AND IS INTENDED TO RESULT IN PERMANENT LOSS OF ITEMS!!!

Known Issues

Forbidden Give Commands are Too Generous

Using the /give command to give X of any item tagged max_stack_size_0 gives the target a stack of that item with a count of 1 when it should give 0. These forbidden stacks do near immediately disappear, but their very existence is a bug of low priority.

Files

datastacks-0.10.7-1.21.4.jar(950.1 KiB) Primary Download

Project members

Hydraheadhunter

Member

Details

Licensed CC-BY-NC-SA-4.0
Published a year ago
Updated 6 months ago