MagicManICT wrote:Sevenless wrote:What I'd really like to know: Can loftar fix this? (whoever's fault it actually is)
Saying "oops, sorry, the most updated version of java doesn't work with my game" doesn't look good on Salem.
Maybe not. It may be an internal issue with Java that needs to be fixed by Sun, and any hacks or workarounds loftar does might need to be fixed yet again when the internal bug actually gets fixed. I hate these transitional periods like this because you have so many "early adopters" that have no hindsight and force people to upgrade to use their software. I realize that Java 7 has been out for over a year now, but as we can see, that's still not enough time to get all the bugs fixed. (Just doing a longer beta doesn't work, either, because people don't upgrade and then the bugs still don't get found.)
I agree with your sentiments, but that's a problem all developers have, especially when a new code base is out you're trying to be compatible with. Then again, this is a beta test just so these sorts of issues can be found and worked out. If that's still there come launch, then I will have to agree that it will look poorly on Seatribe. But then... you have publishers like Oblivion and look how buggy the Gamebryo engine (Fallout 3, Elder Scrolls) is.
I definitely agree this isn't SeaTribe's fault, the issue is they still lose potential longterm customers. Java 7 Salem is horrendous for crashing, and I wouldn't be willing to downgrade Java for a new game I found. Heck, I still use Java 7 and occasionally get a KO from hunting because of it.
Neat to hear the reason why it's going on. Thanks.