Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-123229

Vindicators hold axe in the wrong position

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • 1.17.40.20 Beta, 1.17.40
    • 1.17.11 Hotfix, 1.17.20.22 Beta, 1.17.20.20 Beta, 1.17.0.56 Beta, 1.16.230.54 Beta, 1.16.220, 1.16.230.50 Beta, 1.16.221 Hotfix, 1.17.0, 1.17.2 Hotfix, 1.17.30, 1.17.32
    • None
    • Confirmed
    • Multiple
    • 518616

      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:

      1. Apply a resource pack having "format_version": 1 in its manifest.json file. (The Classic Texture Pack from the Marketplace can be used.)
      2. Open the demo world. Get into Creative mode if you aren't.
      3. 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.

        1. B009A3C5-64E7-414E-BA96-B0DBF764C315.jpeg
          B009A3C5-64E7-414E-BA96-B0DBF764C315.jpeg
          241 kB
        2. MCPE-123229 demo.mcworld
          54 kB
        3. Minecraft 3_31_2021 9_23_07 AM.png
          Minecraft 3_31_2021 9_23_07 AM.png
          2.54 MB
        4. Screenshot_20210819-094309_Minecraft.jpg
          Screenshot_20210819-094309_Minecraft.jpg
          734 kB

            Twowolfnfs Nik
            Votes:
            13 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: