Attributes in 1.16 have been renamed to use all lowercase, so e.g. generic.movementSpeed has become generic.movement_speed

Reported by Red_Bones

Description

When an advancement file is put under a directory like this: data/<namespace>/advancements/recipes/, it will be recognized as a recipe.

Diagnostic

The current extension uses following configuration to provide JSON validations:

"jsonValidation": [
    ...
    {
        "fileMatch": "data/*/advancements/*.json",
        "url": "./src/advancement.json"
    },
    ...
    {
        "fileMatch": "data/*/recipes/*.json",
        "url": "./src/recipe.json"
    },
    ...
]

The ideal solution is to use a glob pattern like data/*/advancements/**/*.json to match files. But unfortunately, the fileMatch doesn't support double asterisks (**) for recursion purposes, that said, * indicates recursions already.

I have no idea about how to fix this problem, so I just open an issue and hope someone to help me out :/

🚨 The automated release from the released branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the released branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

package.json not found. A package.json is required to release with vsce.

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the semantic-release-vsce plugin to add more helpful information.

Good luck with your project ✨

Your semantic-release bot 📦🚀

🚨 The automated release from the released branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the released branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

In Minecraft 1.15.2 damage_flags has been renamed to type. Please fix this, or at least add an option to ignore errors on a case by case basis.

{
    "condition": "minecraft:entity_properties",
    "predicate": {
        "equipment": {
            "mainhand": {
                "tag": "minecraft:logs"
            }
        }
    },
    "entity": "this"
}

Be aware the property value doesn't use the usual leading # for the tag.

As documented on https://minecraft.gamepedia.com/Advancement/JSON_format#minecraft:shot_crossbow , there is a minecraft:shot_crossbow trigger for advancements and it is not present in src/advancement.json

recipe "type": "minecraft:stonecutting" is not supported
recipe "type": "minecraft:crafting_special_*" are not supported
"item": "minecraft:honey_block" is not supported

Release notes for draft 2019-09: https://json-schema.org/draft/2019-09/release-notes.html

Schema: https://json-schema.org/draft/2019-09/schema

It should allow extensions.

The extension marks recipe types that do contain the minecraft: prefix as non valid and hints me that I should use one of the proper ones: smelting, smoking, blasting and campfire.

Strange too though, shapeless and shaped don't get hinted as well. I think something is off in the JSON schemas here.

There should be an equipment property in ./shared/predicate.json#/definitions/entity.

Currently throws a warning if you do not explicitly state "minecraft:"

https://minecraft.gamepedia.com/Recipe#minecraft:campfire_cooking

Reporter: Cjsah_