enneract

So you aren't going to touch the textures either? Not even sure what this is supposed to mean.

See quoted post.

Modern versions of MKS do not use Kethane, they use ORS.

The latest version of SweetFX is incompatible with modern windows operating systems.

Try This 10char

StripSymmetry totally works. It gives you a window of every part currently attached to the vessel in the editor and lets you remove symmetry flags from any of them. By your description, it is *exactly* the mod which you used before.

Where does one find 'your onedrive'?

The decoupler on the avionics ring does not seem to function on linux 64-bit. Not just an issue of no force... there is no decoupling at all.

You want a mod called StripSymmetry

I don't use KCW or SM, but mine corrects the stock behavior of causing resets every time you update the ship. The randomization is an optional feature.

Check out the mod in my sig, might be useful to you.

I believe this is intended to prevent unintentional downgrades when the user installs a mod with an older version of ModStatistics, which is a flaw which is present in Firespitter, though bypassed by MM using a different file name per version (which has its own flaws (requiring user intervention to curate installed versions)).

Think this one through for a second, seriously. For the sake of arguing this particular point, accept the premise that ModStats *is* opt-out instead of opt-in. ModStats comes bundled with a variety of other mods. ModStats has (optional) auto-update functionality. The relative values of that design decisions are not what I'm asking you to think through, but rather your complaints about the *implementation* of those decisions. Ok, so, ModStats comes bundled with other mods. It negotiates among each of the ModStats dlls to find the one which should be active. Cool! Now throw the auto-update wrinkle in. Our user has decided to enable it. Where does ModStats write the updated DLL to? One answer is... to where ever the most-current DLL is running itself from. Ok, that works, but if the user uninstalls that mod, we have to update again. Doable, but not elegant, and potentially adds noticeable time to the user's game loading (unlike the negotiation, which adds nanoseconds). The elegent answer is... to a central location - and hell, if we are doing that, why don't we move the most-current version there? (And thus, the illusion of 'automatically re-installing' is born). Next, ModStats is opt-out. How would you like that opt-out preference to be stored? Well, if KSP was windows-only, we could write it to the registry (which is the preferred 'windowsy' way of doing something like this). Can't do that on Linux or OSX, and it breaks KSP-mod convention (which is to use .cfg files). Where do we put that .cfg file? Well, the normal place is with the .dll file that reads it. But... ModStats can be in a number of different places, and we want *all possible* versions of ModStats to notice that the user has opted out, because we respect the user's privacy. The only possible options then, are to either put the cfg in a central location (/GameData/ModStatistics/), or literally scan every single .cfg file in GameData looking for that key. If we took option 2, and stored a cfg with the opt-out alongside some particular instance of ModStats, rather than a central one, the risk is run that the user could unintentionally remove their opt-out status by uninstalling a particular mod which included modstats. *EDIT* - I want to point out that my use of the word 'we' is an ideosyncracy I have about walking through code or program design, it is not intended to imply that I had any role in the design or creation of ModStatistics.

Idk about the rest of the modding community, but I make mods for myself. I'm doing (the proverbial) 'you' a favor by allowing you to use it.

It emulates the 'media keys' present on many keyboards. It looks like it will control whichever player your OS decides it should, in that context.

-snip- Your point here is predicated on the (false) assumption that a commercial operation can do a better job of data security than an individual. The same tools that are used by Steam and Squad to secure their website are used by even rank amateurs. A zero-day for Apache is a zero-day for Apache, etc. Again, you are complaining that you are suffering the consequences of abrogating your personal responsibility. Translation: I want someone else to choose for me what kind of content is allowed in mods, because I'm too lazy to practice basic, common-sense 'computer hygiene'.

Yes, absolutely necessary. Those statements are *true*. What can be destroyed by the truth, should be. Let's be clear here, though - I'm not calling *users* idiots, I'm saying that they seem to expect to be able to behave *like idiots*. There is a difference.

Fair enough, though interpreting an automatic update mechanism as a sinister plot is... reaching, at best. Again, this is pretty standard. Most commercial software's auto-update mechanism functions in a similar way. You should probably immediately remove any software which communicates with the internet, including KSP's Launcher and Steam. Uhh, yea, I think reading a forum post before you download software is perfectly reasonable. If you download a mod which includes modstats, you are getting 'exactly that mod and nothing else' because modstats is *a part of that mod*. Just because you *WANT* to behave like an idiot does not mean that the world must bend to accommodate your whims. No disagreement. I think ModStats was probably a bad call. I just think that the arguments against it are puerile, fallacious, and ridiculous.

You admit that you did not practice due diligence. Your complaints are invalid.

That is the automatic update mechanism, which IS opt-in. I'm not sure where you get this 'It can be pointed at anything on any website and the DLL will download and save it anywhere on the drive KSP was installed to' nonsense. It downloads the newer version of the DLL specified on the update server, and places it in a specific location.

No. Read the thread. You have old contracts from a previous version.

Negative mass! Quick, build a hyperdrive!

That isn't a 'flaw', that is the whole point. If you can't be bothered to read the description for what you are downloading, you gave up your right to complain about it when what you downloaded does what it says on the tin. Nobody said anything about 'bad people', just people who have abrogated their personal responsibility. non sequitur Not relevant? I'm simply talking about people who fail to read the plain description of what the author claims the download does. You get into the realm of malware when you are dealing with software which not actually do what it claims to do.

If you can't be bothered to read what a file that you are about to download does, you have no buisness downloading that file, end of story. Every mod that includes modstatistics clearly states that it includes it, and at the very least contains a link to the modstatistics thread which clearly explains what modstatistics does, and how to disable it. At that point, you have the choice to not use that mod, or to follow the simple instructions to disable it. Anyone who neglects to perform this basic step of computer 'hygiene' has no buisness downloading files, much less installing mods. Anyone calling modstatistics 'spyware' is indulging in pointless histrionics.

I had considered it, but I don't necessarily want to completely automate auto-crewing. There should be some thought involved, and that involves the user choosing which kerbals should be on a flight. Fortunately, if you have this mod installed, you dont have to worry about that choice resetting