The new launcher runs a checksum comparison when it is started, to determine whether the current installation is up to date or not, or if it contains any corrupted files.
The problem that arises from this is, that it makes it impossible to install clientside mods, as the launcher will detect a checksum mismatch and thus not permit the modified game to be launched.
The previous launcher worked with checksums too, however it only compared them, when the user ordered the launcher to update, to determine whether or not an update was necessary, the it relied on the information in the version.txt
I request a way to at least manually excempt certain files from this check, or to disable the initial check, and only perform it when an update is necessary.
Description
Details
- Task Type
- Feature
- Affected Gamemode(s)
- none/unspecified
- Reproducible
- uncertain
- Category
- Launcher
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
Related Objects
Event Timeline
Another interesting thing would be to integrate modding into the launcher by being able to add mod-zipfiles, which's contents override the respective file in the installation folder. In case of the starmade.jar or other zipfiles have not the entire file overridden, but the zip/jar from the mod be merged into the zip/jar from the installation. In case of conflicts between mods, the user should be prompted to choose which of the overrides should be applied.
Fixing T739 resolved this issue as well.
Details: the startup version check updated the selectedVersion value, thereby triggering an unwated checksum scan due to the behavior described in that ticket.
-QA testing-
Fixed, with no reason to believe in the existence of not yet tested edge-cases.