benjamg

@dagobert: Generally I've found just reconnecting to the server has given me more kerbals to play with in Career mode, however the fact the 'story line' contracts, other than the first three, only seem to be doable once per server rather than once per play made if very hard for players to get enough money to do anything. So it's not the only issue you'll face. Currently I play in science mode with other people on my server, gives some progression at least. As far as I'm aware ore generation isn't the same for each player either which will lead to problems with shared mining outputs later on.

Heh, okay. In that case it worked perfectly Thanks. Now I just need to work out why kerbals randomly go kia/mia

@godarklight, just to note that the 6716a3e116adb which changed the part names to include periods didn't appear to solve the problem where solidBooster.sm is a forbidden part. I had to disable the part checking to get around it.

Just started a v1.0 server with locked down parts and it's complaining smallBooster.sm is not a valid part. This is sort of reasonable as the part is called smallBooster_sm in both the client and the server parts list, however I'm not sure why it's deciding to tell the server is has a . instead of an _ Can anyone point me to where I should start investigating this?

How did you get around the fact the kethane maps reset each time you connect? or is it only me that gets that issue.

You, and the server itself, need to have the part you want to use in the KMPPartList.txt file. There is instructions in the readme file for the server on how it do it. If the server doesn't have it enabled you are out of luck though,

How does this server handle the kethane thing? doesn't it reset each time you join?

A couple of the mods for KSP, notably kethane, use the persistence file that is essentially regenerated each time you connect to the server and so resetting all the data for these mods. Looking at the code it doesn't look like there is an easy way for a mod to inject persistent data into the system as it stands, although my c# is very rusty so I'm happy to be corrected on this. I'm mostly wondering if anyone knows of a workaround for this.

You need to add the following lines to your KMPPartList.txt. I have this file in both the KMP Server directory and in my client one where the part list file game from (see the server README.txt) mumech.MJ2.AR202 mumech.MJ2.Pod After that it all worked with mechjeb happily. It the autowarp will try and warp in physics areas too which isn't allowed doesn't seem to hurt anything though.