It has, I confess, been annoying week. One or two mod developers have already heard specific comments, sent direct. I have puzzled out a couple of things, but some of you guys can be more than a bit obscure. So I thought I'd try to make some helpful suggestions, rather than just ranting. 1: Building in help features is a good thing. But remember that the new user may not be starting quite where you expect. For an example of where this can be a needless puzzle, got look at the Wiki page at http://wiki.kerbalspaceprogram.com/wiki/Subassembly Ask yourself this. How do I make and store a sub-assembly? I had to do a lot of digging, in a maze of twisted forum posts, all alike, before I found a mention that you needed Advanced Mode. I eventually found that: click on the icon at the top-left of the VAB screen, an extra row vertical of icons appears at the left, and one of these switches to the sub-assembly mode. 2: When you have a Mod pack with a large number of parts, a list is helpful. Plain text is good, with the part-categories. Some part details are more useful than others. For a fuel tank, diameter and capacity. It's worth knowing the thrust of an engine. 3: For the more complicated items, has some key detail been missed? Be careful of revisions. There is one useful utility that does one job in two distinct steps. There's a primary window, and you have to use sub-window A to get to the target planet, before the useful semi-cheat in sub-window B. There was a helpfile in an earlier version, and I was able to read the source, and this was mentioned. It isn't in the current system. 4: It's probably useful for you as an author too: include a readme.txt file which details what the Mod does. Include which KSP version it is made for. Some Mods have dependencies. List them. Sometimes a Mod might not depend on a particular item but you won't get the full effect without itâ€â€you can do things with the Tech Tree, but Rockomax-sized boosters need Rockomax-sized tanks. None of this needs great literature. But. as with so much else in the world, the bottom 10% can be really bad, and not difficult to fix. I have seen a few related things in part.cfg files, such as description texts with a spelling error, and a decoupler labelled with the wrong size. That sort of error is why even professional authors have to deal with copy-editors. Believe me, you can be uncannily blind to your own errors. "Just Read The Instructions" is a great name for a ship to land rockets on, but somebody had to write the instructions.