Preparing for v0.3

Update readme, and add some breakthrough KSP config patchers.

Author: R-T-B

README.txt

@@ -17,16 +17,16 @@ Sure, you can, if your game offers it (Kerbal does). It should work. Dunno. I us
 
 So, this transmits no data at all?
 
-Pretty close to nothing. It merely "pings" the main Unity Telemetry servers at boot (that seems unavoidable and is a core unity functionality), but if you examine the packets in Wireshark all fields should be null or blank strings. It should never contact the server again, and even if it does, it will still all be empty data. Literally the only string in any of my source code that it could possibly transmit is it's version, which is humourously set to "STOPMININGMYDATAUNITY1.0"
+Pretty close to nothing. At the very least, THESE dlls transmit nothing.  The Unity engine may still try in certain games, but there is a settings file for most of them (I provide a settings patcher script for KSP) that should patch it to ensure it only contacts the server once with some basic platform config data, and then it should never do so again in the launch. In my DLLs, literally the only string in any of my source code that it could possibly transmit is it's version, which is humourously set to "STOPMININGMYDATAUNITY1.0"
 
-Still, any contact at all beyond the initial "pings" is not ideal, and should be able to be overridden/stopped. If you detect any traffic to a unity controlled domain or ip using a tool like wireshark, and it's been more than 30 seconds after launch, you have a legitimate cause to open an issue at github. Please do so.
+Still, any contact at all beyond the initial "pings" is not ideal, and should be able to be overridden/stopped. If you detect any traffic to a unity controlled domain or ip using a tool like wireshark, and it's been more than 10 seconds after launch, you have a legitimate cause to open an issue at github. Please do so.
 
 So, I installed this in gamedata and nothing happened!
 
-God dang it bobby, read the manual! You're supposed to put it in KSPINstall\KSP_x64_Data\Managed, replacing your existing dlls (other Unity games, wherver your telemetry dlls are put them there and replace the originals. Maybe take a backup, who knows?)
+God dang it bobby, read the manual! You're supposed to put it in KSPINstall\KSP_x64_Data\Managed, replacing your existing dlls (other Unity games, wherver your telemetry dlls are put them there and replace the originals. Maybe take a backup, who knows?).  Also, if you are playing Kerbal, please run the config patcher script for your platform. (.cmd for windows, .sh for *nix/OSX)
 
-Why is the release for 1.7 so...  old?  Also, it still transmits some data!
+Why is the release for 1.7 still transmiting some data!?
 
-1.7 and Unity 2017 support are an ongoing issue.  See here:
+1.7 and Unity 2017 support are an ongoing issue.  You will probably need to patch the platform config file for most of these. See here for an example using KSP (which I include a patcher script for):
 
 https://github.com/R-T-B/UnityAnalyticsKiller/issues/2

UnityConfigKiller_KSP.cmd

@@ -0,0 +1,7 @@
+cd %HOMEPATH%
+cd AppData\LocalLow\Squad\"Kerbal Space Program"\Unity
+cd ????????-????-????-????-????????????
+cd Analytics
+echo "{"analytics":{"events":{"custom_event":{"max_event_per_hour":1}},"enabled":false},"connect":{"limit_user_tracking":true,"player_opted_out":true,"enabled":false},"performance":{"enabled":false}}" > config
+attrib +r config
+exit

UnityConfigKiller_KSP.sh

@@ -0,0 +1,6 @@
+cd ~/AppData/LocalLow/Squad/"Kerbal Space Program"/Unity
+cd ????????-????-????-????-????????????
+cd Analytics
+echo "{"analytics":{"events":{"custom_event":{"max_event_per_hour":1}},"enabled":false},"connect":{"limit_user_tracking":true,"player_opted_out":true,"enabled":false},"performance":{"enabled":false}}" > config
+chmod 444 config
+exit