AD

Friday, 28 February 2020

Riot's Unrevealed FPS Seems to Be Called Valorant

League of Legends developer Riot Games is working on an FPS codenamed Project A - but recent details suggest it will be titled Valorant. Now, a new screenshot of the game, and several of its characters, appears to have leaked. Earlier this week, RespawnFirst pointed to a trademark for Valorant filed by Riot, as well as a Twitter account created at around the same time as the trademark, @PlayValorant. The account is followed by multiple pro gamers and FPS streamers despite being a next-to empty page. Yesterday, a Project A fan account also posted what appears to be a leaked screenshot of the game featuring a character select screen for a character called Sage: That screenshot, if legitimate, also appears to confrim characters called Viper and Brimstone, alongside a number of character portraits. This design for Sage appears to match up with previously-shown Project A footage (below) of a character that uses a green orb to summon walls and resurrect teammates. Sage's abilities shown in the image match with that footage, and place her as functioning something like Overwatch's Mercy and Moira characters. [ignvideo url="https://www.ign.com/videos/2019/10/16/riot-games-project-a-announcement-trailer"] Riot announced Project A – a PC hero shooter unconnected to the universe of League of Legends - at the end of last year. The game will be set on a near-future Earth, and will take the form of a 5v5 shooter with a search-and-destroy mode. Former Counter-Strike: Global Offensive pro HenryG said it felt most similar to CS:GO in action. It's not the only secretive game in development at Riot (which, for many years, only worked on League of Legends) – a long-rumoured fighting game, Project L is also in the works, alongside several others. [widget path="global/article/imagegallery" parameters="albumSlug=riot-games-competitive-pc-shooter-codenamed-project-a-screenshots&captions=true"] [poilib element="accentDivider"]

from IGN News https://ift.tt/2whq2Ze
via IFTTT

No comments:

Post a Comment