Closed linuxgurugamer closed 6 years ago
Need an example.
working on it, the one I was looking at had a bad file in github :-(
Closing issue, was a bad file. sorry
Ok. got it to happen again: CKAN 1.23.0 KSP 1.3.1 Mod: Custom Barn Kit It installed 1.1.17.0, even though the ranges were from 1.4.0 to 1.4.1
{
"NAME": "CustomBarnKit",
"URL": "https://ksp.sarbian.com/jenkins/job/CustomBarnKit/lastSuccessfulBuild/artifact/CustomBarnKit/CustomBarnKit.version",
"DOWNLOAD": "http://forum.kerbalspaceprogram.com/index.php?/topic/109027-/",
"VERSION":{
"MAJOR": 1,
"MINOR": 1,
"PATCH": 17,
"BUILD": 0
},
"KSP_VERSION": {
"MAJOR": 1,
"MINOR": 4,
"PATCH": 1
},
"KSP_VERSION_MIN": {
"MAJOR": 1,
"MINOR": 4,
"PATCH": 0
},
"KSP_VERSION_MAX": {
"MAJOR": 1,
"MINOR": 4,
"PATCH": 1
}
}
That's just the min version being hard coded in the netkan:
thank you
Specifically, if a .version file for a mod is only listing a specific KSP version, ie: 1.4.1, and I start CKAN on a 1.3.1 version game, it is showing me that mod as being available for the game
This is a critical error and is part of why people don't trust CKAN.
This happens to be on a Windows 10 system
I'm in the middle of adopting KSP-AVC, and can help you with the logic, if you need help.