Closed silas-hw closed 3 months ago
Turns out it's to do with asset loading! You can't get a list of files or sub-directories from a class path - which is what assets are put in when built to a jar!
I had to do some hackey way to dynamically load in assets without knowing every asset directory beforehand, but it works.
Since asset laoding is only done once, at the start, this isn't a huge problem.
Canary builds show that a 'main class' isn't present in the jar
Also this initial issue was me being stupid but lead me to finding the other problems. The 'main class' wasn't showing because I was running the jar as a java program and not a jar (I forgot the -jar
tag)
Canary builds show that a 'main class' isn't present in the jar