Take Command Mod in 1.4.4

[Klapaucius]

I've got the Take Command Mod installed. It works just fine in 1.4.4., but every time I start KSP, I get a message that I have an unsupported KSP version and that I need 1.4.1.

This is not a big deal, but not being a coder, I was just wondering what was going on.   It's interesting I get this message but the mod still works.  The forum for this mod is closed, so I assume it is not being updated?

[DoctorDavinci]

25 minutes ago, Klapaucius said:

I've got the Take Command Mod installed. It works just fine in 1.4.4., but every time I start KSP, I get a message that I have an unsupported KSP version and that I need 1.4.1.

This is not a big deal, but not being a coder, I was just wondering what was going on.   It's interesting I get this message but the mod still works.  The forum for this mod is closed, so I assume it is not being updated?

Use this one ... the mod changed hands and is now being maintained by another person

[Klapaucius]

@DoctorDavinci That's the version I am using. I doublechecked and re-downloaded it just to make sure. Same thing. It asks me to check for updates and simultaneously tells me it is unsupported. Again, it IS working in the game, so not a real problem.  Its just a bit of a hassle to continue click these messages during bootup.

 

[Xd the great]

Its caused by a modder forgetting to update their mod to tell the game that it is compatible.

No harm should come to you, as I have 3 mods that do the same.

[4x4cheesecake]

Well, you can remove the miniavc.dll from the mod folder to get rid of the message but you will not get any update informations for this mod anymore.

[Papa_Joe]

The cause is the .version file that is included with the mod.  Since the last time it was updated was KSP 1.4.1, the version file reflects that version of KSP.  KSP-AVC is the mod checking that file to determine if the mod is out of date.  If the mod works in later versions (as they often do), then the mod author (linuxgurugamer in this case) will not bother to update the mod as there is no compelling reason to do so.  Given that linuxgurugamer is supporting over 140 mods, I suspect that a working mod is very low on his priority list.

I would just ignore the warning for now.  If you really don't want to see it and you are brave, you can update the .version file that came with the mod  

From:

    "KSP_VERSION_MAX":
    {
        "MAJOR":1,
        "MINOR":4,
        "PATCH":1
    }

To:

    "KSP_VERSION_MAX":
    {
        "MAJOR":1,
        "MINOR":4,
        "PATCH":4
    }
 

If you do not see this entry in the file, just add it before the very last "}" in the file.

58 minutes ago, 4x4cheesecake said:

Well, you can remove the miniavc.dll from the mod folder to get rid of the message but you will not get any update informations for this mod anymore.

This is not necessarily true.  Since many mods include this file, you will likely find multiple copies in your KSP install.  It can be quite tedious to try to locate them all if you have a lot of mods installed.  Therefore the best solution is the one I described above

Edited July 20, 2018 by Papa_Joe

[4x4cheesecake]

16 minutes ago, Papa_Joe said:

This is not necessarily true.  Since many mods include this file, you will likely find multiple copies in your KSP install.  It can be quite tedious to try to locate them all if you have a lot of mods installed.  Therefore the best solution is the one I described above

I actually thought that avc will check the online version file so that editing the local file will not change anything...

Well, let me quote the miniavc description created by cybutek:
 

Quote

This plugin checks inside its current directory and all contained directories for version files.

I should have know from this description that you can edit the local version file to trick avc...but on the other hand, if you don't have miniavc installed in your GameData folder, it will only check the mod folder where it is located so you can delete it there and this particular mod will no longer be checked. I prefer to delete all the bundled miniavc.dlls and install full avc, but that's just my personal favourite

[Papa_Joe]

7 minutes ago, 4x4cheesecake said:

I actually thought that avc will check the online version file so that editing the local file will not change anything...

Well, let me quote the miniavc description created by cybutek:
 

I should have know from this description that you can edit the local version file to trick avc...but on the other hand, if you don't have miniavc installed in your GameData folder, it will only check the mod folder where it is located so you can delete it there and this particular mod will no longer be checked. I prefer to delete all the bundled miniavc.dlls and install full avc, but that's just my personal favourite

You are of course correct that the miniavc checked online when it was maintained by cybutek.  however, since linuxgurugamer took over maintenance of KSP-AVC I believe he disabled that feature.  So updating the local file should correct it.  I just performed a test on my local install and it works as I described.

Edited July 20, 2018 by Papa_Joe

[4x4cheesecake]

2 minutes ago, Papa_Joe said:

You are of course correct that the miniavc checked online when it was maintained by cybutek.  however, since linuxgurugamer took over maintenance of KSP-AVC I believe he disabled that feature.  So updating the local file should correct it.  I just performed a test on my local install and it works as I described.

Good to know!  I guess I can get rid of the EVE and SVE notification then

[Lisias]

I suggest to use KSP-AVC. I delete every MiniAVC.dll on my GameData (one less thing to bother), and rely on KSP-AVC to do the checking - it give you one report with all the issues found. A click in the "OK" button, and life goes on.

[DoctorDavinci]

There is always this to remove miniAVC  ... should work fine as is in ksp v1.4.4

 

Edited July 20, 2018 by DoctorDavinci

[Klapaucius]

10 hours ago, DoctorDavinci said:

There is always this to remove miniAVC  ... should work fine as is in ksp v1.4.4

 

That did the trick. What happens if I update?  Do I get any notice if things are no longer going to work?