Just adding a 'me too' to this ticket, as when I contacted Mojang Support via Twitter, they seemed to be unaware of the problem.
I'm aware, as above, that there are some 'hacks' to make it work... but as also noted, that's not really a fix. MC should work on Yosemite (OS X 10.10) out of the box, or minimally with a simple additional install of a RECENT version of Java. My gosh, how long as Yosemite been PUBLIC beta even! Does Mojang not even have an OS X box around or something???
Sorry for the tone here, but I'm finding it almost unimaginable that this hasn't been dealt with yet, and if not, that it isn't quite high on the priority list.
Jonathan, good point, but then that ticket should be updated to talk more about Yosemite. This issue is no longer just a matter of a Mac user here or there who has updated their Java to a more recent version. It's now going to affect the entire Mac community who are quickly updating to Yosemite. And most of them aren't going to know to fix it or will end up installing old Java.
Just adding a more recent comment here and a 'me too'. Mojang Support seemed unaware of this issue via a Twitter conversation. I'm not sure they get that this will be EVERY Yosemite user (the percentage is growing quickly... it was over 12% within 4 days of release). And, a 'hack' isn't a good solution... Mojang needs to fix this so it works 'out of the box.'
Does Mojang have no Macs? Yosemite has been out for well over a week and was in public beta for quite some time. What am I missing here???
I'm not sure what is going on either. I've been in a Twitter conversation with Mojang Support about this as well, and they are at least playing clueless about the existence of a problem. I'm not sure if this is typical Mojang support or if it has something to do with the Microsoft purchase of them, etc. as this is the first time I've contacted them as well.
My understanding, from the reading I've done, is that if you install the Java 6 JDK (which gets pointed to when I launch MC on my Yosemite laptop), it might then work. I haven't actually tried that yet, as I'm hoping Mojang comes up with, IMO, a better solution. I'd think they would make it work on a newer version of Java... but either way, they should have some good Mac OSX Yosemite instructions, now that it doesn't work 'out of the box' like it has in the past.
Can anyone who knows MC and Java better chime in? From what I gather, Yosemite no longer includes any Java JDK, correct? Does MC work on Java JDK v7 or v8? If yes to the latter, then I'm expecting install instructions for, hopefully, v8 of the Java JDK (yes, I can probably figure it out... but I mean for ALL users... some decent documentation) and an update to the Launcher so it then works without tweaking files, etc.
Hey guys... while I appreciate the effort, IMO, this is something Mojang needs to address directly. (Plus, I'd typically not advise average users to start downloading various fixes from the community - it's a security risk!). Minecraft is a PAID application which should be supported by Mojang.
An OSX Yosemite user should be able to go to site, follow some simple instructions, and start playing MC. Until this is the case, this issue isn't solved. (And, I'd sure hope that solution is to get us on a more recent Java than v6.)
Jeroen - No, this has nothing to do with Apple. If Apple had somehow made it impossible to run Minecraft any longer, then yes, it would have something to do with Apple. That's not the case, so this is something Mojang CAN address. The fact that they seem to refuse to do so indicates something else is going on.
And, weeks after a major platform software release... to still be acting like they have no clue what users are complaining about smacks of either incredible ineptness or willful poor support. (Insert whatever lame reason for these you like.)
Bryan - exactly. While I could figure out a couple ways to get Minecraft running again on my Yosemite laptop (and I'm holding off upgrading my desktop due to this issue in part), there clearly needs to be an official update with clear instructions (if additional installs are needed) from Mojang.
Hey everyone, I finally got sick of it not working and tried a 'fix' on my Yosemite laptop that was pretty easy and wrote up an article about it. I'd love input from someone who knows more about Java. I'm pretty sure my fix wouldn't help folks who do other stuff with Java and need multiple versions (like this ticket)... but it might work for the average Minecraft player who updated to Yosemite and just wants Minecraft to work.
Hi Jonathan, as I think I mentioned earlier... if MCL-1049 could be updated to reflect the Yosemite nature and importance of the issue, then I'd say yea, it's a duplicate. The thing is though, that MCL-1049 reads more like someone who wants the ability to run Minecraft with other or multiple Java installs, not that Minecraft is now effectively 'broken' for all Yosemite users.
Also, I got sick of it not working on my laptop and 'fixed' it. I wrote up an article I'd love any input on, as I don't know it will work for all situations and I have limited testing ability (and don't know all that much about Java). And, certainly, Mojang REALLY REALLY needs to address this ASAP (like months ago!).
Also, yes, my understanding is that it will work if you download Apple's Java 6 rendition, but IMO that still isn't a fix because it requires extra steps that Mojang hasn't mentioned or documented and isn't a great idea from a functional or security standpoint to install an outdated version of Java on a new OS. (And, I think now that I have Minecraft running on Java 8, it is taking less CPU and other resources.)
True, but if I were a Minecraft developer looking at prioritizing the importance of tickets, it should make a big difference whether we're talking about the flexibility to support various versions of Java (a good thing for sure, but something many of those who might do so could fix themselves), vs Yosemite users (hundreds of millions of them? many non-technical) being unable to play Minecraft (or at least hesitant to do so). MCL-1049 sounds like a special-case improvement vs a customer support catastrophe.
That said, the fact that Mojang is ignoring this, speaks to some greater underlying issue or conspiracy anyway... so I'm not holding my breath.
I totally agree about it using the latest version automatically. That would be great! But, my point is that from the standpoint of Mojang (or the general Mac user-base), it should be more important that MC doesn't work for Yosemite users than that it doesn't pick the right version of Java. Most Mac users wouldn't have more than one version unless it were accidental.
At least in my experience, something did change with Yosemite. Unless I'm getting really forgetful, I don't recall installing anything special when I started playing Minecraft... and my laptop is new enough it must have shipped with Mavericks. Are you saying that Minecraft wouldn't run on a clean Mavericks system or would have broke when someone upgraded from, say Mt Lion? I'm also pretty sure when I started playing MC on my desktop, I would have been running Mavericks (which I still am there). I don't recall having to install Java for either. (Though it's likely I had Java previously on my desktop, so that makes sense... but my point is that upgrading to Mavericks didn't break things from my memory.)
I must be getting forgetful. I wonder if the install method was different (like just a button telling me I needed Java with an 'OK' or something and then it installed). I must have installed it on my laptop 2013 MacBook Air, but I don't recall a 'more info' button and going to an Apple website, downloading an installer, etc. Maybe with Mavericks there was a different way?
I guess it makes sense for my desktop, as I probably had Java 6 lingering around from an earlier OSX version, as I've upgraded the OS and moved from system to system for years without a fully clean install.
I guess I'll need to get my Parallels up to date and do some testing.
Very good news indeed. And I'm really happy it looks like they are going fix it right. Aside from taking WAY too long and not communicating very well, kudos Mojang.
The solution Mojang is working on sounds great, but until then if you're just wanting to get Minecraft working, I wrote up a pretty detailed article (and recently added a YouTube walkthrough) on getting it working on OS X Yosemite with Java 8. It worked on all my systems and seems to have worked for most who have tried it so far. The nice thing about this method is that you don't have to tweak any files or install any unknown components, etc. http://www.cgwerks.com/make-minecraft-work-mac-osx-yosemite-latest-java-8/
Well, it took them over two years to patch that last server security hole, while being bugged by the guy that found the problem. So, I'm sure they are working on it... it's just a matter of when (weeks, months, years?).
Just adding a 'me too' to this ticket, as when I contacted Mojang Support via Twitter, they seemed to be unaware of the problem.
I'm aware, as above, that there are some 'hacks' to make it work... but as also noted, that's not really a fix. MC should work on Yosemite (OS X 10.10) out of the box, or minimally with a simple additional install of a RECENT version of Java. My gosh, how long as Yosemite been PUBLIC beta even! Does Mojang not even have an OS X box around or something???
Sorry for the tone here, but I'm finding it almost unimaginable that this hasn't been dealt with yet, and if not, that it isn't quite high on the priority list.
Jonathan, good point, but then that ticket should be updated to talk more about Yosemite. This issue is no longer just a matter of a Mac user here or there who has updated their Java to a more recent version. It's now going to affect the entire Mac community who are quickly updating to Yosemite. And most of them aren't going to know to fix it or will end up installing old Java.
Just adding a more recent comment here and a 'me too'. Mojang Support seemed unaware of this issue via a Twitter conversation. I'm not sure they get that this will be EVERY Yosemite user (the percentage is growing quickly... it was over 12% within 4 days of release). And, a 'hack' isn't a good solution... Mojang needs to fix this so it works 'out of the box.'
Does Mojang have no Macs? Yosemite has been out for well over a week and was in public beta for quite some time. What am I missing here???
Hi Chrissy,
I'm not sure what is going on either. I've been in a Twitter conversation with Mojang Support about this as well, and they are at least playing clueless about the existence of a problem. I'm not sure if this is typical Mojang support or if it has something to do with the Microsoft purchase of them, etc. as this is the first time I've contacted them as well.
My understanding, from the reading I've done, is that if you install the Java 6 JDK (which gets pointed to when I launch MC on my Yosemite laptop), it might then work. I haven't actually tried that yet, as I'm hoping Mojang comes up with, IMO, a better solution. I'd think they would make it work on a newer version of Java... but either way, they should have some good Mac OSX Yosemite instructions, now that it doesn't work 'out of the box' like it has in the past.
Can anyone who knows MC and Java better chime in? From what I gather, Yosemite no longer includes any Java JDK, correct? Does MC work on Java JDK v7 or v8? If yes to the latter, then I'm expecting install instructions for, hopefully, v8 of the Java JDK (yes, I can probably figure it out... but I mean for ALL users... some decent documentation) and an update to the Launcher so it then works without tweaking files, etc.
Hey guys... while I appreciate the effort, IMO, this is something Mojang needs to address directly. (Plus, I'd typically not advise average users to start downloading various fixes from the community - it's a security risk!). Minecraft is a PAID application which should be supported by Mojang.
An OSX Yosemite user should be able to go to site, follow some simple instructions, and start playing MC. Until this is the case, this issue isn't solved. (And, I'd sure hope that solution is to get us on a more recent Java than v6.)
Jeroen - No, this has nothing to do with Apple. If Apple had somehow made it impossible to run Minecraft any longer, then yes, it would have something to do with Apple. That's not the case, so this is something Mojang CAN address. The fact that they seem to refuse to do so indicates something else is going on.
And, weeks after a major platform software release... to still be acting like they have no clue what users are complaining about smacks of either incredible ineptness or willful poor support. (Insert whatever lame reason for these you like.)
Bryan - exactly. While I could figure out a couple ways to get Minecraft running again on my Yosemite laptop (and I'm holding off upgrading my desktop due to this issue in part), there clearly needs to be an official update with clear instructions (if additional installs are needed) from Mojang.
Hey everyone, I finally got sick of it not working and tried a 'fix' on my Yosemite laptop that was pretty easy and wrote up an article about it. I'd love input from someone who knows more about Java. I'm pretty sure my fix wouldn't help folks who do other stuff with Java and need multiple versions (like this ticket)... but it might work for the average Minecraft player who updated to Yosemite and just wants Minecraft to work.
http://www.cgwerks.com/make-minecraft-work-mac-osx-yosemite-latest-java-8/
Note: Yes, this ABSOLUTELY needs to be addressed (a long time ago!) by Mojang!
Hi Jonathan, as I think I mentioned earlier... if
MCL-1049could be updated to reflect the Yosemite nature and importance of the issue, then I'd say yea, it's a duplicate. The thing is though, thatMCL-1049reads more like someone who wants the ability to run Minecraft with other or multiple Java installs, not that Minecraft is now effectively 'broken' for all Yosemite users.Also, I got sick of it not working on my laptop and 'fixed' it. I wrote up an article I'd love any input on, as I don't know it will work for all situations and I have limited testing ability (and don't know all that much about Java). And, certainly, Mojang REALLY REALLY needs to address this ASAP (like months ago!).
http://www.cgwerks.com/make-minecraft-work-mac-osx-yosemite-latest-java-8/
Also, yes, my understanding is that it will work if you download Apple's Java 6 rendition, but IMO that still isn't a fix because it requires extra steps that Mojang hasn't mentioned or documented and isn't a great idea from a functional or security standpoint to install an outdated version of Java on a new OS. (And, I think now that I have Minecraft running on Java 8, it is taking less CPU and other resources.)
True, but if I were a Minecraft developer looking at prioritizing the importance of tickets, it should make a big difference whether we're talking about the flexibility to support various versions of Java (a good thing for sure, but something many of those who might do so could fix themselves), vs Yosemite users (hundreds of millions of them? many non-technical) being unable to play Minecraft (or at least hesitant to do so).
MCL-1049sounds like a special-case improvement vs a customer support catastrophe.That said, the fact that Mojang is ignoring this, speaks to some greater underlying issue or conspiracy anyway... so I'm not holding my breath.
I totally agree about it using the latest version automatically. That would be great! But, my point is that from the standpoint of Mojang (or the general Mac user-base), it should be more important that MC doesn't work for Yosemite users than that it doesn't pick the right version of Java. Most Mac users wouldn't have more than one version unless it were accidental.
At least in my experience, something did change with Yosemite. Unless I'm getting really forgetful, I don't recall installing anything special when I started playing Minecraft... and my laptop is new enough it must have shipped with Mavericks. Are you saying that Minecraft wouldn't run on a clean Mavericks system or would have broke when someone upgraded from, say Mt Lion? I'm also pretty sure when I started playing MC on my desktop, I would have been running Mavericks (which I still am there). I don't recall having to install Java for either. (Though it's likely I had Java previously on my desktop, so that makes sense... but my point is that upgrading to Mavericks didn't break things from my memory.)
I must be getting forgetful. I wonder if the install method was different (like just a button telling me I needed Java with an 'OK' or something and then it installed). I must have installed it on my laptop 2013 MacBook Air, but I don't recall a 'more info' button and going to an Apple website, downloading an installer, etc. Maybe with Mavericks there was a different way?
I guess it makes sense for my desktop, as I probably had Java 6 lingering around from an earlier OSX version, as I've upgraded the OS and moved from system to system for years without a fully clean install.
I guess I'll need to get my Parallels up to date and do some testing.
Very good news indeed. And I'm really happy it looks like they are going fix it right. Aside from taking WAY too long and not communicating very well, kudos Mojang.
The solution Mojang is working on sounds great, but until then if you're just wanting to get Minecraft working, I wrote up a pretty detailed article (and recently added a YouTube walkthrough) on getting it working on OS X Yosemite with Java 8. It worked on all my systems and seems to have worked for most who have tried it so far. The nice thing about this method is that you don't have to tweak any files or install any unknown components, etc.
http://www.cgwerks.com/make-minecraft-work-mac-osx-yosemite-latest-java-8/
Well, it took them over two years to patch that last server security hole, while being bugged by the guy that found the problem. So, I'm sure they are working on it... it's just a matter of when (weeks, months, years?).