JasonZ617
Assigned
Reported
MC-213266
Customizing huge_red_mushroom feature crashes the game
Awaiting Response
MC-165249
Tick function summoning an invisible armorstand causes some of those armor stands to render transluscent for 1 frame
Duplicate
MC-150259
Guardians not spawning on older ocean monuments
Duplicate
MC-131837
Torch blockmodel missing "normal" variant
Duplicate
MC-131444
Prismarine bricks variants wrong names
Works As Intended
MC-126563
Monument pillars generation does not replace tall seagrass
Duplicate
MC-126467
Glowing blocks give yellowish light underwater
Fixed
MC-126466
Cant use anvils if vanilla datapack is disabled
Duplicate
MC-126394
Guardian beam not aligned!
Duplicate
MC-126155
Structure Block Floating Nameplates Not Working
Duplicate
MC-125162
Can't shoot in adventure mode
Duplicate
MC-125150
Cant use sneakTime as objective criteria
Invalid
MC-87294
EntityId tag doesnt work with /setblock for spawners!
Duplicate
MC-57581
Underwater Sea Lanterns "Yellowish" effect
Incomplete
MC-57576
Water Looks like Coal
Duplicate
Comments
It just says "Process crashed with exit code -1", no other details.
Fixed in 1.14.3 snapshots (tested on Pre2)
Did A LOT of tests updating a 1.14.0 world to 1.14.1 & 1.14.2... updated normally/optimizing/optimizing&erasing cache, etc... all of them failed and villagers lost their memory.
But i can confirm its fixed in 1.14.3 snapshots!, tested a couple of times and villagers worked normally, followed their schedule, and kept their jobs...
😃
It doesnt scroll untill you manually click&drag the scrolling bar once... Once you do that the mousewheel scrolling works.
Confirmed on 18w22a
Nevermind... I just found the workaround to that crash thing... And no, This is not an issue anymore! Clear beautiful lightning 😃
Â
I dont know... the last 3~4 snapshots crash on startup... They show the Mojang logo for 2 sec and boom...
It happens to me no matter how much memory i add to it... Just hit play on the launcher... Mojang screen shows up and crashes.
Happens to me on 18w19a-18w19b
Confirmed 18w10d
^^^ Clever!
But it is still a bug xD
Or maybe grass generating inside pillars? I dunno ._.
Thats actually normal! 😃
The monument started generating on its South-East corner (the only corner touching seafloor) and thats why the rest of the monument generated high above the lower terrain. The pillars just generate downwards until they hit the floor
Confirmed on 18w09a
This needs to be removed soon!
Yep. Still happens
Thank You, i didnt see anything about this on changelogs
Nothing about using wrong state providers or missing strings as it usually does when the code is wrong... Just "game crashed with exit code -1", no more debug or warn messages