00:04 <ckanbot> [CKAN] HebaruSan commented on issue #2581: Looks like that's because that version is missing a period:... https://git.io/fpcmu

02:45 <ckanbot> [CKAN] linuxgurugamer commented on issue #2581: Crap. I'l just do an epoch, or can you fix the meta data? This is a problem on Spacedock, most likely I made a typo putting in the version. Cause there is no way that error can be made in the .version file https://git.io/fpc3H

02:50 <ckanbot> [CKAN] HebaruSan commented on issue #2581: Yes, we can fix the metadata. Do you want to fix it on SpaceDock first, or is it OK as-is? https://git.io/fpc3F

03:03 <ckanbot> [CKAN] linuxgurugamer commented on issue #2581: I can't do anything on spacedock other than deleting it and adding it back, which causes other problems. It can be left as is, as long as the meta data is correct.... https://git.io/fpcsU

03:17 <ckanbot> [CKAN] HebaruSan closed issue #2581: Allowing older versions be compatible has mod version for older KSP version override the current https://git.io/fpcmR

18:31 <ckanbot> [CKAN] HebaruSan commented on issue #2213: Another interesting possibility is a `$vref` for forum threads. Rather than trying to get *all* of the info about a mod from the forum, we could get most of it from the host with an existing `$kref`, and then just use the forum thread as the authoritative source for version info. This could have problems with getting out of sync, though, if a modder uploads a new version and forgets to update the forum thread