search

andrewphorn / ClassiCube-Client

The applet used for classicube.net
34 stars 19 forks source link

Make ClassiCube playable in-browser #121

Closed Dzienny closed 9 years ago

Dzienny commented 10 years ago

Java breaks Minecraft again, this time even more. The newest Java update makes Minecraft classic on minecraft.net website unplayable. The applet hangs during the loading phase. Classicube.net still works but it will stop to work with the next Java update. It's because Oracle apparently decided to kill self signed applets altogether. I forecast that the killer update will be no sooner than in 2 to 3 months. It's logical that there should be some time for developers to prepare their applets for the changes. So 2-3 months is how much time there is to do something about this problem.

I thought about some possible solutions. Here's what I came up with:

  1. Stop players from updating their Java. But there are two problems with it. The first is that it would decrese the players' security, the second is that you can't really stop them.
  2. Buy a Java code signing certificate. It costs around 80-100$ If someone has that money to spare, it would solve the problem the easy way.
  3. Make a HTML5/JS port of the game. But it won't work. Even if it's going to "work", the performance will be a way too low.
  4. Make a Unity3D port. It seems like the only free solution that would secure the future of ClassiCube.

You can also hope that all the current users will switch to the stand alone client. But since it hasn't happened yet (many users still prefer website access), it's unlikely that it will happen.

If someone has any other ideas how to solve it, please share.

mstefarov commented 10 years ago

Option 2 is the only practical one, but none of us has $100 to spare.

Jonty800 commented 10 years ago

Hi. In December I can pay for this. Maybe. Contributions, I am a student

Jonty800 commented 10 years ago

Basically I get £500 in Dec. Which is lots of tequila

andrewphorn commented 10 years ago

That would be incredible. I have some plans for when we completely open up in a couple days, too.

Dzienny commented 10 years ago

In the newest MCDzienny release I added an announcement that is displayed to minecraft.net users every 5 minute:

Please play Minecraft Classic on classicube.net minecraft.net/classic will stop to work soon! classicube.net is free, so enjoy :)

Hopefully, at least some of the current players will switch to ClassiCube before they update their Java.

andrewphorn commented 10 years ago

Wow, thank you so much for your support :D

andrewphorn commented 10 years ago

With the help of Cueball, fragmer has purchased a code-signing certificate for use with ClassiCube- and fCraft-related projects.

DingusBungus commented 10 years ago

Awesome! That's great news. Dear Mojang: classic will be around for a long time.

Dzienny commented 10 years ago

What is the current status on this issue?

umby24 commented 10 years ago

Stick around the IRC channel and you would have known.

Status is: The company we were attempting to buy a cert from continued to get things incorrectly and customer support was less than accomidating. As such we received a refund and will be unable to continue to get a coding signing cert unless we get even more money donated.

mstefarov commented 10 years ago

Cueball and I put up $100 towards the cert. We tried to buy from Comodo, who dragged on the validation process for over a month. We got a refund eventually.

Our current best option is to buy a signing cert from another authority (Thwarte), but they charge more -- about $50 more. We haven't been able to raise any money towards getting it.

Dzienny commented 10 years ago

I see. So Comodo failed. What about some reseller like Ksoftware? Maybe they are more reliable?

mstefarov commented 10 years ago

Ksoftware resells Comodo certificates. That's exactly where we purchased it, back in early January. Verification process is still done through Comodo, who are amazingly slow and incompetent.

Dzienny commented 10 years ago

It appears that website java applet is a dead end anyway. The Chrome team plans to disable all NPAPI plugins before the end of 2014 -> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/xEbgvWE7wMk It means that Java applets won't work on Chrome anymore. There are, of course, other browsers, but still it's going to be a blow.

In my opinion, it seems reasonable to focus only on the stand-alone client. The web client can be kept as an option for its current users. However, the new players shouldn't even be informed about the website client, as it's broken and is going to just cause confusion. The web client may even make some people think that the game is in general broken or it doesn't work on their machine, and they won't even bother to download the stand-alone client.

tyteen4a03 commented 10 years ago

I support dropping support of the web applet.

mstefarov commented 10 years ago

Yeah. Might as well kill it off. We've spent a lot of money and effort trying to get a signing cert (without luck), it's probably not going to be worth spending more.

mstefarov commented 9 years ago

Applet is officially dead.

tyteen4a03 commented 9 years ago

A HTML5 port powered by asm.js would probably work, and would rid us of any future copyright issue code-wise.

mstefarov commented 9 years ago

I'm afraid asm.js is not magic, and Java+LWJGL cannot be compiled to asm.js

tyteen4a03 commented 9 years ago

Well a port is a port.