Settings loading and saving need more error checking, and handling of value not previously present in the settings file.

I need to find a formula that works properly beyond 45 degrees

using either one of the stock RenderSettings.ambientLight or vacuumAmbientColor causes issues, this would fix them and allow better control for a nicer look.

Detect the body color only for the portion that is under the vessel

PlanetShine is throwing up a warning box on KSP 1.1.1.
You may want to make it accept any patch level in 1.1.

This mod can be extracted into the top-level directory since everything writes to GameData -- except Alternate Colors and README.txt. The README.txt should go in the GameData/PlanetShine directory along with the LICENSE -- or at the very least be renamed to PlanetShine-README.txt to avoid collisions with other mods.

right now it's only controlled by two simple gradient, one for the atmospheric light, and one for the PlanetShine.

There should be more options, and we might want a stronger atmospheric light on low altitude than on the ground.

currently the surface light is of one color, however with the current system it should be possible to have a different color depending on the side, and maybe eliminating altogether the need to calculate the light direction in relation to the sunlit part of the body

See forum post: http://forum.kerbalspaceprogram.com/threads/109753-1-0-2-SKY-Scale-up-Kerbalism-for-You-Includes-a-2nd-Gas-Giant-v1-5-beta?p=1919557&viewfull=1#post1919557 :

http://imgur.com/a/GQR1H#0

THIS is an album showing quickly what's going on for me with the non-EVE syterion rings. It's possible it's a result of planetshine? I havn't snipped out my mods yet and troubleshot to figure out the exact result, i had originally just presumed it was a known issue.
You can see the essence of what happens: The rings are only visible from certain camera angles, and fade away or are even invisible at certain angles. The other rings are the EVE rings

I assume this is some legacy code. PlanetShine tries parsing the CelestialBodyColor nodes used by DistantObjectEnhancement, and it logs a lot of errors (trapped exceptions from a try/catch block). I realize these are handled exceptions, and they're not really errors, but I think it'd be better not to try to parse CelestialBodyColor nodes so the log doesn't clutter with

[ERR 09:32:28.927] [PlanetShine] An exception occured reading CelestialBodyColor node:
CelestialBodyColor
{
    name = Bop
    color = 100,86,76
}

The exception was:
System.ArgumentNullException: Argument cannot be null.
Parameter name: s
  at System.Double.Parse (System.String s, NumberStyles style, IFormatProvider provider) [0x00000] in <filename unknown>:0 
  at System.Single.Parse (System.String s) [0x00000] in <filename unknown>:0 
  at PlanetShine.ConfigManager.LoadBody (.ConfigNode bodySettings) [0x00000] in <filename unknown>:0 

(and so forth, once per world).

Options or auto detections to let other plugins to take full control of some things that PlanetShine affects.

I want to provide a convenient way for the user to switch between different presets according to his needs (streaming/recording, realistic).

Presets will be provided by individual preset config files and loaded across the whole GameData folder, allowing other mods/plugins to provide their own presets.

Whenever an external mod/plugin provides a new preset, the user will be prompted to ask if he wants to switch to this new one or keep his previous one.

The setting is saved, but there is no effect

Allow the user to create, edit, and save custom preset within the in-game menu of planetshine.

In the latest version - 1.9, random purple cubes and squares appear in the game. They normally stay where they spawn, with the exception of the squares which seem stuck to kerbals and obscure most of the IVA view.

I am running 1.1.0 now and I get a white square in my toolbar instead of the icon which I saw in 1.0.5.

The app appears to work fine, just some missing art.

This is to avoid module manager rebuilding the patches on each game loading instead of using the much faster cache. Read this for more information: m4v/RCSBuildAid#32

Requires a complete refactoring and cleaning of the current PlanetShine class

vacuumAmbientColor should be used strictly for vacuum ambient color: currently it's used while landed or in low altitude to provide global atmospheric illumination.

The issue is that when switching in map view, all celestial bodies are affected by this same vacuumAmbientColor.