![how to update smite launcher how to update smite launcher](https://techquack.com/wp-content/uploads/2021/07/SMITE-Online-Game-image.jpg)
Thanks MSI and other manufacturers that do this! Updated the system information box in the debug tab to be a bit larger to allow longer motherboard names to be displayed correctly. This error happens when an internal error occurred during the config backup routine.
![how to update smite launcher how to update smite launcher](https://m.media-amazon.com/images/I/B1P4LO47KIS._CR3,0,1914,1080_SR342,193__BG0,0,0__QL65_.png)
#How to update smite launcher code
Changed error code 003 to be more descriptive. These errors happen when individual files of the config backup fail being copied. Changed error code 001 - 002 - 012 to be more descriptive. Usually this happens when they're set to read only mode. These errors happen when the optimizer could not write to the config files. Changed error code 004 - 005 - 013 to be more descriptive. > This made it so that changing the FPS uncap option in the advanced tab had no effect. Fixed a bug with the Desired FPS (Uncap) option always using the simple tab input even when in advanced mode. > All of this only applies to users that are making use of the launcher bypass or the in-game log-in form. It is highly recommended to NOT stay logged in to improve security. > Critical information like this should NEVER be stored as plain-text. > We are not interested in this information and it is a massive security risk as debug dumps usually get posted publicly. > Steps have been implemented to ensure that this critical information is filtered out so that it is NOT being stored and sent. > This behavior is unacceptable as this file is packed when creating a debug dump. For whatever reason Hi-Rez decided it is a good idea to store login information and the access token in the BattleGame.ini file which I discovered today.