-
-
Notifications
You must be signed in to change notification settings - Fork 55
Installation
If the install links are not working for you, this is the preferred method to use TF2BD.
This version is entirely self contained within its folder (except what it puts in the hl2/tf/custom directory) and can be placed anywhere on your computer that your account has read/write access to (this should be most non-system places). It should not be anywhere in your tf2 install location. Many users just leave it in their download folder.
You may need to install the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019.
This link will download the latest public release zip. If you would like to use the preview or nightly channel you can select that on first run.
Before even looking at this, consider using the portable version of TF2BD. It is significantly easier and the recommended method. There is no difference in features and many users prefer the familiarity of non-uwp apps.
If you do not have access to the Microsoft Store (which is tightly coupled with the mechanism by which those install links work), you can attempt to install TF2 Bot Detector by running some PowerShell commands. It should be noted that the way in which a user or administrator disables the windows store may break quite a few things and you may get further errors even attempting to use the Add-AppxPackage command since it is a part of the Appx module. This module seems to be sensitive to the various scripts and programs users use to strip out certain Windows features. Since there are so many way this install method can be broken, it is beyond the purview of this information to try and work every time for ever user.
The "main" command that is needed to install modern Windows packages is Add-AppxPackage. This command is part of the module Appx. More about the command can be read about here. You can read more about MSIX (aka AppX) here. There are two major dependencies (that users have so far reported missing) for TF2BD, the Microsoft C++ redistributable and C++ Runtime framework packages for Desktop Bridge.
The base idea is that you want to install the dependencies, then pass the desired msixbundle to Add-AppxPackage. You should be able to just point the Add-AppxPackage command at the dependencies via the flag -DependencyPath and it should just grab them for you. This has worked for some users and not worked for others.
There are 3 release "channels". There is the major version release known as "public", the still pretty stable but closer to source "preview" build, and lastly there is the "nightly" which is a direct compile of the master branch. It is generally recommended to at least run preview since it is pretty stable and offeres new features. If you can stomach things sometimes ( breaking for a few hours, the nightly build is recommended. You can always change which channel you use down the line.
https://tf2bd-util.pazer.us/AppInstaller/Nightly.msixbundle
https://tf2bd-util.pazer.us/AppInstaller/Preview.msixbundle
https://tf2bd-util.pazer.us/AppInstaller/Public.msixbundle
Here is an example of what an install command might look like:
Add-AppxPackage -Path "https://tf2bd-util.pazer.us/AppInstaller/Public.msixbundle" `
-ForceApplicationShutdown `
-DependencyPath "https://tf2bd-util.pazer.us/AppInstaller/vcredist.x64.msix","https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx"Add-AppxPackage -Path "https://tf2bd-util.pazer.us/AppInstaller/Public.msixbundle" `
-ForceApplicationShutdown `
-DependencyPath "https://tf2bd-util.pazer.us/AppInstaller/vcredist.x86.msix","https://aka.ms/Microsoft.VCLibs.x86.14.00.Desktop.appx"For a detailed explanation of this command and its usage read this
Some have reported the error Add-AppxPackage: The 'Add-AppxPackage' command was found in the module 'Appx', but the module could not be loaded. For more information, run 'Import-Module Appx'., upon running Import-Module Appx the error Import-Module: Operation is not supported on this platform. (0x80131539) is received. This has not been solved and not much effort has been put towards solving it since it indicates something has been deeply borked about that windows install. Either delve into madness to try and fix it or use the portable installation. The latter is the official recommendation. If you do the former, report back. What you learn could help someone else.
Microsoft continuously changes the rules about UWP apps, and we don't have time to deal with it anymore. So this is no longer supported in any capacity.
These are one click installs that should work on standard Windows 10 installs.