Okay, so before I even bother with the actual "void for vagueness" issue, Mojang is not an American company. They're a Swedish company, and Swedish law goes.
If you order, say, some candy from China, and said food has something in it that is banned from use in candy here, you can't do anything, so long as the substance isn't an illegal one.
It's a similar situation here. If you knowingly buy a Swedish product, the United States constitution no longer protects you.
That aside, let's humor the vagueness issue.
What part of this:
https://account.moja.../minecraft_eula
is too vague to be upheld in a court?
0
Secondly, it was a joke, TheMogMiner said as much on Reddit.
0
Age: 22.99 (I turn 23 on Tuesday.)
Location: Texas
Favorite thing to build: Random crap, mostly. I like to create mob farms and stuff of that nature, though.
Skype: debugman18 (Although I very rarely use it.)
0
0
Your point doesn't stand at all. As far as the chunk improvement, chunks do indeed load faster, but the order is incorrect. It's not been optimized in the snapshots we have available.
Also, nobody mentioned hyperthreading, or multicore. The new chunk loading is based on multithreading. Like I said, you have no idea what you're talking about. That is still painfully obvious.
0
You have no idea what you're talking about. Multithreading doesn't work the way you think it does.
http://en.wikipedia.org/wiki/Multithreading_(computer_architecture)
Secondly, this is discussing the next snapshot. This is even clearly in the "Future Updates" section.
0
It isn't like Dota or LoL at all. It was completely and totally random before, and that's no way to balance a game. The new system, in my opinion, is much better. It also definitely rewards staying alive more.
0
0
Unfortunately, it doesn't seem we can. I just tested it by modifying the cobblestone.json blockstate, and no dice. That would be fantastic, though.
0
This is indeed fantastic. Now, what I'm wondering, is can we used things like this:
snowy=true": { "model": "grass_snowed" }
on other blocks? For instance, could we make a snowy cobblestone?
0
3
0
-Xms is the initial amount of memory allocated, so if you have that set to 200, then yes.
If it's the launcher, it shouldn't be using that much memory.
Garbage collection doesn't make something lag. Just like memory pointers don't make something lag.
It's how it's programmed that matters. Sure, you could, in theory (with very, very excellent programming) make Minecraft lag a little insiginficant amount in C++ or another language.
It's just not worth it in any way, shape, or form.
1
That's a myth. The lag has nothing to do with Java. The game would be an extreme resource-hog even in something like C++.
0
7 months isn't terrible. Aside from that, there's a ton of bugfixes, additions, and performance improvements.
0
I disagree. He pointed out that mining stone drops cobblestone. (Broken bits of stone.) That is an aspect of realism; breaking a rock does indeed drop pieces of that rock. He also pointed out that it was due to the pick being stone.
Now, as far as homogenus rules goes (fallacies aside), the simplest answer is that it is unreasonable for Mojang to add a cobble variant for the three new stone types if they do not want to. Sure, some people may want them, but others may not (however unreasonable that unwant may be), so it's ultimately up to Mojang.
All of that aside, I would definitely like cobble variants of the new stone types.