blizzy78

On the topic of "stupidly high inclinations," I'd like to contribute this fine video. It tries to explain why you generally don't see such high inclinations in the real world.

ha, good point

Personally I don't like the "rename" way to simulate branches, let alone the fact that saving the craft overwrites previous revisions (in stock.) I imagine a way for the plugin to show me a graph of revisions for a particular craft (its revisions and branches), and I could just select one and hit "load". I would be fine if the plugin provides a completely different way of saving and loading craft, so that I wouldn't use the regular save/load buttons anymore. It's just another way of doing things. Right, with that in mind, it is probably better to not modify previous commits. Not sure if that's time well spent, but of course that's your decision.

Are you planning on adding branching support? I believe that together with the ability to enter custom commit messages, branching can be very useful in iterative design. It should come with some visual representation of the particular branches for a given craft, though. I also think that branching should be used and visualized as per-craft, while of course internally it would be per-savegame (because there is one repository per save game.) Additionally, it should be possible to edit past commit messages, for example to add additional comments. Since the repository is only local, messing with its commit history shouldn't pose any problems.

You know you did it when they go and make a tribute video of you.

The repository in your save folder maintained by this plugin should be a regular Git repository, so you could always add a remote yourself and then push, even if KSP is running at the same time.

If the author doesn't want you to include it in a mod pack, they could have said so by using an appropriate license. For example, check the Kethane license - it clearly states that you may not distribute it yourself, which includes mod packs.

That would require an online repository, such as on GitHub. But the idea is really interesting, especially since GitHub has an API that can be hooked into.

If the readme or the license says you can do it, why ask? It's a waste of time.

This has nothing to do with the plugin. Also, to zoom back in, you can just enter map mode, then exit map mode again.

May I recommend my engine cluster calculator. (see signature)

The calculator is only intended to produce lifter setups. I take it you don't want to go into low Kerbin orbit, but go higher up. In that case it might be easier to just add an additional transfer stage that takes you from LKO to a higher orbit. As far as the calculator is concerned, that transfer stage would factor into the payload. Yes. "Best TWR" will give you the result of all possible combinations that has the best TWR, while all other parameters must still be met. Of course "best TWR" doesn't have much use, since the specified range must still be met. I just put it in there regardless. The other options are more interesting. I don't think I will add anything complicated. Perhaps an interesting choice would be something like "best Isp @10 km" or something like that, but not averaged over the entire ascent. Yes, for one, widening the restriction for a specific center stack size opens up alot of engine combinations, so calculation time is definitely an issue here. Second, you may want to impose such a restriction for whatever reason.

This looks useful. As others have stated, it should be a partless plugin. Also, it would be nice if the button could be integrated into the Toolbar Plugin.

Hmm, I just use my own backup software. Not KSP-specific, of course

Regular-click the download link in the OP, then select File > Download in the menu on that page. In the Google Drive menu, not the right-click menu of your browser. Granted, the system to download from Google Drive is idiotic at best.

You might want to try the Fusebox plugin.

Toolbar Plugin 1.4.2 is now available for download.

Toolbar Plugin 1.4.2 is now available for download.

How so? What exactly prevents me from uploading a DLL that deletes all your files? Which is the point of this thread.

Needs more information. Define "froze". Provide output_log.txt.

Not necessarily, you can also cache the result for X days, at the expense of security, of course. But since revocations shouldn't occur all too often, this might be an acceptable compromise.

I'd rather have this as a requirement. Self-signed DLLs wouldn't contribute to a "secure" feeling in the sense of auditing, but at least the user can be sure that the DLL comes from the respective author rather than a third party. Of course each user could disable any checks for self-signed certificates. Also, certificates used to self-sign DLLs should be signed by the auditing team/mod/quorum/...

Guess what I did just yesterday.

Please check that there is exactly one Toolbar.dll that lives in GameData\000_Toolbar\. Delete any other Toolbar.dll you can find.

It is. I've verified that the achievement works as intended for the location you gave.