Quote from BrokenEye
Seven-point-ten? What manner of foul bewitchment is this? There is no point-ten! Point-ten is the same as point-one!
What difference does that make for version identification? It is never actually interpreted as a number, only as a text string. Not to mention the obvious fact that 1.7.10 is not a valid decimal number to begin with.
You would indeed be right if you were to do this: if (7.1 == 7.10) printf ("Equal"); else printf ("Not equal");
But what happens if you do this? if (strcmp ("7.1", "7.10") == 0) printf ("Equal"); else printf ("Not equal");
It is all about context. In the context of mathematics 7.1 is indeed 7.10 and you always get the same result from equations, but in the context of version numbering / identification, 7.1 and 7.10 are distinct identifiers. You should actually read 1.7.10 as 3 numbers separated by dots, where each number has its own meaning. 1 is the release number, 7 is the major patch version and 10 is the minor patch version.
0
Unbreaking is much more likely to come with Efficiency than the other way around, from my experience any ways, so at this point I only go for Unbreaking, Fortune and Silk Touch picks, and add an Unbreaking 3 book if it didn't come with the latter two.
0
Did you actually use a stopwatch to get that? I see the world exit delay too but it's nowhere near 1 minute, 4 seconds at the absolute most.
0
It does. Though it's worth noting that the newest launcher is a native executable and downloads the latest Java VM version for the platform, so your own Java installation won't be used by the game unless you are using the older Java-based launcher.
5
Patches affecting software version identifiers is an industry standard dating back decades and there is absolutely no reason not to do it, it brings consistency and awareness of progress to those who need it (servers, modders...). The system right now works just fine; bugfixes and security updates increment the right-most value while major content updates increment the middle one.
Also, Mojang is the one developing, releasing and labelling these updates, not MS.
0
If someone provided a fixed .class file I'd be very thankful, it would also likely work with 1.8.8+ just by renaming it to the correct obfuscated class for each update.
0
The clickfest can only really be avoided if the game rewards more timed / careful combat strategies, can be done with stuff like re-attack delays, taking damage cancels attacks (you'd want to retreat instead before trying again), shields absorb all damage when used / held in front of you but can't be used at the same time as sword swings...
But then there's the question where to draw the line for complexity, we want more skill-based combat but not a fighting simulator with a billion variables. Hopefully Mojang will pull this off.
2
The 2nd and 3rd line strongly indicate that he was just joking and saying he was dreaming it.
0
Yes, and in the case of Java VM it can actually hurt to allocate way more than it needs, then the garbage collector will have a tendency to get lazier and let unused objects build up to larger piles before it does a sweep, resulting in potentially longer in-game stutters.
0
There is a thing called virtual memory. Every process running on your computer can allocate up to the maximum defined by the OS, it's not a case where every process needs to share your 8 GBs together and that's it, the RAM is just a cache: the runtime environment of a process is bound to its context, and that context could be stored on RAM or a page file on the hard disk for examples. So Minecraft (or more correctly the Java VM) 'could' allocate up to the maximum of your OS if it so desired, for 64-bit OSs that number is quite large (but usually not remotely as large as 64-bit addressing space allows). A good rule of thumb is that your most active processes should together stay within your RAM capacity, after that things start slowing down real fast since disk access, even SSD, is far slower than RAM.
As for my own MC, I play vanilla and I usually see it stay around 400-500 MBs, though I don't make it a habit to check.
0
I had forgotten about it for a while but it happened again recently when I put down 2 beds in the 2nd floor of a village church. If I sleep in the innermost bed (touching 2 walls) I'll be spawned on the ledge outside the church tower upon waking up. Guess the programmers just forgot to check for the special case where the diagonal is spawn-eligible but is blocked by 2 solid blocks on the adjacents.
1
Playing the game without backups in general is a bad idea, both because you can't foresee hardware failures or data corruption, and of course the game is broken to the point of hilarity at this point, experienced players probably die more often to glitches than actual gameplay dangers. Another "fun" glitch to watch out for that nearly had me walk straight off the edge of my tower to my death: beds can spawn you on the wrong side of a structure if the diagonal is air or you are using glass panes at floor level.
0
They changed snapshot day to Wednesday during 1.8 development.
0
Yeah no kidding, I actually consider them to be the more reasonable part of the MC community. Better late than never I suppose.
I do wonder how slow Mojang needs to be to make the last few people in denial about the situation finally crack. Whether one is excited or not, you have to ask yourself what they are doing with their supposed 8 hours a day 5 days a week, especially when looking at past updates and how quickly they appeared, with a smaller team no less. I see people talking about internal code changes, that was a valid reasoning for 1.8 but Searge explicitly stated that 1.9 would not have any big rewrites, and would be feature-driven. If the team has been using up their time well in the past 9 months, 1.9 is going to be astronomical in scale, which would indicate that there are a whole bunch of things they haven't shown us yet in teasers.
0
Looks like Reddit is also noticing that Mojang's productivity has slowed down like a virus-infected computer:
https://www.reddit.com/r/Minecraft/comments/389y2b/its_been_273_days_since_18_update_time_flies/
0
Your account's unique identifier is static and can't be changed, that is the very reason why name changes are allowed.
(Not sure what this has to do with the above discussion, though.)