Valorant has dropped its latest version patch 5.08call him Chapter 5 Chapter 3 along with the introduction of a number of other changes. This time, Valorant has launched its new India-based agent. Varun Batracodenamed Portas well as introducing a few more cosmetic changes. However, one of the primary sources of revenue for Riot developers comes from Valorant weapon skins and other cosmetics, so Valorant has decided to be a philanthropist this time around for ‘Keep it Safer’ gunslinger.
this Keep it Safer Gun Buddy will be available for those who activate two factor authenticationor 2FA with basic authentication through Riot platforms. As a reward method, Riot is distributing this fellow in arms to raise awareness of account theft and instruct people to keep their accounts safe.
How to Request a ‘Keep it Safer’ Brother in Arms
To enable two-factor authentication and claim your mate, follow these steps:
- Open the web browser and visit the official site of Riot Games or just click to log in. here.
- Enter your login information and Login.
- Once in your account, go to the area that mentions Two-Factor Authentication. There will be a field that says email and a gray button that says “Enable”.
- Click Activate and you should now get a notification that an email has been sent to your registered email account.
- Sign in to your registered email account and search for the email from Riot Games with the subject “Enable Two-Factor Authentication”.
- In the mail, you have to click on the big red button that says “Enable Two-Factor Authentication”.
- After clicking the red button, a new window will open confirming that “Two-Factor Authentication” has been successfully enabled.
After enabling two-factor authentication, all you need is open game again and log in. Your brand new comrade in arms will be waiting for you. However, for those who have already enabled 2FA, they will have to go through the process again to claim the cosmetic. There was a glitch that could not assign Weapon Buddy to the corresponding account, but this was fixed with the Latest 5.08 patch.
