Caused by: java.lang.UnsupportedClassVersionError: zsawyer/mods/mumblelink/MumbleLinkImpl : Unsupported major.minor version 51.0
Minecraft Version: 1.7.10
Operating System: Mac OS X (x86_64) version 10.9 Java Version: 1.6.0_65, Apple Inc.
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Apple Inc.
It seems like Minecraft is started using Java 6. You will need to update to Java 7 for this mod to work.
hey i have read the page and I saw I have to do a request for my operating system in the readme I'm on osx 10.7.5.
it would be really really awesome if you will make a version for mac! when you have time of cource...
bye
Hi asneep,
I am not sure where in the readme you have found that information but OSX support has been there since version 2.3.3 of this mod. I just cannot test if it still works.
To be honest I am not a MAC fan and the stupid apple license that forbids cross-compiling for OSX is simply a slap into the face of developers. Making it impossible for non-MAC-users like me to provide you with anything at all - even if I could it would be illegal for me to compile the code needed.
So either you are lucky and the library still works or someone else with a mac has to compile it for "us".
But really nothing major has changed on that library, so there really is no reason why it should not work anymore (except for apple not being backwards compatible to fat dylibs).
The most common problem is that OSX users are using an old java6 while this mod needs java 7.
If you followed the link you should have seen that you can post the crash log of minecraft and we will see what the actual issue is. The general remark that it crashes is impossible to debug. More information is required. And I doubt that the library is not compatible with newer versions of OSX anymore. So post your log.
If possible, may you provide a JAR for MAC? If you have, we are having crash problems. However, I do not see support for Mac. Only Linux and Windows. I told him to get a PC!!
The provided jar is only tested for WIndows 7 64 bit by me. However, Ubuntu and MAC OSX should still be supported as nothing in that regard changed. Please have your friend post the crash log (he/you can use http://pastebin.com for that). A common issue is that Java 1.7 is required for my mod.
The sounds works the same as if we weren't using the mod. (Sorry I took so long to say anything else)
Hi MarsGem,
I am sorry to have skipped to reply, but to be honest I am stumped. If you both are getting the confirmation messages "Minecraft linked." and "Mumble linked." then it really should work. I am suspecting that there is either a setup problem with Mumble or a driver issue that prevents Mumble from providing 3D sounds.
Have you looked at the minimum volume value as suggested in my previous post?
Which Operating Systems are you using?
Where do I download the "Mumble for Windows" shown the the installation tutorial video?
This is weird, I thought I'd linked it. You should go to http://mumble.info and download the version appropriate for your Operating System. It will redirect you to a SourceForge download. You can get different versions there too: http://sourceforge.net/projects/mumble/files/Mumble/
Could you please update this to 1.8 as soon as possible? The Forge 1.8 just came out.
My work life is taking priority and burning me out at the end of a day. I barely have time or incentive to even check the forums as you can see. I'll try to find a slot for it. Maybe this week - if not... then probably not before Christmas.
No I have not heard of Mekanism and I must say the walkie-talky seems sweet. I had a look at the code (because they are open-source as well) and found that they are implementing the voice chat themselves, based on the javax api. To get attenuation and positional working one could possibly upgrade their implementation. But it seems like there won't be much to reuse from my mod. Most of it would be completely new code and using codecs like mumble does would be another story.
Is it possible? Yes, it seems like it.
Will I do that? Probably not. - Don't have the time for it.
I'm trying to use your mod and it seemed fine in the videos. We did every you said, but our voices don't fade even when were several hundred blocks away. I have no idea how to fix this, because it says Minecraft Linked and Mumble Linked, but nothing.
This sounds strange. Do you only have issues with the fading or also with the directional aspect? That is: Can you hear that your friend is for example left of you?
If directional is working but attenuation is not, check the Minimum Value (it should be below 30%, else you might not hear the effect.
Hey man, a group of my friends are trying to use mumble for 1.7.10 - there's 3 people who use Mac computers, and they've followed the install you guys have recommended, but when they open the forge profile the game crashes instantly.
Any suggestions?
Make sure they are using Java 7 or later.
If this still does not work you/they will have to post their crash log so we get some more information about what the real issue could be.
Without logs it's guess work. Please see the Support section.
It requires Forge and I am not aware of a Forge release for 1.8. You can always try and see if MC crashes - this mod doesn't modify anything so when you have a working Forge it's safe to simply install it and see if it works.
Yeah, I switched the active repo from SF to GitHub. I keep SF to host the artifacts because GH doesn't provide that anymore. So the SF repo is not always up-to-date - I do try to sync it from time to time though.
I will definitely try to see if I can get your build script to work even if it means I need to restructure my repo. Have you seen that I was using a sub-project structure? That would have to go away, right?
Thanks for taking the time and addressing my issues. Why would I think this is a slow reply? It is really appreciated!
It is good to get to understand why design decisions were made and helps me consider pitfalls with my approaches. So thanks for that in-depth discussion.
Your analysis is quite accurate and considering the path I took (MCP -> MCP+ML -> MCP+ML+Forge -> ML+Forge -> ForgeGradle+ML+Forge -> ForgeGradle+Forge and now ForgeGradle+Forge+LL) you are right, going to MCP+LL would feel like a step back which is why I am happy that there is the LL plugin for FG. So yes, I know that those tools and yours are taking a lot of the tedious work away and I am grateful for that. Remembering that a release took me several hours just to reobfuscate the mod when MCP updated and now it is almost at a point where it automagically builds on a hosted CI... Which is why my expectations are so high I guess.
3. Regarding the API-Jar: The nice thing about that would be that it would work outside of MCP because separated interfaces like that do not need obfuscation. It is my understanding that if you provide those all a dev would have to do is insert the jar into the MCP's jars or lib folder and compilation would run without issues and without having to deobfuscate because those are not obfuscated. But I could be wrong here. Maybe the decoupling from MC is not strong enough for that.
4. I am not against the MD5 procedure at all I was just afraid that not running this procedure prevents me from successfully testing the dev build. But if that is not the case, then all is good.
6. I understand that support is time consuming and we all are doing this in our free time so any documentation or support is already nice. The tutorials help with avoiding the support ping-pong of asking questions back and forth. Your videos are great and already helping there but to be honest videos are a horrible resources to go back to and look something up again
2. About the .litemod-extension: I imagine I could also tell my user base to rename their .jar file into .litemod but with each setup step the chance of installation failure increases. I have very little posts in my thread because the Installation just works, I'd like to keep it that way . The checkbox or config file entry is another setting the users could miss - but yes that would be a workaround for hybrid jars in general I guess. Although if Killjoys' recommendations work I might just ship two (different) files after all.
Regarding this problematic of loading bad or conflicting jars: Have you considered using a custom class loader as a sandbox environment and only transfer the valid jars to the main class loader? Just an idea.
Killjoys' replies gave me hopes that this can actually still work out nicely even at the current state that initially I found so problematic for my approach.
0
Check this out: https://docs.oracle.com/javase/7/docs/webnotes/install/mac/mac-preferences.html
Also note that you should be able to change the $PATH or $JAVA_HOME environment variable to point to jre7 instead of 6.
0
Thanks for posting your log.
I have found the problem:
Caused by: java.lang.UnsupportedClassVersionError: zsawyer/mods/mumblelink/MumbleLinkImpl : Unsupported major.minor version 51.0
Minecraft Version: 1.7.10
Operating System: Mac OS X (x86_64) version 10.9
Java Version: 1.6.0_65, Apple Inc.
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Apple Inc.
It seems like Minecraft is started using Java 6. You will need to update to Java 7 for this mod to work.
0
Or click on the Download button in my signature (you will need to scroll).
0
Hi asneep,
I am not sure where in the readme you have found that information but OSX support has been there since version 2.3.3 of this mod. I just cannot test if it still works.
To be honest I am not a MAC fan and the stupid apple license that forbids cross-compiling for OSX is simply a slap into the face of developers. Making it impossible for non-MAC-users like me to provide you with anything at all - even if I could it would be illegal for me to compile the code needed.
So either you are lucky and the library still works or someone else with a mac has to compile it for "us".
But really nothing major has changed on that library, so there really is no reason why it should not work anymore (except for apple not being backwards compatible to fat dylibs).
The most common problem is that OSX users are using an old java6 while this mod needs java 7.
If you followed the link you should have seen that you can post the crash log of minecraft and we will see what the actual issue is. The general remark that it crashes is impossible to debug. More information is required. And I doubt that the library is not compatible with newer versions of OSX anymore. So post your log.
Snipe.
0
The provided jar is only tested for WIndows 7 64 bit by me. However, Ubuntu and MAC OSX should still be supported as nothing in that regard changed. Please have your friend post the crash log (he/you can use http://pastebin.com for that). A common issue is that Java 1.7 is required for my mod.
Hi MarsGem,
I am sorry to have skipped to reply, but to be honest I am stumped. If you both are getting the confirmation messages "Minecraft linked." and "Mumble linked." then it really should work. I am suspecting that there is either a setup problem with Mumble or a driver issue that prevents Mumble from providing 3D sounds.
Have you looked at the minimum volume value as suggested in my previous post?
Which Operating Systems are you using?
0
This is weird, I thought I'd linked it. You should go to http://mumble.info and download the version appropriate for your Operating System. It will redirect you to a SourceForge download. You can get different versions there too: http://sourceforge.net/projects/mumble/files/Mumble/
My work life is taking priority and burning me out at the end of a day. I barely have time or incentive to even check the forums as you can see. I'll try to find a slot for it. Maybe this week - if not... then probably not before Christmas.
Please read http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/1272675-1-7-10-mumblelink-forge-smp-lan-mumble-realism#support
0
1
Is it possible? Yes, it seems like it.
Will I do that? Probably not. - Don't have the time for it.
0
0
you might have java 7 installed, but Minecraft is not run with it, see the log: Java Version: 1.6.0_65, Apple Inc.
I don't know how you can convince the MAC but setting system variables $JAVA_HOME to the 1.7 directory or your $PATH to the jre1.7/bin might help.
0
This sounds strange. Do you only have issues with the fading or also with the directional aspect? That is: Can you hear that your friend is for example left of you?
If directional is working but attenuation is not, check the Minimum Value (it should be below 30%, else you might not hear the effect.
0
Make sure they are using Java 7 or later.
If this still does not work you/they will have to post their crash log so we get some more information about what the real issue could be.
Without logs it's guess work. Please see the Support section.
1
It requires Forge and I am not aware of a Forge release for 1.8. You can always try and see if MC crashes - this mod doesn't modify anything so when you have a working Forge it's safe to simply install it and see if it works.
0
Yeah, I switched the active repo from SF to GitHub. I keep SF to host the artifacts because GH doesn't provide that anymore. So the SF repo is not always up-to-date - I do try to sync it from time to time though.
The previously linked GH repo is a feature branch including the changes made to support LiteLoader.
I will definitely try to see if I can get your build script to work even if it means I need to restructure my repo. Have you seen that I was using a sub-project structure? That would have to go away, right?
0
It is good to get to understand why design decisions were made and helps me consider pitfalls with my approaches. So thanks for that in-depth discussion.
Your analysis is quite accurate and considering the path I took (MCP -> MCP+ML -> MCP+ML+Forge -> ML+Forge -> ForgeGradle+ML+Forge -> ForgeGradle+Forge and now ForgeGradle+Forge+LL) you are right, going to MCP+LL would feel like a step back which is why I am happy that there is the LL plugin for FG. So yes, I know that those tools and yours are taking a lot of the tedious work away and I am grateful for that. Remembering that a release took me several hours just to reobfuscate the mod when MCP updated and now it is almost at a point where it automagically builds on a hosted CI... Which is why my expectations are so high I guess.
3. Regarding the API-Jar: The nice thing about that would be that it would work outside of MCP because separated interfaces like that do not need obfuscation. It is my understanding that if you provide those all a dev would have to do is insert the jar into the MCP's jars or lib folder and compilation would run without issues and without having to deobfuscate because those are not obfuscated. But I could be wrong here. Maybe the decoupling from MC is not strong enough for that.
4. I am not against the MD5 procedure at all I was just afraid that not running this procedure prevents me from successfully testing the dev build. But if that is not the case, then all is good.
6. I understand that support is time consuming and we all are doing this in our free time so any documentation or support is already nice. The tutorials help with avoiding the support ping-pong of asking questions back and forth. Your videos are great and already helping there but to be honest videos are a horrible resources to go back to and look something up again
2. About the .litemod-extension: I imagine I could also tell my user base to rename their .jar file into .litemod but with each setup step the chance of installation failure increases. I have very little posts in my thread because the Installation just works, I'd like to keep it that way
Regarding this problematic of loading bad or conflicting jars: Have you considered using a custom class loader as a sandbox environment and only transfer the valid jars to the main class loader? Just an idea.
Killjoys' replies gave me hopes that this can actually still work out nicely even at the current state that initially I found so problematic for my approach.