-
Notifications
You must be signed in to change notification settings - Fork 30
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Minor changes to texture definition RegExp, & added "FANCY" material …
…enum (#290) * Implement some missing `ui/` schemas - Add `allow_debug_missing_texture` - Add `propagate_alpha` - Add `use_child_anchors` * Tweak descriptions of `item_ref` It should be noted that UI are referred to as "elements." Moreover, the examples used colon (`:`) instead of dots (`.`) which contradicts the given description. * Add more enum values to the `easing` property These are all known values, aside from the five that was given. * Update damage_source.json The list of damage sources have been updated and added new possible damage sources. Damage source `attack` has been deprecated going forward and has been split into two, namely: `entity_attack` and `entity_explosion`. Damage source `fatal` has also been deprecated in newer format/`min_engine` versions, and has caused content log errors upon testing. But will remain for backwards compatibility. This commit aims to resolve #185. Please refer to the damage sensor documentation here: https://github.com/MicrosoftDocs/minecraft-creator/blob/main/creator/Reference/Content/EntityReference/Examples/EntityComponents/minecraftComponent_damage_sensor.md * Define `pack_scope` and `product_type` fields for pack manifests With the release of Add-Ons in the marketplace, these property fields have become present in pack manifests. * Tweak RegExp for defining texture names - It will now match for a colon text (`:`) whereby namespaces are defined with - Fix completely off-the-mark RegExp for `item_texture.json` and `terrain_texture.json` files. * Add `FANCY` material enum * Merge branch
- Loading branch information
ライゼン1920
authored
May 28, 2024
1 parent
3476c4c
commit 38ea808
Showing
5 changed files
with
16 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters