Update READMEs

README.md

@@ -44,6 +44,7 @@ You can modify which functions are proxied by adding/removing entries in dll.def
 
 The current set up allows to use the proxy for the following DLLs:
 
-* `winhttp.dll` (All exports)
+* `winhttp.dll` (All exports, works better with Wine)
+* `version.dll` (All exports, better support for Unity 3)
 
-(WIP: Currently all build results are placed in separate folders; will be changed later)
+Simply rename the Doorstop DLL to use it as a different proxy (as long as the exports are included).

docs/dist_readme.md

@@ -12,7 +12,7 @@ Doorstop is released to the public domain under CC0 and can be distributed as-is
 
 ## Installation
 
-1. Put `version.dll` into the game's root directory
+1. Put `winhttp.dll` into the game's root directory
 2. In game's root directory, create a file `doorstop_config.ini` with the following contents:
 
 ```ini
@@ -30,6 +30,13 @@ redirectOutputLog=false
 4. Run the game
     * If run with the example, a file named `doorstop_is_alive.txt` should appear in the game's root with the success message.
 
+## Using Doorstop as `version.dll` proxy
+
+The official releases allow you to use Doorstop as `version.dll` proxy as well.  
+While `winhttp.dll` has been tested to have better support running on Wine, `version.dll` 
+appears more functional with Unity 3 games. As such, you can choose between `winhttp` and `version` proxies 
+by simply renaming the Doorstop DLL.
+
 ## Using Doorstop to execute assemblies
 
 Doorstop will execute any managed .NET assembly (version depends on version of Mono used by the game) with a valid [entry point](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/main-and-command-args/). In nutshell any of the following signatures are considered a valid entry point: