The GithubRepositoryAdapter uses the engineVersion as the displayVersion. The list of releases in the UI is built from what it sees in the repositories. The installed files do have the right displayVersion, so they seem to not match.
We should think about Offline Mode (#198) while deciding how to address this. The fact that it depends on an online repo to tell us what is installed and ready to play locally is out-of-order.
During playtest today, I successfully installed and ran stable release 5.1.1.
After restarting launcher, it did correctly use last-played-version [or did it?], but it thought it needed to re-install:
Logs indicate that wasn't just a cosmetic thing, it did unzip the distro again when I hit the button.
Originally posted by @keturn in https://github.com/MovingBlocks/TerasologyLauncher/issues/646#issuecomment-894854510
Cause
https://github.com/MovingBlocks/TerasologyLauncher/blob/4327450c1ef751910cedd27698fe8d9955ab4e90/src/main/java/org/terasology/launcher/repositories/GithubRepositoryAdapter.java#L59
The GithubRepositoryAdapter uses the engineVersion as the displayVersion. The list of releases in the UI is built from what it sees in the repositories. The installed files do have the right displayVersion, so they seem to not match.