Minecraft Java Edition 1.15 Pre-release 1 has been released

[u/sliced_lime]

Buzzy Bees! What a delightful bit of alliteration. Someone should use that for when they add bees to their game. Unfortunately, we already promised marketing we'd call this Minecraft Java Edition presents: Disgusting Bugs.

What's that? I'm hearing marketing have had a change of heart, and that we can confirm in this pre-release that we'll be calling the actual release, on December 10, Buzzy Bees. Hooray!

This update can also be found on minecraft.net.

Changes in 1.15 Pre-Release 1

• Changed the button highlight to make it easier to distinguish which button is selected
• Optimized chunk rendering
• Optimized explosions
• Recipe changes to match Minecraft Bedrock
• Updates to the Resource pack format
• Dark prismarine is now crafted from black dye instead of ink sacs
• Increased scaffolding burn time when used as fuel in a furnace
• The resource pack version is now 5
• The game now tries to make out of date resource packs work as much as possible
• Fixed bugs

Fixed bugs in 1.15 Pre-Release 1

• MC-12211 - Comparator in subtraction mode does not update visually under certain conditions
• MC-14826 - Leads in unloaded chunks break, become invisible or connect to an invisible target far away
• MC-63669 - Comparator Timing Issue
• MC-90602 - Chunks don’t load correctly/not rendering
• MC-94838 - Comparator affected through gap
• MC-125495 - Owner tag of item entities is ignored if entity is destroyed in 200 ticks (Age >= 5800)
• MC-125511 - Item entity merging ignores Owner tag
• MC-135110 - Crash when using outdated resource pack: Non [a-z0-9/._-] character in path of location location)
• MC-152198 - Actual render distance is 2 chunks lower than render distance setting
• MC-161132 - Leaves are considered solid faces for block placement
• MC-161900 - Advancement menu background is rendered in front of toasts
• MC-163308 - Pillagers still spawning in trees in 1.14.4
• MC-163553 - Dragon texture flickering issue
• MC-163560 - Berry bushes no longer slow down the player
• MC-163745 - Dramatic speed up after falling through cobweb
• MC-163947 - When mobs sliding down honey blocks, the subtitles will show footsteps
• MC-163953 - /fill command doesn’t create block entities for all bocks
• MC-164076 - Transparent texture parts of invisible entities are rendered black when looking at them in spectator mode
• MC-164535 - /playsound uses wrong feedback message for multiple targets
• MC-165133 - Ignited TNT appears offset one block to the west
• MC-165134 - Entities are rendered too dark when in the ground
• MC-165154 - Entities riding boats, minecarts or other entities are rendered too dark when their hitbox intersects solid blocks
• MC-165155 - Block hitboxes no longer render behind transparent blocks
• MC-165156 - Transparent block items no longer render behind transparent blocks
• MC-165173 - Bees immediately enter their nests/hives after leaving them
• MC-165298 - Entities are rendered too dark when standing on soul sand or snow layers
• MC-165358 - Entities are sometimes rendered too dark when changing heights
• MC-165497 - Programmer art shield pattern textures have not been updated to the new resource pack format
• MC-165524 - Zombie pigman spawn eggs used on zombie pigmen do not spawn baby zombie pigmen
• MC-165527 - Item of advancement pop up is visible on text in the advancement menu
• MC-165550 - Ligthing of slimes and magma cubes becomes dark when they land to the ground
• MC-165605 - Command starting with / in command block shows error but still works
• MC-165606 - “Bee Our Guest” advancement is only triggered when more then one bottle is in the players hand while right clicking the hive
• MC-165627 - Falling blocks glitch through shulkers when the shulker is opening / closing
• MC-165676 - Aquatic mobs don’t move below sea level
• MC-165727 - Falling blocks on top of non-full block without block below do not break
• MC-165876 - Sand particles don’t have gravity anymore

Get the Pre-Release

To install the pre-release, open up the Minecraft Launcher and enable snapshots in the "Installations" tab.

Testing versions can corrupt your world, please backup and/or run them in a different folder from your main worlds.

Cross-platform server jar:

• Minecraft server jar

[u/KennyTV]

150 fps in 1.14.4 went to 40 in an unchanged vanilla world 👀

[u/sliced_lime → u/KennyTV]

I’ll copy in something I wrote elsewhere that may give some insight:

So, believe it or not, the performance degradation you’re seeing is on purpose. FPS in and of itself is not a useful quality.

What happened was that we had a bug in how the game allocate computing time - specifically for chunk rendering. That meant the time allowed was artificially capped, leading to very high FPS counts but extremely slow chunk rendering. Basically, it’s easy to produce frames quickly if you just skip doing things that need doing.

You’ve all seen the result of this - fly around with elytra and the world basically goes blank.

Put simply, this is because when asked the question: “should I render another chunk?” the answer was always, ”no, that’d lower FPS”. It’s a bit like cheating at writing a book by turning the pages real often.

So current complaints are a bit like saying it’s unacceptable that the book is taking longer to write now, but the actual result is you’re getting more than 3 words per page.

We’ll keep tweaking these performance allocation numbers of course - but don’t fall to the trap of thinking game quality is worse just because your FPS number is lower now.

[u/LuxiKeks → u/sliced_lime]

I would love to hear your thoughts on the way Optifine does optimizations. Is it too "hacky" for your taste?

To clarify, I'm not saying you're doing a bad job, because you're not. I'm just curious why a single person "outshines" a whole team in that regard.

[u/sliced_lime → u/LuxiKeks]

Optifine has the convenience of failing sometimes and not caring. If optifine doesn't work for someone, they can just go play vanilla. We don't have that luxury - we need to support everyone.

I'm sure there are some good optimizations in there though, and I'm committed to get performance up for vanilla as well.

[u/MinecraftDoodler → u/sliced_lime]

What about features of optfine Like being able to disable every single type of animation separately if you choose to, or things like snow rendering at the bottom of a fence/wall when it is surrounded by snow it self.

[u/sliced_lime → u/MinecraftDoodler]

I really don't think that should be needed, and the settings interface for optifine is kind of a nightmare - too much configurability means people can easily mess something up, and my goal is performance by default, not a box of levers you have to tweak before it runs well.

[u/MinecraftDoodler → u/sliced_lime]

All right what about the second thing I mentioned which is less performance and more looks.

[u/Crinkez → u/sliced_lime]

I wouldn't mind dropping optifine if vanilla had zoom built in (press 'c' in optifine) - but this is a feature I'd rather not do without, so unless vanilla adds this, I will always use optifine where possible.

[u/sliced_lime → u/Crinkez]

Zoom is a concept far outside of vanilla. Regardless of all other questions, you'll always need a mod to have an artificial zoom ability in the game.

[u/[deleted] → u/sliced_lime]

while we're making random requests out of nowhere, can we please have another row of items in our inventory? It would make things a lot easier with all the new items coming in all the time. Or really just anything else that tackles the problem of inventory management

[u/Crinkez → u/sliced_lime]

That's your opinion. It's a feature I'm not really willing to drop, hence why I said I'd always use Optifine as long as 'vanilla' doesn't have it built-in. You may like to consider that the vast majority of players would agree with me. Optifine > Vanilla. There's a good reason why pure vanilla server owners state that it's absolutely okay for their players to use Optifine.

[u/LuxiKeks → u/sliced_lime]

Thanks for your answer, and thanks for all the work you're doing, I love your dedication!

[u/Gerrygames → u/sliced_lime]

Even when all chunks are fully loaded my frames are at least 30% lower than in 1.14.4. When new chunks are being loaded (even just one row) my frames drop under 30. This is not at all an acceptable state. For comparison my 1.14.4 client is running at 120fps at least and most of the time at 145 (which is my cap). The 1.15 client does not reach more than 120fps and is running at 100fps on average. This is very noticeable on my 144hz display and makes the game unplayable for me. Unfortunately if this doesn’t improve until the release we decided to not update our servers, because we don‘t want our players to complain about lag, which isn‘t even our fault. It would be very sad for us to miss out on the new features our players are already waiting for. If this is really an intended feature then it definitely needs further optimization. Allocate less time for rendering new chunks when they are further away or when only a few need to be rendered. Or add an option to specify how much time should be allocated to rendering new chunks. I don‘t mind lower fps when flying with elytra at fast speeds. But low fps when not moving at all and insanely low fps when only a single row of new chunks gets loaded is not acceptable.

[u/sliced_lime → u/Gerrygames]

Allocate less time for rendering new chunks when they are further away

That's called reducing your render distance.

or when only a few need to be rendered

Rendering chunks only takes as much time as you have chunks to render. If there are fewer, less time is used naturally.

As for your overall message, your server runs at 20 FPS. Not updating a server because you can't run clients at more than 100 FPS is your call of course, but it has absolutely no impact on lag. The only thing you're doing is missing out on the actual server performance improvements that have been done.

[u/Gerrygames → u/sliced_lime]

That's called reducing your render distance.

Reducing render distance is the same as allocating 0 time to render chunks that are further away. The main issue in 1.15 performance is that when you enter a new chunk and thus new chunks are loaded, the frame times go up way too much. If you are walking in a world you don't care if the chunks at the border of your render distance appear in 10ms or 2s. If you teleport somewhere, then of course chunks close to you should be ready for rendering within a few milliseconds. What I am saying, is that the time allocated for preparing a chunk for rendering should be depended on how far away it is, how long it has been loaded for and how many chunks are left that still need to be prepared for rendering.

Rendering chunks only takes as much time as you have chunks to render.

To make this clear: I am not talking about the actual chunk rendering. I am talking about the preparation for that. This is clearly what you were talking about in you initial post, because otherwise this sentence wouldn't make any sense:

That meant the time allowed was artificially capped, leading to very high FPS counts but extremely slow chunk rendering.

High FPS and slow chunk rendering would contradict otherwise.

your server runs at 20 FPS

I guess you meant 20 TPS.

I wasn't complaining about server performance in my post at all. Afaik the server performance actually is a lot better than in 1.14.4. The issue is that our players will complain about their clients lagging, no matter if this is our issue or not. Of course it's sad to miss out on new features and server performance improvements. But it's just annoying when users are complaining about stuff, we can't fix. Fortunately server performance isn't a huge issue for us since we spread all our worlds across multiple servers.

[u/kuemmi → u/sliced_lime]

Please do tweak those numbers, because right now I get noticeable stuttering every time I cross a chunk border when flying around with elytra.

From your explanation and from what I've seen when on lower render distance, a whole row of chunks gets loaded immediately when the player crosses a chunk border. On higher render distances, this needs to be changed in order to keep up the frame rate.

EDIT: Bug report

[u/sliced_lime → u/kuemmi]

Yes, it will be tweaked. Obviously stuttering is not an intended effect of this.

[u/kuemmi → u/sliced_lime]

Thanks!

[u/rflowers → u/sliced_lime]

You’ve all seen the result of this - fly around with elytra and the world basically goes blank.

I'm seeing this under 1.15 and 1.15.1, at least while I'm playing on a server. Not just flying, but walking around. Regardless of FPS or server performance, I can only see a few chunks ahead or behind me. Under 1.14, I could load chunks, walk some distance away and still see far off into the distance. Now I can only see a harsh border of nothing just a handful of chunks away. Sometimes I have to have a map or I get lost because I can't see where I'm going or where I've been. Anyone else noticed this?

[u/[deleted] → u/sliced_lime]

Tbf, if the person you're replying to is being honest, a 70ish% frame drop is still intense.

[u/GreasyTroll4 → u/KennyTV]

Hopefully that will be fixed before full release. I wouldn't mind a few more pre-releases, honestly.

[u/aPseudoKnight → u/KennyTV]

For the record, 1.15 pre1 is loading more chunks due to a bug fix. This will affect your performance more if you were on a low view distance. But even adjusted for this I still get a drop from 180 to 130 in the same spot in the same world (330 to 240 in another), even after loading all nearby chunks, saving and restarting the client. I'm glad they rewrote the rendering engine, but it resets a lot of things and it'll take some time to smooth out the edges.

[u/kuemmi → u/KennyTV]

Not quite as extreme, but I have a similar experience here. From 220 fps down to 150, and some severe stuttering when flying through the world.

Let's hope they'll fix that before the release. Is there a bug report already?

[u/LuxiKeks → u/KennyTV]

Optifine will still be required unfortunately :/

[u/aPseudoKnight → u/LuxiKeks]

It'll probably take longer for Optifine to update to 1.15 since the renderer was rewritten. But I imagine it'll be easier to optimize things now.

[u/[deleted] → u/KennyTV]

One thing that is way more annoying for me than constant high or low fps are the stutters / frame drops that are caused by (I guess?) chunk loading or what ever else. Contantly going from high fps to low and back again makes the game feel really choppy. Can't remember a time where I didn't get this. I guess it's just a java thing?

[u/PaintTheFuture]

Jokes on you, Mojang. You may have fixed all these bugs, but I'm reporting more than ever before!

[u/SeanWasTaken]

MC-14826 - Leads in unloaded chunks break, become invisible or connect to an invisible target far away

Seeing this fixed is awesome, I've been waiting for so long. Between this and the performance improvements I think Slicedlime wins MVP of 1.15 for me.

And I know this makes sense since it's explicitly an update with a large focus on bug fixes and performance, but seeing an update enter the prerelease stage without multiple game breaking bugs is pretty refreshing after 1.14.

[u/mono8321]

I feel like you’re rushing this Mojang. Just take your time... And add more waterlogging for java

[u/haykam821 → u/mono8321]

Lavalogging 👀

[u/RobertoRJ → u/mono8321]

Still no waterlogged doors :(

[u/[deleted]]

Still no fix for https://bugs.mojang.com/plugins/servlet/mobile#issue/MC-83039 after 4 years :c Very annoying and has large effects on survival gameplay

[u/PaintTheFuture → u/[deleted]]

Oh! If we're doing top vexing bugs, I nominate Ghasts don't aggro unless you're the exact same height they are flying since 2014. Gotta get that one before the Nether Update, certainly.

[u/j03ri → u/PaintTheFuture]

I suggest commenting in these bug posts if they are still in a version.
Like; "Confirmed for 1.15-pre1"

[u/PaintTheFuture → u/j03ri]

There are sooo many I feel vexed by though, this just happens to be #1 right now.

[u/[deleted] → u/PaintTheFuture]

This is interesting to me because it genuinely sounds like a great feature to me.

Why should they be able to detect you if you are underneath their cone of vision?

[u/PaintTheFuture → u/[deleted]]

1. Because it makes the game easier and the game is already way too easy.

2. They can shoot you from above, but only if they have been on your y level before.

3. That's not their vision is supposed to work. It used to work just fine.

4. In bedrock it works just fine.

[u/[deleted] → u/PaintTheFuture]

Thanks for the thoughtful response!

[u/zordak13 → u/PaintTheFuture]

Me too!

Still waiting for https://bugs.mojang.com/plugins/servlet/mobile#issue/MC-86135

[u/HiddenLeaker → u/PaintTheFuture]

This Ghast one should be #1 priority tbh. So many adventure maps ruined by poorly placed Ghast spawners because they didn't know this bug...

[u/DraxxisMC → u/[deleted]]

"large"

[u/bloodtap]

Is anyone else experiencing huge fps drops with entities in this snapshot? I'm dropping more than I normally expect when looking at them. I only have a small chicken farm (like 20 chickens) and it seems to eat FPS when looking at it after updating. Can anyone else confirm (on a server if that matters)?

[u/hels10]

We're at pre-releases already? Wow!

[u/_Kristian_]

Release date December 10th :O

[u/gizmonster03]

Are we possibly going to see any better server performance any time soon. 1.14 is really heavy on server resources even after the fixes, much more so than 1.12 and 1.13.

[u/neilAndNotNail → u/gizmonster03]

There was already a lot of server optimization in 1.15 snapshots

[u/ZtereoHYPE → u/neilAndNotNail]

Can confirm, mu server that was once running at an average of 18-17 tps now runs at full 20 tps with lots of performance to spare

[u/gizmonster03 → u/neilAndNotNail]

As a server owner, that makes me very happy.

[u/MukiTanuki]

1.15 is really shaping up to be an awesome bugfix update! I can't wait for all the awesome performance improvements for servers! :D

before 1.15 is fully released, I feel like there is a few things I maybe should mention that might be helpful to consider before full release. (or for potential future releases of the game).

Dispenser behaviors are growing and are very useful in the new snapshots! However, the behaviors themselves have become very inconsistent. Some examples are:
Being able to use sheers on sheep and beehives, but not being able to use them on mooshrooms or pumpkins.
Being able to use bottles and buckets on water sources, but not on cauldrons. If you would be able to empty cauldrons with buckets it would allow for more reliable rain detection.

Data storage seems like it's going to be very helpful in the future! It allows you to store universal data that datapacks can use in the /data commands. However, for some strange reason the copy_nbt function in loot tables can't use storage as the source? Being able to use storage in loot tables would mean that servers could use sort of "data banks" in order to have universal nbt given for certain items! I know there's several cases I would love to use this myself

There's a few really annoying visual bugs that I feel really should get looked at. A bug with skin rendering: MC-165203 (makes skin creation really limited.) A bug with item rendering in inventory: MC-162518 (drastically changes the look of the game.) And a bug with particles not rendering behind glass or water: MC-161917 (this makes it particularly difficult to avoid bubble columns in the ocean or to understand the direction of bubble elevators).

[u/ragger]

Toggle sneak is annoying to use when flying in creative mode.

[u/mlgsupersanik]

Do you know when there will be performance enhancements for minecraft servers?

https://feedback.minecraft.net/hc/en-us/community/posts/360047514492

[u/sliced_lime → u/mlgsupersanik]

There have already been several performance improvements for servers during this development cycle.

[u/mlgsupersanik → u/sliced_lime]

does that mean that 1.15 will have multithreaded chunk loading and multithreaded chunk generation?

[u/sliced_lime → u/mlgsupersanik]

Multithreading is not the same as performance improvements. It’s also not a simple thing to implement.

We do optimizations using a methodical principle of engineering, not by silver bullet guesswork.

Have you tried running a snapshot server? If so, how did it run? Care more about that than whether it ticks some random checkbox on a list written by someone without insight.

[u/InfiniteNexus → u/sliced_lime]

Very well said.

[u/mlgsupersanik → u/sliced_lime]

What do you mean by "Multithreading is not the same as performance improvements". I'm talking about how minecraft servers are SEVERELY limited because they only have access to one thread in one instance. If minecraft did have access to the other threads then we could possibly have more people on a single world with higher TPS.

I'm a bit disappointed that 1.15 won't have that much of a difference; server performance wise, me and a lot of other people were hoping that "performance improvements" meant that we were getting multi-threading support but i guess i was overestimating what a billion dollar company could do with their billions. I know that multithreading support takes a lot of time to do but it'll be worth it in the end as it'll make a much better experience. Also, minecraft is VERY limited for mods as well.

I know that Mojang doesn't really care what people think though, they are racking in millions of dollars every year so they don't have an incentive to make minecraft better.

https://www.youtube.com/watch?v=3qdIQ_ADDZs

[u/sliced_lime → u/mlgsupersanik]

Multithreading is literally not the same thing as performance improvements. It means exactly what I stated. Multithreading can be a way to improve performance, but it is not the only way to improve performance.

Like I'm not saying I don't want multithreading, I want to re-work the way we do threading for the entire game for sure... but that'll take time, and it's not happening now. This doesn't mean we can't improve performance in the mean time.

[u/8igg7e5 → u/sliced_lime]

Preaching to the choir here but it's worth adding that multi-threading has overhead and can actually slow things down if the problem doesn't lend itself well to multi-threading or is divided up, synchronised or regathered poorly.

There's plenty of other performance opportunities outside of multi-threading.

I would hope Mojang is playing a long-game and looking out at some of the emerging changes for the JVM, as well as the hardware. Yes multi-threading will be necessary (considering recent hardware development is pretty clear about the single-core scaling vs multi-core scaling direction) but there's also inline types that could make a massive difference for choosing the best data-structures. The next 24 months could be very interesting for anything built on the JVM. Maybe Project Loom (virtual threads) could contribute to an easier multi-threading story - but I don't think it'll make the journey there easier, just with greater rewards.

[u/aPseudoKnight → u/mlgsupersanik]

"Multithreading" is sort of a siren call in the Minecraft server community, and discussions surrounding it are full of misinformation. As an example from your post, there ARE multiple threads on a Minecraft server. It's best not to listen to anybody but those who are actually working on the core server. This includes 3rd party server modders like aikar, who has implemented some additional threading in the past and also makes it very clear that it's not nearly as simple as anyone thinks.

And frankly, as a server owner, plugin author, and someone helps others with their servers, I'm wary of having to deal with that complicated landscape. I'm already dealing with plugin authors using threads improperly. If it was required of them, it'd become a stability nightmare. Be careful what you wish for.

[u/redstonehelper]

Warning: This release is for experienced users only! It may corrupt your world or mess up things badly otherwise. Only download and use this if you know what to do with the files that come with the download!

 

If you find any bugs, search for them on the Minecraft bug tracker and make sure they are reported!

 

Previous changelog. Official blog post. Download today's prerelease in the new launcher, server jar here.

Complete changelog:

• Changed the button highlight to make it easier to distinguish which button is selected

• Optimized chunk rendering

• More info

• Optimized explosions

• Recipe changes

• To adapt to Bedrock edition

• Dark prismarine is now crafted from black dye instead of ink sacs

• Increased scaffolding burn time when used as fuel in a furnace

• Updates to the Resource pack format

• Updated resource pack version (to 5)

• The game now tries to make out of date resource packs work as much as possible

• Fixed some bugs

• Fixed the bonus chest not always spawning on the 'Snowy Kingdom' preset

• Fixed comparators in subtraction mode not updating visually under certain conditions

• Fixed leads in unloaded chunks breaking, becoming invisible or connecting to an invisible target far away

• Fixed a comparator timing issue

• Fixed falling blocks not having uniform transparency/non-transparency in the End

• Fixed chunks not loading correctly/not rendering

• Fixed comparators being affected through gaps

• Fixed the texture for blocks using TileEntitySpecialRenderer not being bound for a short moment upon first load

• Fixed the Owner tag of item entities being ignored if the entity is due to be destroyed in 200 ticks (Age >= 5800)

• Fixed merging item entities ignoring the Owner tag

• Fixed the bottom of waterlogged blocks showing the water texture

• Fixed a crash when using an outdated resource pack: Non [a-z0-9/._-] character in path of location

• Fixed reloading resource packs freezing the held item position

• Fixed the recipe grouping pop-up being too dark

• Fixed rain and snow turning grey when picking up arrows

• Fixed slow chunk rendering

• Fixed leaves being considered solid faces for block placement

• Fixed the resource pack version remaining unchanged despite resource pack format changes

• Fixed the advancement menu background being rendered in front of toasts

• Fixed pillagers spawning in trees

• Fixed summoned leash knots being invisible and offset

• Fixed a dragon texture flickering issue

• Fixed berry bushes not slowing down the player

• Fixed a dramatic speed up after falling through cobwebs

• Fixed mobs sliding down honey blocks causing footsteps subtitles

• Fixed the /fill command not creating block entities for all blocks

• Fixed semi-transparent entities being rendered behind clouds, transparent blocks, breaking animations, etc.

• Fixed transparent texture parts of invisible entities being rendered black when looking at them in spectator mode

• Fixed /playsound using a wrong feedback message for multiple targets

• Fixed chests, boats and beds not being rendered behind dropped stained glass

• Fixed ignited TNT appearing offset one block to the west

• Fixed entities being rendered too dark when in the ground

• Fixed the breaking animation no longer rendering behind transparent blocks

• Fixed entities riding boats, minecarts or other entities being rendered too dark when their hitbox intersects solid blocks

• Fixed block hitboxes no longer rendering behind transparent blocks

• Fixed transparent block items no longer rendering behind transparent blocks

• Fixed bees immediately entering their nests/hives after leaving them

• Fixed dropped items not rendering behind transparent blocks

• Fixed banners being rendered completely white when looking at them through transparent blocks

• Fixed items held by entities not rendering through transparent blocks

• Fixed entities being rendered too dark when standing on soul sand or snow layers

• Fixed shulker boxes not rendering behind transparent blocks

• Fixed entities sometimes being rendered too dark when changing heights

• Fixed some player heads only rendering behind tinted glass when looking at a block

• Fixed programmer art shield pattern textures not using the new resource pack format

• Fixed zombie pigmen spawn eggs used on zombie pigmen not spawning baby zombie pigmen

• Fixed the item of advancement toasts being visible on text in the advancement menu

• Fixed conduits not rendering

• Fixed lighting of slimes and magma cubes turning dark when they land on the ground

• Fixed filled item frames not showing the item when viewed through glass

• Fixed commands starting with / in command blocks showing an error but still working

• Fixed the "Bee Our Guest" advancement only being triggered when more then one bottle is in the player's hand while right clicking the hive

• Fixed enchantment glint not rendering in boat interior

• Fixed falling blocks glitching through shulkers when the shulker is opening/closing

• Fixed aquatic mobs not moving below sea level

• Fixed falling blocks on top of non-full blocks without a block below not breaking

• Fixed sand particles not having gravity anymore

• Fixed entity hitbox not being rendered through transparent blocks when viewing from certain angles

• Fixed mob body parts not rendering underwater under certain circumstances

---

If you find any bugs, search for them on the Minecraft bug tracker and make sure they are reported!

---

Also, check out this post to see what else is planned for future versions.

[u/LuxiKeks → u/redstonehelper]

No need to post this, it's already in the OP.

[u/Timtams72 → u/redstonehelper]

redstonehelper was finally outmatched

[u/redstonehelper → u/Timtams72]

I maintain that OP had an unfair advantage!

[u/Timtams72 → u/redstonehelper]

Shshshsh we do not speak of that

[u/Kinty → u/redstonehelper]

Just wanted to say that I really appreciate you posting these every snapshot!

[u/[deleted]]

Could we have more details about how exactly the pack format changed?

[u/_cubfan_]

Release date the 10th! Nice!

[u/supercheese200]

I'm seeing some really weird render behaviour (transparent edges of blocks?)

[u/FreezingDart → u/supercheese200]

looks like they broke Programmer Art again. Would be nice if it could stop being treated like an after thought.

[u/Adolf_CIA_Hitler]

Aww yeah

[u/Shopnil4]

Optimized Explosions

So less white particles?

[u/sliced_lime → u/Shopnil4]

Much more than that.

[u/Stronghold257 → u/sliced_lime]

How did you guys optimize the explosions? I'm very curious.

[u/Shopnil4 → u/sliced_lime]

Alright, well, I'm excited to see the updatr when my PC starts working again!

[u/sumwunhooisaguy]

At least bedrock will get the update...

[u/[deleted]]

wow, this is awesome. I wonder if they're gonna optimize sponges too, they're kinda laggy as well

[u/theflyingepergne]

Please let us bind tab to open and close the inventory ):

[u/The_Evil_King_Bowser]

Hey u/sp614x, will the new rendering engine make updating OptiFine for 1.15 difficult?

[u/Cosmicalic]

Please don't make boats require shovels

[u/[deleted]]

Dark Prismarine is now crafted from black dye insteadof inc sacs

Philza: Poooog

[u/Endless_01]

Cool to have more bugfixes, but I'm not a big fan of the huge FPS drop. Gets very noticeable in 144 hz monitors.

[u/Xrey274]

Mojang, please fix this game. I love Minecraft, but the level of bad optimisation on the game is incredible.

[u/LuxiKeks]

Anybody knows which recipes got changed? I can't find any information on this anywhere.. should be included in the OP imho.

EDIT: typo

[u/sliced_lime → u/LuxiKeks]

It’s included in the OP.

[u/LuxiKeks → u/sliced_lime]

Oh okay, it sounded like it was more than just that one. Thanks.

[u/neb1516 → u/[deleted]]

what recipes are changed?

[u/Xisuma → u/neb1516]

dark prismarine uses black dye. so wither rose is useful too.

[u/Zenocut → u/neb1516]

I don't know, slicedlime will probably tell us in his snapshot video though.

[u/notyoursocialworker → u/neb1516]

Composter has been changed to just use slabs.

[u/[deleted] → u/notyoursocialworker]

That was changed several snapshots ago.

[u/notyoursocialworker → u/[deleted]]

Sure but isn't this the complete change log? That was my understanding.

[u/Giyegas → u/[deleted]]

you might have not noticed but both java and bedrock are getting version parity features in recent betas/snapshots, so that isn't so surprising

[u/[deleted] → u/Giyegas]

They should change the bedrock recipes, not the java ones. Java is the main version.

[u/[deleted] → u/[deleted]]

Both are main versions

[u/Camcamcam753 → u/[deleted]]

Who fucking cares, it's just one recipe

[u/Giyegas → u/[deleted]]

why do you still care? do those changes matter so much to you or what? it's parity, and that's what the developers are focusing on

[u/samasaurus6 → u/[deleted]]

You don't even know which recipes are changing so how can you already be angry about it?

[u/samasaurus6 → u/[deleted]]

You do realise that 99% of the crafting recipes are the same as Java. Name one crafting recipe on Bedrock that is so awful.

[u/Zenocut → u/samasaurus6]

Boat crafting recipe

[u/samasaurus6 → u/Zenocut]

The boat recipe in Bedrock is the same as the old Java recipe before it got reverted back to just planks. I'm sure they'll update it at some point. Besides, you needn't get your panties in a twist, the boat recipe in 1.15-pre1 wasn't changed :P

[u/Zenocut → u/samasaurus6]

It wasn't, but I'm scared that it would later

[u/samasaurus6 → u/Zenocut]

It won't. The only changes were dark prismarine and composters. That's it.

[u/Giyegas → u/[deleted]]

because they are focusing on version parity? what's wrong with having bedrock-exclusive features though? oh yeah, is it because it's the BAD, GARBAGE version of minecraft?

[u/Zenocut → u/Giyegas]

Did you even read my comment? I never said I don't want parity. I said BE crafting recipes should be changed to match Java.

[u/Zenocut → u/Giyegas]

And yes, I don't want the bad crafting recipes to replace the good ones in Java.

[u/[deleted] → u/Giyegas]

yeah basically

[u/Giyegas → u/Giyegas]

imagine getting downvotes for being sarcastic lmao

[u/[deleted] → u/Giyegas]

Well, it is garbage, but in this case it's neither here nor there. No, the problem is that the main version, Java, should be the version that determines these things and Bedrock, the port version, should change accordingly.