Improve the Subpack System (Very Specific With Examples, Please Read)
(This explanation is intended to go alongside the image provided. It will not make sense without the image alongside.)
Minecraft Bedrock's current subpack system leaves a lot to be desired. With the screenshot you saw, most of its issues could be fixed.
This document should explain the idea behind the new system. First off:
What Does It Add?
• Multiple ways to create settings: toggle, slider, or drop down.
• The ability to change multiple settings with one resource pack.
• An easily controllable default state and tier system.
• Fully customizable folder pathing for subpacks.
Different Ways To Create Settings
These are all based on current ways to change settings in Bedrock Edition.
• "drop_down": The drop-down menu system found in places such as Camera Perspective. Most useful for lists of many different settings.
• "slider": The same as the current subpack system. Useful for scaling things, such as resolutions.
• "toggle": One option that can be enabled or disabled. Useful for enabling or disabling specific things, like beta features.
The tier assigned to each will control what order they appear. Tier 0 is on top, with higher numbers going further down. Decimals not supported.
The name can be translated by giving it a definition in lang files. Typing "pack.tier1", for example, in the manifest could allow you to translate into many other languages with the language files.
Default States and Tiers
The state an option starts with can be controlled easily by defining the default_state or default_tier for each option.
Default State is for toggles, and is either set to true or false. True means the toggle is on by default, false is the opposite.
Default Tier is for drop-downs and sliders. It should be set to the tier number of the option meant to be default.
Each option in a slider or drop-down can be given a Tier. For a drop-down, 0 is on top, with higher numbers going further down. For a slider, 0 is far left, with higher numbers going further right.
Anything not explained in this document is assumed to be self-explanatory. You will need to look at the image to see the JSON structure.
Please sign in to leave a comment.