This is the official thread for posting general opinions about the upcoming 1.13 snapshots and update releases.
Please be respectful of other peoples opinions and try to keep the discussion civil and on-topic. Suggestions or ideas for Minecraft should be posted in the Suggestions forum section. This thread is only for discussing the actual content of the 1.13 snapshots and release.
Just a reminder: flaming/insulting other users and the use of profanity will not be tolerated. Please see the forum rules for more information.
The sounds seem a bit strange to me, as if they are playing from a low quality speaker. Maybe it has to do with the updated LWJGL (and OpenAL packaged with it).
Here are video comparisons of sound in 1.12 and 17w43b (the first video being 1.12). The 17w43b seems to have lower quality and the panning is too severe:
Hi, I'm going to solve a thing that happens to some people, Snapshots 1.13 will have many bugs of the usual so it will have to be in 1.12 until they solve the bugs that we will find during the game, since they will change the graphics of the game, and that will give many errors
I Always love big minecraft updates. I love the fact that they are going to introduce new textures. Previous builds may look a bit odd with new textures, but we can explore new combinations of blocks and perhaps make something completely different with them. I get really inspired when I see those new textures.
The data packs also really excite me! I have never really been much into altering minecraft, regarding both resource packs and mods, but I think this is a good opportunity to get started. I Always hated the fact that blocks like clay, dirt, sand and gravel are non-renewable, but with the new data packs, I can just add my own recipe for them.
On top of that, I can now also create a function which makes shulkers spawn in the end like endermen, which is something I really wanted, because I don't want to spend increasing amounts of time, travelling to unexplored end-cities. I will make those shulkers very rare though and I'll only let them spawn on the outer end islands. Of course I could already do this in 1.12, but now I can pack everything together easily and just copy-paste it anywhere I want( and perhaps there are people I can share it with ).
Minecraft already runs perfectly fine on my computer, so the performance boost which this update is supposed to give, doesn't excite me that much, but I'm sure loads of people who had troubles with minecraft are going to love this.
I'm very much into commands lately, because I wanted to try and make a minigame. Just for the sake of making it. The extra command hints are really going to help a lot with that, because I'm currently switching back and forth between my game and the wiki. The wiki always loads horribly slow for me, so that's not ideal to say the least. These hints are not in the snapshots just yet, but I am really looking forward to them.
They said that they were going to do a complete overhaul of the command system. They have decided that the [if|unless] thingy would be added to the execute command.
This is useful, because you can use it for every command. Having the [if|unless] in the function command is strange, because: "Why would the function command have it and not the tp command for example?" Now, the [if|unless] is in one central location and it's accessable for every command. It's no longer necessary to have it in the function command, so keeping it there would be sloppy. Since they were going to change everything anyway, they might as well change the function command.
When they are done, we have a much more refined command system, which is a bit tedious at the beginning, because we need to relearn everything, but it is going to be much more enjoyable in the long term.
They said that they were going to do a complete overhaul of the command system. They have decided that the [if|unless] thingy would be added to the execute command.
This is useful, because you can use it for every command. Having the [if|unless] in the function command is strange, because: "Why would the function command have it and not the tp command for example?" Now, the [if|unless] is in one central location and it's accessable for every command. It's no longer necessary to have it in the function command, so keeping it there would be sloppy. Since they were going to change everything anyway, they might as well change the function command.
When they are done, we have a much more refined command system, which is a bit tedious at the beginning, because we need to relearn everything, but it is going to be much more enjoyable in the long term.
Implementing a certain mechanic never requires deprecating another which is already established.
Instead of having simple syntax for functions, everything has to be done through a certain command, in a certain order to perform the same action.
Introducing new mechanics you are intentionally going to change is called rushing, it wasn’t finished when they added it to the game, and now everything that was built upon the current functions system is either obsolete or has to be updated.
If they wanted it to be flexible they should’ve waited with their update and make everything right the first time, not rushing snapshots and release versions with “half-way there” features and whatnot.
I sure am not going to update megabytes of text and hundreds of structures because someone that that would be a great idea.
Implementing a certain mechanic never requires deprecating another which is already established.
Instead of having simple syntax for functions, everything has to be done through a certain command, in a certain order to perform the same action.
Introducing new mechanics you are intentionally going to change is called rushing, it wasn’t finished when they added it to the game, and now everything that was built upon the current functions system is either obsolete or has to be updated.
If they wanted it to be flexible they should’ve waited with their update and make everything right the first time, not rushing snapshots and release versions with “half-way there” features and whatnot.
I sure am not going to update megabytes of text and hundreds of structures because someone that that would be a great idea.
Very much true that new functionality shouldn't deprecate old features, but I don't think this is about adding something new, but rather about centralising an existing functionality to allow easy global use and easy maintainance for the minecraft developers as a bonus.
The syntax for the function command is now even simpler, because it has become just one argument instead of three. The idea that everything has to be done through a certain command, in a certain order, well... that's basically the essence of commands and programming in general. after all: You have to write the original function command in a certain order as well. You can't switch around the arguments. I can imagine however, that you don't think about the execute command directly if you think about conditional execution, which makes the new system less intuitive.
They didn't introduce the function command just to change it later. They have thought it through and thought that the original implementation was the way to go. That's why they introduced the command like this. Since minecraft 1.13 was going to break all the commands regardless, this was the perfect moment to rethink the complete system. They have decided that the [if|unless] functionality should be globally applicable, rather than just for functions, so they moved this functionality to a command that is specialised in conditional execution.
If they were to wait with introducing new features, just because they might change in the future, we wouldn't have any updates at all, because everything is prone to change, like minecraft 1.13 proves. Everything can change in the future, but they release it the way they think is best at right now.
You don't have to update all your megabytes of text and all your structures. Just don't update your minecraft. It's one of the things I find charming about minecraft: You are not forced to use a certain version. Deprecated worlds or commands don't exist. They just work on a different version. You see this very well in the modded world. A lot of mods only work in certain minecraft versions. Everybody with a legal minecraft copy has access to all the versions, including the historical ones.
I do understand that it is unfair to release the new commands together with all the other features, because everybody wants better performance, but not everybody wants new commands. I guess you'll have to make a choice there.
Just checked out the "b" snapshot. Terrain closer to you seems to load slightly quicker, although the distant chunks still take a while to fully load (Talking 24-32 render distance). Took notice of the new loading screen. Meh. I did however make an interesting find at least in the world I loaded. Jungle was right next to Extreme hills. Not sure if it was the seed again, but the terrain seemed to have a lot more variation, and the Extreme Hills didn't look like a typical post-1.7 hills biome. Is that just me?
It's a bit early to be saying very much, but we'll see what comes to us down the road.
Im really happy with this update.My computer runs minecraft at 30-40 fps and with this update i got incredible 80-90 fps on normal worlds.Thats spetacular!
Also im such interested at the datapacks what a i can do with them,I see many possibilities of what do with them,and how easier they got to be made and ´installed´.Kinda curious with what the community will be able to do with this!
Until now,the only thing i got a little angry with was the missing sounds sometimes,but as always,after some snapshots,this should get fixed
Very much true that new functionality shouldn't deprecate old features, but I don't think this is about adding something new, but rather about centralising an existing functionality to allow easy global use and easy maintainance for the minecraft developers as a bonus.
The syntax for the function command is now even simpler, because it has become just one argument instead of three. The idea that everything has to be done through a certain command, in a certain order, well... that's basically the essence of commands and programming in general. after all: You have to write the original function command in a certain order as well. You can't switch around the arguments. I can imagine however, that you don't think about the execute command directly if you think about conditional execution, which makes the new system less intuitive.
They didn't introduce the function command just to change it later. They have thought it through and thought that the original implementation was the way to go. That's why they introduced the command like this. Since minecraft 1.13 was going to break all the commands regardless, this was the perfect moment to rethink the complete system. They have decided that the [if|unless] functionality should be globally applicable, rather than just for functions, so they moved this functionality to a command that is specialised in conditional execution.
If they were to wait with introducing new features, just because they might change in the future, we wouldn't have any updates at all, because everything is prone to change, like minecraft 1.13 proves. Everything can change in the future, but they release it the way they think is best at right now.
You don't have to update all your megabytes of text and all your structures. Just don't update your minecraft. It's one of the things I find charming about minecraft: You are not forced to use a certain version. Deprecated worlds or commands don't exist. They just work on a different version. You see this very well in the modded world. A lot of mods only work in certain minecraft versions. Everybody with a legal minecraft copy has access to all the versions, including the historical ones.
I do understand that it is unfair to release the new commands together with all the other features, because everybody wants better performance, but not everybody wants new commands. I guess you'll have to make a choice there.
1.13 was not going to magically deprecate everything by the nature of itself, it was a decision made prior to 1.12 that it would happen.
Newer version, at least as stated and I'll take the word for it, should increase performance by a bunch, and I'm willing to sacrifice a few projects *just* for that. Still, that's some one shouldn't be force to do. Letting players adapt, as in allowing for functions to be run with conditions would be just magnificent.
We're making one very big change that is necessary, cannot be avoided and will break every single command: changing almost every block/item ID so that we can have infinite blocks & items. Right now we have no space for any extra blocks in the game.
We need to do that, and it's happening for 1.13. Every command relating to blocks or items will be broken. It's unavoidable.
Because of that, I'm rewriting the entire command system because things are already broken. I'm adding new features, speeding it up, making changes that people requested for years. All of this in hopes that it means we don't have to make any major changes again in the future.
We're breaking everything at once, instead of every single update.
So... You're right, it's not magic, but it is also not really a decision. If it wasn't going to happen in 1.13, then it would in 1.14, because it was unavoidable. Hopefully, after this update, the commands won't change again and players should be able to adapt to one command system.
Horses deserve the detail, such long legs just look awkward without the second joint... especially while walking. No other minecraft mob has legs like them, so it makes sense that they wouldn't have a second joint, as it wouldn't add anything to the mob.
The face just seems odd to me. Why remove the opening mouth? It was the best part of horses! The head shape itself is poor, comes out too widely and the snout obviously is nothing like a horse's snout should be. It also is strange that the mane ends so abruptly; it seemed fine to me when it went into the body.
It seems counter-productive, to update every texture to be more consistent and get away from Notch's pixel art style, while downgrading the most detailed mob to better fit Notch's modelling style. If you're going to change models too, why not bring them in line with the best model you have? The horse does not seem terribly out of place as is, in my opinion.
It reminds me of the polar bear model, which I hate with a passion.
Horses deserve the detail, such long legs just look awkward without the second joint... especially while walking. No other minecraft mob has legs like them, so it makes sense that they wouldn't have a second joint, as it wouldn't add anything to the mob.
The face just seems odd to me. Why remove the opening mouth? It was the best part of horses! The head shape itself is poor, comes out too widely and the snout obviously is nothing like a horse's snout should be. It also is strange that the mane ends so abruptly; it seemed fine to me when it went into the body.
It seems counter-productive, to update every texture to be more consistent and get away from Notch's pixel art style, while downgrading the most detailed mob to better fit Notch's modelling style. If you're going to change models too, why not bring them in line with the best model you have? The horse does not seem terribly out of place as is, in my opinion.
It reminds me of the polar bear model, which I hate with a passion.
I agree with you. I do wonder why they removed the opening mouth, like why the heck?
From some of the feedback in here I would like to point out that Jeb said that while they aren't planning on reverting the horse model, they are still working on improving it. Dinnerbone has also said that the command system still isn't done, and some things are broken, so the large box and tabbing to complete commands will likely be fixed.
Want some advice on how to thrive in the Suggestions section? Check this handy list of guidelines and tips for posting your ideas and responding to the ideas of others!
From some of the feedback in here I would like to point out that Jeb said that while they aren't planning on reverting the horse model, they are still working on improving it. Dinnerbone has also said that the command system still isn't done, and some things are broken, so the large box and tabbing to complete commands will likely be fixed.
I'm not fond of the new horse model one bit. if anything it's the cow and pig that need model upgrades, not downgrading the horse model. Their faces are too flat. I really hope all the feedback gets us the proper horse model back.
Please be respectful of other peoples opinions and try to keep the discussion civil and on-topic. Suggestions or ideas for Minecraft should be posted in the Suggestions forum section. This thread is only for discussing the actual content of the 1.13 snapshots and release.
Just a reminder: flaming/insulting other users and the use of profanity will not be tolerated. Please see the forum rules for more information.
- sunperp
The sounds seem a bit strange to me, as if they are playing from a low quality speaker. Maybe it has to do with the updated LWJGL (and OpenAL packaged with it).
Here are video comparisons of sound in 1.12 and 17w43b (the first video being 1.12). The 17w43b seems to have lower quality and the panning is too severe:
Hi, I'm going to solve a thing that happens to some people, Snapshots 1.13 will have many bugs of the usual so it will have to be in 1.12 until they solve the bugs that we will find during the game, since they will change the graphics of the game, and that will give many errors
I noted something's wrong with 1.13 snapshots.
If you started Minecraft offline, the 1.13 snapshots seem to be ignored.
You need to go online to play 1.13 snapshots.
I hope Minecraft 1.13 does not need to start online to play it.
My videos: https://www.youtube.com/user/robingravel
My cartoons: http://www.dailymotion.com/robin-gravel
Flash Animation (if your computer supports flash):
http://robingravel.byethost15.com/eflash.htm
Few flash movies have easter egg/extras
1.13 is going to ruin Minecraft!, the days of chunky gameplay and buggy features are over! /s
I Always love big minecraft updates. I love the fact that they are going to introduce new textures. Previous builds may look a bit odd with new textures, but we can explore new combinations of blocks and perhaps make something completely different with them. I get really inspired when I see those new textures.
The data packs also really excite me! I have never really been much into altering minecraft, regarding both resource packs and mods, but I think this is a good opportunity to get started. I Always hated the fact that blocks like clay, dirt, sand and gravel are non-renewable, but with the new data packs, I can just add my own recipe for them.
On top of that, I can now also create a function which makes shulkers spawn in the end like endermen, which is something I really wanted, because I don't want to spend increasing amounts of time, travelling to unexplored end-cities. I will make those shulkers very rare though and I'll only let them spawn on the outer end islands. Of course I could already do this in 1.12, but now I can pack everything together easily and just copy-paste it anywhere I want( and perhaps there are people I can share it with ).
Minecraft already runs perfectly fine on my computer, so the performance boost which this update is supposed to give, doesn't excite me that much, but I'm sure loads of people who had troubles with minecraft are going to love this.
I'm very much into commands lately, because I wanted to try and make a minigame. Just for the sake of making it. The extra command hints are really going to help a lot with that, because I'm currently switching back and forth between my game and the wiki. The wiki always loads horribly slow for me, so that's not ideal to say the least. These hints are not in the snapshots just yet, but I am really looking forward to them.
Check out my ongoing project: https://github.com/srQianna/Adventure
They said that they were going to do a complete overhaul of the command system. They have decided that the [if|unless] thingy would be added to the execute command.
This is useful, because you can use it for every command. Having the [if|unless] in the function command is strange, because: "Why would the function command have it and not the tp command for example?" Now, the [if|unless] is in one central location and it's accessable for every command. It's no longer necessary to have it in the function command, so keeping it there would be sloppy. Since they were going to change everything anyway, they might as well change the function command.
When they are done, we have a much more refined command system, which is a bit tedious at the beginning, because we need to relearn everything, but it is going to be much more enjoyable in the long term.
Implementing a certain mechanic never requires deprecating another which is already established.
Instead of having simple syntax for functions, everything has to be done through a certain command, in a certain order to perform the same action.
Introducing new mechanics you are intentionally going to change is called rushing, it wasn’t finished when they added it to the game, and now everything that was built upon the current functions system is either obsolete or has to be updated.
If they wanted it to be flexible they should’ve waited with their update and make everything right the first time, not rushing snapshots and release versions with “half-way there” features and whatnot.
I sure am not going to update megabytes of text and hundreds of structures because someone that that would be a great idea.
Check out my ongoing project: https://github.com/srQianna/Adventure
Very much true that new functionality shouldn't deprecate old features, but I don't think this is about adding something new, but rather about centralising an existing functionality to allow easy global use and easy maintainance for the minecraft developers as a bonus.
The syntax for the function command is now even simpler, because it has become just one argument instead of three. The idea that everything has to be done through a certain command, in a certain order, well... that's basically the essence of commands and programming in general. after all: You have to write the original function command in a certain order as well. You can't switch around the arguments. I can imagine however, that you don't think about the execute command directly if you think about conditional execution, which makes the new system less intuitive.
They didn't introduce the function command just to change it later. They have thought it through and thought that the original implementation was the way to go. That's why they introduced the command like this. Since minecraft 1.13 was going to break all the commands regardless, this was the perfect moment to rethink the complete system. They have decided that the [if|unless] functionality should be globally applicable, rather than just for functions, so they moved this functionality to a command that is specialised in conditional execution.
If they were to wait with introducing new features, just because they might change in the future, we wouldn't have any updates at all, because everything is prone to change, like minecraft 1.13 proves. Everything can change in the future, but they release it the way they think is best at right now.
You don't have to update all your megabytes of text and all your structures. Just don't update your minecraft. It's one of the things I find charming about minecraft: You are not forced to use a certain version. Deprecated worlds or commands don't exist. They just work on a different version. You see this very well in the modded world. A lot of mods only work in certain minecraft versions. Everybody with a legal minecraft copy has access to all the versions, including the historical ones.
I do understand that it is unfair to release the new commands together with all the other features, because everybody wants better performance, but not everybody wants new commands. I guess you'll have to make a choice there.
Just checked out the "b" snapshot. Terrain closer to you seems to load slightly quicker, although the distant chunks still take a while to fully load (Talking 24-32 render distance). Took notice of the new loading screen. Meh. I did however make an interesting find at least in the world I loaded. Jungle was right next to Extreme hills. Not sure if it was the seed again, but the terrain seemed to have a lot more variation, and the Extreme Hills didn't look like a typical post-1.7 hills biome. Is that just me?
It's a bit early to be saying very much, but we'll see what comes to us down the road.
Figured it was time for a change.
Im really happy with this update.My computer runs minecraft at 30-40 fps and with this update i got incredible 80-90 fps on normal worlds.Thats spetacular!
Also im such interested at the datapacks what a i can do with them,I see many possibilities of what do with them,and how easier they got to be made and ´installed´.Kinda curious with what the community will be able to do with this!
Until now,the only thing i got a little angry with was the missing sounds sometimes,but as always,after some snapshots,this should get fixed
1.13 was not going to magically deprecate everything by the nature of itself, it was a decision made prior to 1.12 that it would happen.
Newer version, at least as stated and I'll take the word for it, should increase performance by a bunch, and I'm willing to sacrifice a few projects *just* for that. Still, that's some one shouldn't be force to do. Letting players adapt, as in allowing for functions to be run with conditions would be just magnificent.
Check out my ongoing project: https://github.com/srQianna/Adventure
Following is a post by Dinnerbone on reddit:
Source: https://www.reddit.com/user/Dinnerbone/comments/6l6e3d/a_completely_incomplete_super_early_preview_of/dlf02tr
So... You're right, it's not magic, but it is also not really a decision. If it wasn't going to happen in 1.13, then it would in 1.14, because it was unavoidable. Hopefully, after this update, the commands won't change again and players should be able to adapt to one command system.
New horse is ugly, but it's just as ugly as every other mob in the game now so I guess it's consistent.
Horses deserve the detail, such long legs just look awkward without the second joint... especially while walking. No other minecraft mob has legs like them, so it makes sense that they wouldn't have a second joint, as it wouldn't add anything to the mob.
The face just seems odd to me. Why remove the opening mouth? It was the best part of horses! The head shape itself is poor, comes out too widely and the snout obviously is nothing like a horse's snout should be. It also is strange that the mane ends so abruptly; it seemed fine to me when it went into the body.
It seems counter-productive, to update every texture to be more consistent and get away from Notch's pixel art style, while downgrading the most detailed mob to better fit Notch's modelling style. If you're going to change models too, why not bring them in line with the best model you have? The horse does not seem terribly out of place as is, in my opinion.
It reminds me of the polar bear model, which I hate with a passion.
Praise be Ro-naza, greatest among the thaumaturges!
I agree with you. I do wonder why they removed the opening mouth, like why the heck?
From some of the feedback in here I would like to point out that Jeb said that while they aren't planning on reverting the horse model, they are still working on improving it. Dinnerbone has also said that the command system still isn't done, and some things are broken, so the large box and tabbing to complete commands will likely be fixed.
https://twitter.com/jeb_/status/928545653239754753
https://twitter.com/Dinnerbone/status/928291947378348032
https://twitter.com/Dinnerbone/status/928295312581591043
Want some advice on how to thrive in the Suggestions section? Check this handy list of guidelines and tips for posting your ideas and responding to the ideas of others!
http://www.minecraftforum.net/forums/minecraft-discussion/suggestions/2775557-guidelines-for-the-suggestions-forum
Okay, thank you for informing me! I don't have Twitter, so I didn't have interest in checking before. But again, thank you for sharing this to me!
I'm not fond of the new horse model one bit. if anything it's the cow and pig that need model upgrades, not downgrading the horse model. Their faces are too flat. I really hope all the feedback gets us the proper horse model back.