mojira.dev

Artem

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

No issues.

Reported

View all
MC-307085 Black screenshots when pressing F2 on Intel HD Graphics 4000 (1.21.8–26.1) Duplicate WEB-8408 Minecoins Awaiting Response MCL-26179 error 0x80070003 Invalid MC-301699 I cant see any custom skins Duplicate MC-301006 Strange fog in the end Invalid MC-300604 Unnecessary block variations in the redstone block tab Duplicate MC-300136 Held item positions are synchronized between entities of the same model in view Fixed MCPE-220271 Invisible tnt Duplicate MCPE-216940 Это не ошибка Incomplete MCPE-216921 Problem with showing classic skins Cannot Reproduce

Comments

[media: зображення-20260327-141212.png]

The problem is with the OpenGL drivers. I checked the Mesa driver and it renders Minecraft using the CPU, but this worked.

Just removed it, doesnt seem to fix anything

[media]
[media]
[media]

And block makes a mettalling clang sound when hit ,like armor plating and block have knockback effect

yes here, but in addon only pandas, because i deleted bears and made copy of them in other files, i don't want to see how others can steal my work, btw here
http://www.mediafire.com/file/802plnk97n6zu91/6k-kXnejAAA__Copybears.zipp/file just delete last "p"

Let's start with this:
When i testing my project on 1.16.20, animations for custom panda work correctly, and they using runtime identifier, bss without this they will broke other stuff in code, so with runtime identifier rolling,snacking,sneeze work perfect are bones animated even "rightItem" using this query: "query.get_euipped_item_name" , but when i testing 1.16.100+ betas custom panda broken, query.is_eating not working when panda sitting with item and even item not animated, query.get_euipped_item_name not work, special queries not works in mobs who using runtime identifier, it happen to my regular bears too "query.is_standing_scale" no longer work with runtime identifier "polarbear" . I hope now you understand what i trying to explain....

In 1.15.2 this fixed

will you fix this bug in a new snapshot?

I have the same bug

I have the same issue, but on windows 10

 

I think it's a client-side issue

I have the same issue

Load more comments