FernandoTBarros · FernandoTBarros · Jan 12, 2020 · Jan 13, 2020 · Jan 13, 2020 · Jan 13, 2020
diff --git a/.gitignore b/.gitignore
@@ -252,3 +252,6 @@ ModelManifest.xml
 *.crt
 /Werewolf for Telegram/Werewolf Control/Languages
 /Werewolf for Telegram/Werewolf Node/Languages
+*.pubxml
+
+Update.exe
diff --git a/README.md b/README.md
@@ -1,5 +1,7 @@
 # Werewolf for Telegram
 
+[![@werewolfbot MAU](https://tgbotmau.quoi.dev/api/bot/werewolfbot/mau/badge?style=flat "@werewolfbot MAU")](https://tgbotmau.quoi.dev/?bot=werewolfbot)
+
 This is the main repo for Werewolf for Telegram.
 
 For language file updates, please submit the xml file on Telegram to the [support chat](http://telegram.me/werewolfsupport) and ask for assistance
@@ -20,40 +22,40 @@ To set up werewolf on a private server, follow these steps:
    * On your server, open regedit, and go to `HKLM\SOFTWARE\`, create a new Key named `Werewolf` (HKLM - HKEY_LOCAL_MACHINE)
    * In the new key create a new string value named `ProductionAPI`.  
    * Paste your API token here.
-2. Grab the Werewolf Database.sql file from this repository
+2. Grab the werewolf.sql file from this repository
    * Open the file in notepad, notepad++, whatever you use
    * Double check the path at the top of the file - update it if you are using a different SQL version
    * Run the sql script.  This will create the `werewolf` database and all the tables / views / stored procs to go with it
    * If you already have some admins (including yourself), add their TelegramID's to the `dbo.Admin` table
 		* In order to obtain your ID, headover to your bot in telegram and /Start. After that, toss a random text to it. Enter this URL to your browser (https://api.telegram.org/botYOURTELEGRAMBOTAPIKEY/getUpdates)
 3. Now it's time to compile the source code
-   * In the Database project, you will need to create an Internal.settings file
-	  * In order to create the Internal.settings file, right click on Database -> Add -> New Item
-	  * Under Visual C# Items -> Settings File and name it as stated.
-      * Create a string setting named `DBConnectionString`, Application Scope, and set the Value to your SQL connection string for the database you created in step 2
-         * Connection String should be this (change the values) `metadata=res://*/WerewolfModel.csdl|res://*/WerewolfModel.ssdl|res://*/WerewolfModel.msl;provider=System.Data.SqlClient;provider connection string="data source=SERVERADDRESS;initial catalog=werewolf;user id=USERNAME;password=PASSWORD;MultipleActiveResultSets=True;App=EntityFramework"`
-			* If you are using Windows Authentication for your MSSQL Server, do take note that the password property will NO Longer be required. You're required to replace it with "Trusted_Connection=True;" instead.
+   * On your server, open regedit
+   * In the `Werewolf` key create a new string value named `BotConnectionString`.
+   * Paste the Connection String here.
+        * Connection String should be this (change the values) `metadata=res://*/WerewolfModel.csdl|res://*/WerewolfModel.ssdl|res://*/WerewolfModel.msl;provider=System.Data.SqlClient;provider connection string="data source=SERVERADDRESS;initial catalog=werewolf;user id=USERNAME;password=PASSWORD;MultipleActiveResultSets=True;App=EntityFramework"`
+			* If you are using Windows Authentication for your MSSQL Server, do take note that the password property will NO Longer be required. You're required to replace it(both user id and password) with "Trusted_Connection=True;" instead.
       * .gitignore has marked this file, so it won't be committed. **However, when you create the setting, VS will copy it to the app.config - make sure to remove it if you plan on committing back to your fork**
-   * In Visual Studio, open the solution.  Make sure you are set to `RELEASE` build.  You may want to go into `Werewolf_Control.Handlers.UpdateHandler.cs` and change `internal static int Para = 129046388;` to match your id.  Also, double check the settings.cs files in both Control and Node.
+   * Create another new string value named BotanReleaseAPI. You can leave this blank if you don't want to track your usage using BotanIO.
+   * If you plan on running another instance of the bot as beta, add another two new string values named BotanBetaAPI and BetaAPI. Again, you can leave BotanBetaAPI empty if you want. Set BetaAPI to the token of your beta bot.
+   * In Visual Studio, open the solution.  Make sure you are set to `RELEASE` build.  You may want to go into `Werewolf_Control.Helpers.UpdateHelper.cs` and add your id to `internal static int[] Devs = { ... }`.  Also, double check the `Settings.cs` files in both `Werewolf Control/Helpers` and `Werewolf Node/Helpers`.
    * Build the solution
 4. Server directories
    * Pick any directory for your root directory
 
    | Directory | Contents |
    |-----------|---------:|
-   |`root\Control`|Control build|
-   |`root\Node 1`|Node build|
-   |`root\Node <#>`|Node updates can be added to a new Node folder.  Running `/replacenodes` in Telegram will tell the bot to automatically find the newest node (by build time) and run it|
-   |`root\Logs`|Node crash directory|
-   |`root\Languages`|Language xml files|
+   |`root\Instance Name\Control`|Control build|
+   |`root\Instance Name\Node 1`|Node build|
+   |`root\Instance Name\Node <#>`|Node updates can be added to a new Node folder.  Running `/replacenodes` in Telegram will tell the bot to automatically find the newest node (by build time) and run it|
+   |`root\Instance Name\Logs`|Logging directory|
+   |`root\Languages`|Language xml files - These files are shared by all instances of Werewolf|
 
    * Note - Once all nodes are running the newest version (Node 2 directory), the next time you update nodes, you can put the new files in Node 1 and `/replacenodes`.  Again, the bot will always take whichever node it finds that is the newest, as long as the directory has `Node` in the name.  **do not name any other directory in the root folder anything with `Node` in it**
 5. Fire up the bot!
-
-
+6. If you try to start a game now, you will notice that the bot will just respond with an error. That is because you didn't update the gif ids yet. See the section below for instructions on how to do this.
 
 
 ## GIF SUPPORT
 In order to use GIFs with the bot, you will need to "teach" the bot the new GIF IDs.  From Telegram, run `/learngif`, the bot will respond with `GIF learning = true`.  Now send it a GIF, and the bot will reply with an ID.  Send the bot all the GIFs you need.  In the Node project, go to Helpers > Settings.cs and find the GIF lists.  You'll need to remove all of the existing IDs and put in the IDs you just got from the bot.
 
-You can test these by running `/dumpgifs` (preferrably in PM!).  Make sure you check out DevCommands.cs, and look at the `DumpGifs()` method - most of it is commented out.  Uncomment what you need.
+You can test these by running `/dumpgifs` (preferrably in Private Message!).  Make sure you check out DevCommands.cs, and look at the `DumpGifs()` method - most of it is commented out.  Uncomment what you need.
diff --git a/Werewolf for Telegram/Achievements.txt b/Werewolf for Telegram/Achievements.txt
@@ -18,5 +18,5 @@ Masochist : Be lynched as the Tanner
 Wobble Wobble : Survive a game as the Drunk
 Inconspicuous : Make it through a game without a single lynch vote against you (20+ players)
 Survivalist : Survive 100 games
-Black Sheep : Get lynched first 3 times in a row
-Promiscuous : Finish the game alive as a harlot without repeating visits or staying at home (5+ nights)
+Black Sheep : Get lynched first 3 times in a row.
+Promiscuous : Finish the game alive as a harlot without repeating visits or staying at home (5+ nights)
diff --git a/Werewolf for Telegram/Bot Watcher/App.config b/Werewolf for Telegram/Bot Watcher/App.config
@@ -1,6 +1,6 @@
-<?xml version="1.0" encoding="utf-8" ?>
+<?xml version="1.0" encoding="utf-8"?>
 <configuration>
     <startup> 
-        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.2" />
+        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8"/>
     </startup>
-</configuration>
+</configuration>
diff --git a/Werewolf for Telegram/Bot Watcher/Bot Watcher.csproj b/Werewolf for Telegram/Bot Watcher/Bot Watcher.csproj
@@ -9,9 +9,10 @@
     <AppDesignerFolder>Properties</AppDesignerFolder>
     <RootNamespace>Bot_Watcher</RootNamespace>
     <AssemblyName>Bot Watcher</AssemblyName>
-    <TargetFrameworkVersion>v4.5.2</TargetFrameworkVersion>
+    <TargetFrameworkVersion>v4.8</TargetFrameworkVersion>
     <FileAlignment>512</FileAlignment>
     <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
+    <TargetFrameworkProfile />
   </PropertyGroup>
   <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
     <PlatformTarget>AnyCPU</PlatformTarget>