Em yeah, as i said i am to stupid for linux so i have no idea what the issue is because i dont use it.
I have someone who got it working on linux but he is not online right now.
I can ask him if you want.
But i have no idea how to fix that. Sorry ^^"
@FriendlyPerson ok i got now 2 sources who suggested me that it might be because of OpenJDK,
They suggest that you try oracle java 8 instead because that ships by default with the JavaFX Library.
I just tried this with a fresh installation of Linux Mint 19.1 in a virtual machine and managed to reproduce the bug.
It seems like openjfx cannot be loaded if the default java version is java 10 (or java 11).
(all this still with openjfx installed and default java versions set via update-java-alternatives)
Just noticed something, you showed a screenshot of OpenJDK 8 instead of Oracle JDK 8, I might be just a Ubuntu User who happens to have Oracle Java 8 installed, but is the Oracle Version installable for Linux Mint too?
Version 1.3 released now:
Changelog:
Version 1.3:
Hey, I havent been able to add mods since I updated to 1.3.
Logs are empty but I recorded what the behaviour looks like.
(youtube, watch?v=KC2cozCw3RE)
@xt9 yeah we are aware of that issue. That was me something breaking in the code -.-"
That will be solved in the next patch.
Until then just import the mod into the repository and get it from there. (In the view repository you can add mods that way)
I came back to this when I got time to kill. I finally running this client (1.3v) as I speak and hopefully it will work form here! Basically this sounds weird but users should try to wipe their distro of Java (completely with the auto remove command) then reinstalling with the distro recommended sudo command THEN following up with the openjfx installation (it will add JDK again and a few other things).
That should at least get the client running!
Apparently the issue I had with that showing unrelated updates is that the mod were showing for 1.13.2 because the Double-Hi-Dpi or whatever interface scaling was too big for the app.
Also why isnât JEI updated already even though I am forcing the repo to update and linking the âquestion ableâ mod to the projectâs page? I literally cannot get this to work even though this was a âreleaseâ update.
After DUMPING the data contents and doing 800 cache size PLUS putting all of other mods it had finally EVENTUALLY accepted all of the mods I had. Phew I hope sooner or later it will be much easier than doing all of that.
Apparently the issue I had with that showing unrelated updates is that the mod were showing for 1.13.2 because the Double-Hi-Dpi or whatever interface scaling was too big for the app.
How is that even possible? Could you provide pictures of that because i can not even imagen what you told?
Also why isnât JEI updated already even though I am forcing the repo to update and linking the âquestion ableâ mod to the projectâs page? I literally cannot get this to work even though this was a âreleaseâ update.
Linking a Mod to the repository just starts to track it, and search for updates if needed.
The Update itself is only done if you are requesting it. Which you can do in the MainUI.
That is 1 button press and it asks you to which version you want to update too.
That is intentionally that way because blindly updating if a version is broken is not a good idea.
After DUMPING the data contents and doing 800 cache size PLUS putting all of other mods it had finally EVENTUALLY accepted all of the mods I had. Phew I hope sooner or later it will be much easier than doing all of that.
Why do you have to dump data to add mods. It could be that it does not know the mods, which it can not find out by just checking them, thats why precaching is a thing. Though the âAdd Mods to a Pack Via Curse Linksâ is at this moment broken but will be fixed in the next patch.
Other then that i ask you maybe to provide exact steps of what you did or a video to show how you did it to see if it is a issue of the software or a usererror.
Thanks for the report.
Below you will see the image of the Linux Mint Desktop Scaling set to this settingâŚ
See belowâŚ
Ahh I gotcha that all make sense now, thanks for further explaining the outstanding issue to me. Hopefully that will out sooner or later. As I believe that why there were this issue in the first place. Because even if I had to I could always point it right at the JEI new version if it doesnât âknowâ it yet.
So the Issue was that the Application didnt use a proper UI Scale? Yeah that seems to be a common problem with simple programs that use outdated Graphics Systems. Would definitely require some research to fix the UI Scale Issue.
Just trying to make sure the Issue is clear for both sides. 
Thanks. Yeah the scale thing is a bit of a trouble, the main issue with the âResize Optionâ is that it breaks the windows completly that are fixed in size for the whole reason that they are a fixed design that does not autoadjust to things. There is not a real layout for such things sadly.
A option that could be added is to unlock these windows optionally that they can be resized, though that is for âuse at own riskâ
About the other thing, we will see that the existing bugreports fix your issue. If not then we can dedicate time to fix it.
Thanks for the report.
You use Swing right? Add a Scrollbar Pane with horizontal and vertical scrolling at the outer most layer of your GUI if it doesnât support scaling, that way you can scroll around if needed, like when youâre on a small Screen, while keeping your fixed Size GUI Design.
You are welcomed, hopefully this get better and that Curse flipping reply to my tickets I put (they didnât even sent me where to update the existing so I had to make a whole new one as an âupdateâ to it). As they saying that the âmanifest.jsonâ doesnât exists and it may due to my error but I reuploaded it and it was auto rejected for the same reason).
So itâs worked as I expected but just make sure you do the followingâŚ
Update the Project ID of your page in the manifest.json and zip up the overrides+manifest.json themsleves instead of shoving them into a folder.
I just wanted to pass by and say thank you so much!
As a Linux user, building and maintaining packs was always a chore for me, not to mention formatting them to the curse format so my friends could download the packs.
And just like that, boom, problem solved.
So yeah there are still room for improvement and some functionalities are a bit unintuitive, but the things that are already there make up for it a thousand times.
Thanks again, and if i can be of any help troubleshooting things, let me know.
Did you export the pack? And if that was the case did you select âExport In Curse Formatâ? Because else it exports it into the ModPackManager Format to make things easier for the MPM.
Yeah thanks.
For the âUnintuitiveâ things, or issues in terms layouts etc it would be nice if you could throw in a couple examples. I will note them down when the next patch get started and try to improve these things.
Ofcourse if you have exact ideas how to improve things you can state that too and we can talk about that. If these things are possible, then I am happy to implement them.
