Rinn
Developer
I cracked open that jar and the manifest looks fine:Java 8u102 is about 5 years old, although I can't imagine there were any critical bugs that caused manifests to be unparseable.
I suppose, if you're feeling really ambitious, you can try unzipping the jar (easiest way is probably to rename it as a .zip) and opening up the META-INF/MANIFEST.MF file, to see if that has Build-Revision: 25709 or whatever. If not, that points to a problem with the jar you're getting, not your environment. If it does, then back to the drawing board.
Code:
Manifest-Version: 1.0
Main-Class: net.sourceforge.kolmafia.KoLmafia
Build-Revision: 25709
Build-Branch: HEAD
Build-Commit: 203da09183f1d00c2f9b2e6392fa252a90870dc8
Build-Jdk: 16.0.1 (AdoptOpenJDK 16.0.1+9)
Build-OS: Linux amd64 5.11.0-37-generic