blizzy78

Everyone is entitled to their opinion, I guess.

I'm sorry, my mistake. Yes, the VoiceCommander.dll is required. No, the VoiceCommanderMechJeb.dll is not required.

Also, "not naming names" is not exactly helpful this time

Please make a copy of voiceserver.exe somewhere outside of KSP, then start that copy. After that, start KSP. Do not start the voiceserver.exe copy inside of your KSP folder. This seems to be a problem on some versions of Windows. For example, it does not occur on mine.

Works fine for me. Can you give more details?

It is not. Check this thread for discussion.

It would be quite silly to just delete the local copy But I agree, the rule is not specific which data has to be deleted on request.

Please read the change log. Also, post #2000 - yay.

Thanks MrWizerd, very kind of you.

Voice Commander 1.3.1 is now available for download. Note: If the download page is linking an older version for you, press F5 in your browser.

Ambient Light Adjustment 1.1.2 is now available for download. Note: If the download page is linking an older version for you, press F5 in your browser.

Achievements 1.6.2 is now available for download. Note: If the download page is linking an older version for you, press F5 in your browser.

Precise Node 0.14 is now available for download. Note: If the download page is linking an older version for you, press F5 in your browser.

Toolbar Plugin 1.7.5 is now available for download. Note: If the download page is linking an older version for you, press F5 in your browser.

Toolbar Plugin 1.7.5 is now available for download. Note: If the download page is linking an older version for you, press F5 in your browser.

Then the rule must explicitly state that.

I think so, at least the rule says something like that: I don't see how that would work without a window of some sort that is always visible.

Which, of course, is really bad when it comes to rules. If you want everyone be treated equally, you can't have ambiguous rules. How would that look like? Always open a window at the main menu so that you can revoke your opted-in permission? ----- Back to the rule in question - I'd also like some clarification on whether it is required for mods to function unchanged if the user opts out of sending data.

Okay, everyone has their opinion, I guess. But let's not turn this into yet another discussion thread

I'm waiting for what's to come with KSP 0.24.1 - you did announce some changes in #kspmodders.

As it is, the whole "sending data" is ambigious. What exactly constitutes "sending data"? Is an empty HTTP request to some remote server "sending data," although the actual payload is empty? In order to get information from the outside, there has to be some request. I'd like for this to be clarified in the mod posting rules. Edit: Also, is it "opt-out" or "opt-in"? The rule mentions both. I'm confused.

I've noticed a typo in the change log: "Grant Tour" should read "Grand Tour". Not sure if that typo is in the actual plugin as well since I don't use it.

The thing is just that Crew Manifest only works in the flight scene (if I remember correctly.) Yet, it advertises to the Toolbar Plugin that its button works in all scenes. But when you click on it in the VAB for example, just nothing happens. This is a bug that should be fixed in the Crew Manifest plugin. (Although I think it has been superseded by the Ship Manifest plugin.)

First, I believe it is a bug in Crew Manifest in that it allows you to make its button visible in all scenes instead of just the flight scene, but the plugin only works in the flight scene. Second, about the functioning (or not) of Crew Manifest, that should be a bug in that plugin as well.

You might want to read up on the forum rules.