Changes since 4.x

Introduced root flattenedProperties node to permit flattening to be represented without using remappedStates.
- This change reduces the size of many schemas by removing useless bloat. All rules that use this feature were previously using remappedStates with a null filter, which generated redundant data in many schemas.
- Unlike remappedStates, this rule does not exclude the use of other rules for a particular block ID. This means that addedProperties, removedProperties etc should still be applied for an ID even if that ID has a flattenedProperties entry. (Basically, it should be treated the same as all the others except remappedStates).
Flattening rules can now make use of TAG_Byte and TAG_Int properties as well as TAG_String.
- A new flattenedPropertyType may appear in flattening rules with value byte, int or string. If omitted, assume string.
- flattenedValueRemaps may contain a dummy map_not_list entry for numeric types. This is a workaround for PHP's handling of objects with numeric properties and should be ignored.
- See here and here for examples.
Flatten property rules may be used in more places, such as when multiple old values map to the same ID. This is the case with tallgrass. Most implementations won't need to be modified to support this.

See pmmp/PocketMine-MP@82c4166 for corresponding upgrader and schema generator changes.

Provide feedback