Superfluous J

Agreed. My only addition is that you should never untertake something like this for others. If you're not doing it for yourself it'll never last.

I would hazard they used it because Minecraft did

If I'm coming down just over dangerous velocity (7-8m/s on land) I ditch it to hopefully slow down enough to not lose anything else.

I've never had a crash related to the number of mods I've installed. During the 32-bit era, I never put enough to hit the limit. Now, I've never done enough to max out my computer's memory. It helps that I almost never install part packs or visual mods. I'm on one of my most unique runs through the game right now, having both JNSQ and ReStock installed.

Nothing. The irony was in the statement I quoted. I may have misread it, now that I read it again months later. At the time I seem to have thought it at least implied that KSP had anti piracy measures, which to me seemed a leap from the very accurate statement that sharing copies was illegal.

Did you get the "rendezvous 2 craft in orbit of Kerbin" contract, and complete it? You basically do whatever you did there, but in Mun's SOI. Note that the two craft can't have launched together (so you can't just undock and be like "yay we rendezvoused!") but neither has to be newly launched. If you have 2 ships in orbit of Mun already, and they didn't launch together, they can rendezvous. Likewise, you can send up a new ship to rendezvous with a ship already in orbit of Mun. Assuming you don't know the fundamentals of rendezvous, there are many tutorials out there but this one is mine. Step 3 is docking so you can skip that one... for now. Rendezvous (getting your craft close): Approach (getting them stationary and close): Docking (getting them REALLY close):

I like this idea. Instead of KAC, the do-everything-you-can-by-eye player in me thinks instead you should have 2 such craft, one matching orbits with Mun (i.e. equatorial) and one Minmus. Then you can very easily just see where they cross and launch when your space center is under that point.

The only place to get 1.7.0, or any version of the game other than the last released for each 1.x version, is from Steam or your own personal local backup. As you don't have either you're sadly out of luck. Your only option is to wait for Kopernicus to update. Actually you have one other option, you could install 1.6.1 and find a version of Kopernicus for it. Assuming one exists. Or 1.5.1, 1.4.3, etc.

Not really a career setting but I consider it one, I disable rescue contracts and use a CustomBarnKit config that does nothing but set the price to hire a new Kerbal to a static amount.

https://www.google.com/search?q=balance+beam&tbm=isch

This thread is really really old but IIRC is where NBTC came from originally. I even made a few textures my own self, though I rarely used anything but the default. Anyway, at the start there is some discussion as to how the game loads the texture. Not sure if it fully answers your questions or is even relevant anymore.

Check out Texture Replacer:

People keep saying this but it's not happening to me. I just docked a ship to a station, neither docking port was REMOTELY close to the COM of either, and I was switching back and forth between them multiple times making sure the ports were each targeting the other (manually, I don't have the SAS option) and both of them targeted the other craft's correct docking port just fine.

AHA! There's a thing. Yeah it is pretty niche which is why I didn't think of it. But yes you can't make maneuver nodes without a comms connection, if all you have in the command pod is non-pilots. Thank you. I feel better now about the built in antennas

When you "review data" on a ship with a lab you should get a 4th option in addition to the normal 3. That 4th option is to process it in the lab. That's about it, other than making sure there are scientists in the lab and you have tons of time, and you transmit it from time to time.

When you switch away from your station to the approaching craft, the station will still hold its active sas mode. If you told it to aim at the target it will continue to do so. You can test this by wiggling your craft back and forth and observing that the docking port on the station follows it. Then really your only choice is to turn SAS on and then do all the work with the approaching ship. Well there is one other choice. Set the target port to hold one of the two normal directions, and tell your approaching ship to do the same with the other direction. Those two points on the navball are unique in that they do not wander over time like the -grade and radial points, so once you get that heading on your ports, they will be guaranteed to be aimed perfectly at each other. Then you can do the actual translations with RCS.

define "easiest" I have found controlling from the docking port and locking hold to target to be helpful but only if you're coming in straight to begin with and don't have any lateral motion. If you can't lock to target, I'd say just turn on SAS and do all the work from the docking craft, that you hopefully made as nimble as is necessary.

If I could only ask one question I'd not expect much from these aliens. So I'd go for the joke. "AGAIN!?"

It's one thing to say we might discover another planet. It's another to hide the existence of the game's equivalent of Mars from its inhabitants. However in the gameplay vs realism continuum, this looks like some fun gameplay. And you can't reasonably expect someone who installed ResearchBodies to want all the planets to be already discovered by default.

In what situation would your rocket act differently without the in-pod antenna? 1) Pilot on board. He can fly it. Antenna doesn't matter. 2) Non-pilot on board. They can't turn on SAS but can steer. Antenna doesn't matter. 3) No one on board. No control, antenna or not. 4) Probe core attached. It has an antenna of its own, pod antenna is redundant. 5) ...? I actually don't know. I've never used KerbNet except on satellites to place biome waypoints and find anomalies. Do pods even have Kerbnet access? I literally don't know. At least it's a reason, I suppose

In the meantime, you can edit the .craft or .sfs file (depending on if this is in the vab/sph or if it's in a ship in flight) but that's kind of an extreme fix.

A discussion about transmitting the new Breaking Ground science got me to thinking. We basically have 2 types of antennas for ships in the game (3 if you count relays but they're not pertinent right now). Built-in and add-on. The built-in ones are distinct from the add-on ones in 2 ways: They are built in (duh) to every command pod and probe core. Without exception. They cannot transmit science but do allow for probe control. Is there something else, though, that the built-in antennas can do? I cannot think of one but I'm very often wrong. And if there is nothing else they do, why do command pods have them? You can't remote-control a command pod so the antenna won't be allowed it's intended purpose there.

Well they power entirely differently so hey

Yes. I put a couple on the ground at KSC with just a controller and power and they transmitted their meager science returns with no issues. If the antenna couldn't transmit science it'd be useless, as you can not fly them or attach them to a rocket

Yikes how far out did you travel? I haven't waited nearly that long, though I recall the potential with some planet packs I installed but never fully explored.