This is great work. I'm pinning this thread and deleting the thread labeled voicebank template/list since it's now useless. Also pinning helps to keep it in an easy to remember place for those who need to come back to the spreadsheets for the mods they are creating.

@Jorshamo
You're basically saying that it is the soldier commenting on a sighting instead of Central. That kind of makes sense seeing as Bradford would say something the first time you saw it but not on missions after that. Like when you go into the gene therapy place and Shen says something like, "Does that look like they are helping people?". But your soldiers would make a comment even if there was another mission later with a similar place.

Also your theory would work with "Civilian Scream". I think when soldiers hear a civilian die far away on retaliation missions they say, "What was that?". So it supports the idea that it is the soldiers commenting on the smaller stuff.

Thank you for this. I knew that voice mods were increasing my memory usage but I didn't know how. I stuck to disabling my voice mods for now but this news should definitely be seen by voice modders, so hopefully people can update the ones they have already released.

• Here is a 20 minute video guide from Xander Sweetman to creating a basic voicepack. Helpful for new users getting started with the Unreal Editor program.
  How to make an XCom 2 Voice Pack
  
  
  
• Here is a 30 minute video guide from Zuff McGruff that can also be found under the guide section of the XCOM 2 Community Hub. Everything you need to use from the video is free.
  https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=626791383
  
  
  
• Here is an in depth google document tutorial for those who prefer to read step by step. Made by E3245 and posted on reddit.
  E3245's Guide[docs.google.com]
  
  
  Some additional links for XCOM 2 modding in general:
  XCOM 2 mod development subreddit
  
  Nexus forums modding resources thread[forums.nexusmods.com]
  
  
  More guides will be added. Please add guides that you have helped you or ones that you made yourself.

1. After downloading the XCOM 2 Development Tools you may get the error saying, "Cannot find one or more components. Please reinstall the application."
   
   "Turns out that Microsoft Visual Studio 2013 Isolated Shell redistributable package shipped with the tool requires Win XP SP 3 and thus can't be installed for Win 7. The solution is to download it manually. https://www.microsoft.com/en-us/download/details.aspx?id=40764."
   
   
2. Next read XCOM 2 SDK\Documentation. It is only 8 pages. Helpful for those new to modding or planning to make extensive use of the Modbuddy.
   
   
   Three main takeaways from the documentation:
   
3. Modbuddy for XCOM2, similar to previous versions of Modbuddy released for Civilization, uses the visual studio isolated shell to provide an IDE for modding. You can find the redistributables in the game’s installation directory under the “Binaries” folder. Example: “\SteamLibrary\steamapps\common\XCOM 2 SDK\Binaries\Redist”. There are two redistributables provided: one for visual studio and one for UE3, please install both.
   
   You should only needed to install the UE3Redist.exe as we downloaded the new vs_isoshell.exe during the first step.
   
   
4. After launching Modbuddy for the first time, users will want to set general settings on the IDE related to where XCOM2 is installed. Choose Tools->Options, and then scroll down to the bottom of the options menu as shown below. Verify that the paths are set correctly.
   
   XCOM 2 Install Path – This path should point to the GAME installation, ending in XComGame.
   
   XCOM 2 User Path – This path should point to the SDK installation, ending in XComGame.
   
   The User Path should end in the XComGame that is under the SDK, not the XCOM 2 game folder. If you set it up to the wrong one then XCOM 2 Editor will get an error saying, "The system can not find the file specified."
   
   
5. By default, build information in the Visual Studio Isolated Shell is set to “minimal’. To get information from the build process / script compiler, you will want to change this setting. Choose Tools -> Options -> Projects and Solutions -> Build and Run. Change the two verbosity dropdowns at the bottom of the options panel to “Normal”, then hit OK.