I was playing Minecraft beta and was playing around with building a custom pillager outpost. when the turn came to spawning vindicators in there section of the build I noticed a wired bug.
the pillagers were holding there axe in the wrong position and even when there arms were crossed. i have added a picture that I took in my bug report world
Steps to reproduce:
Apply a resource pack having
"format_version": 1in its manifest.json file. (The Classic Texture Pack from the Marketplace can be used.)Open the demo world. Get into Creative mode if you aren't.
Spawn a vindicator and look at it.
Expected results:
The vindicator's arms are folded and its axe is not visible.
Actual results:
The vindicator's axe is visible and held in attack position, even though its arms are folded and there is nothing for it to attack.
*Workaround by [~Auldrick]*
We have learned that this issue is triggered by activating older resource packs in a world's Resource Packs list or in Global Resources. Until the big is fixed, you can circumvent the problem as follows.
First, for any packs you obtained from a third-party source (i.e. not the Marketplace), see if an updated version is available. (Marketplace packs are updated by the game automatically, so this step doesn't apply to them.)
If that doesn't work, you need to identify which packs are causing the problem. First deactivate any resource packs in your Global Resources list. Next, for each world you want to fix, deactivate any resource packs in its Resource Packs list, then add them back one at a time, checking after each one to see whether the problem comes back. If it does, deactivate that pack and don't use it again until the bug is fixed.
After you've fixed the problem for each individual world, use the same process in Global Resources: Activate one pack at a time and check whether it triggers the bug again.
If you're a pack author or you're familiar with how packs are made, you might prefer to identify the problem packs by looking at their JSON code. Any resource pack that uses "format_version": 1 in its manifest.json (or pack_manifest.json) file will trigger this issue. You can either deactivate it or correct the problem by changing it to "format_version": 2. You also have to add "min_engine_version": [1, 16, 0] (with an appropriate version number) to the header section because format version 2 requires it, and if the filename is pack_manifest.json I think you have to rename it to manifest.json. Please note that teaching you how to do this is not the bug tracker's job: If you try this and run into troubles, please ask for help on the Minecraft Discord.
Linked issues
is duplicated by 19
Attachments
Comments 17
Resolving temporarily as Awaiting Response. Are there any additional steps to reproduce the issue? Additionally, could you please export the affected world and attach it to this ticket? If it exceeds the file size limit you can upload it elsewhere and link it here.
To clarify, the "Resolved" status does not mean that the bug was fixed, it refers to the ticket. The ticket is like a folder while the bug is like information in the folder.
@unknown: You've been, and continue to be, argumentative and disruptive on this and numerous other bug reports. I've tried to get you to stop but you ignore me. I've tried to direct you to read and follow the guidelines but you clearly can't be bothered. I've tried to get you to talk to us about how the bug tracker works on the Mojira Discord but you think you know everything already. I've tried to explain to you what I can figure out about your problems but you insist that you know more than I do. You are arrogant and demanding and we cannot work with you. I will continue removing your comments that conflict with the guidelines and I've requested that your account be disabled. If you decide to make a new account, please read the guidelines before using it or we will just be doing this again later.
Re-resolving this ticket as Awaiting Response pending a response from the bug reporter, as requested by Weronika above. This ticket will automatically reopen if a reply is received.
Even with compatibility for legacy versions, it wouldn't make sense for someone to use an older version of Bedrock... unless they've got a backup/pirate copy.
Why not just force everyone to update their manifest.json format? It's not that complicated...
@unknown: This isn't the place for a discussion about how Mojang should fix it; that's their decision exclusively. But I can tell you that supporting an old format version isn't about letting people play an old version of the game, it's about letting them use an old add-on in a newer version of the game. And forcing content creators, some of whom have dozens of products, to update all their manifests at the same time (which, btw, doesn't mean just changing that version number; they'd have to review the whole design of the add-on) would put an unreasonable burden on them and possibly threaten their income stream. That would be ver bad, for them and for Mojang..
Please be patient. Like all changes to the game, bug fixes are applied to the Beta first and propagate to the official release after Beta testing. As you can see in the report heading, this issue has been fixed in Beta 1.17.40. It is therefore not expected that the fix would be in the 1.17.32 official release. You can expect it to be in the first 1.17.40 release, assuming testing doesn't find any problem with it. Until then, the work has already been done so there's no point in continuing to update this report.
No date for the official release can be given at this time.
i have no resource packs on btw so its completely vanilla JSON and resource files