Armand
More than one avatar was detected! There might be multiple accounts sharing this same name.
Assigned
No issues.
Reported
View all
MC-173055
You can't rename your stuff in a anvil
Awaiting Response
MC-72500
Piston physics are f*cked up
Duplicate
MC-71520
LAN worlds don't work. For every version released.
Invalid
MC-71469
Server lags and crashes WAYYY too much
Invalid
MC-69561
Grass block rendered as a transparent block with x-ray texture packs
Duplicate
MC-49978
my minecraft crasches
Incomplete
Comments
PLEASE FIX THIS SH** IF IT'S THE LAST GODDAMN THING MOJANG OR ANYONE ON THIS PLANET (Even if it was Kim Jong Un) PLEASE PLEASE PLEASE PLEASE I MEAN REALLY I CAN'T PLAY PVP BECAUSE OF THIS BULLSH**
Grass block rendered transparent with X-ray texture pack
This is not resolved.
X-Ray is still functional on 14w34d through grass blocks
On 14w34d grass block is still rendered as a transparent block. That makes x-ray completely functional.
I can reproduce this on Bedrock v1.17.40.
To reproduce:
Make a behaviour pack with entities/skeleton.json.
In "behavior.nearest_attackable_target": Edit "max_dist" for targeting the player to 35
When you get in range of 35 blocks, it will start glitching.
A similar thing happens with Zombies if you increase the "max_dist" to more than 35. They won't be glitchy but the distance seems to be capped at 35. Is this intended? Why is it not possible to increase the default "max_dist"?