'Fortnite' Summer Skirmish: Streamer Reveals Details of $500K Week 2 Event
Will they get it right this time?
This past Saturday, Epic held the first event of its Summer Skirmish series with a Fortnite duos tournament worth $250,000. The event did not go as planned due to laggy servers resulting in the tournament being cut short. Epic has yet to give info on the second event in the series, but one streamer did reveal some details over social media.
Twitch streamer Rachel “Valkyrae” Hofstetter tweeted Wednesday about the second Fortnite Summer Skirmish event. Unlike the first one, this follow-up tournament will consist of solo matches, have a $500,000 prize pool, and will happen on Friday at 5 p.m. Eastern. Esports consultant Rod “Slasher” Breslau also tweeted about the details of the event, which he learned from his sources.
Like in the first Summer Skirmish event, this tournament will consist of 10 matches, however, the preliminary event only went to four matches. The original format was for a team to be declared the winners when the duo won two of the 10 matches, or if all 10 games were played, the team with the highest placement and most eliminations would win. Since players experienced so much lag making them unable to move in some instances, Epic decided to cut the tournament short after just four games. Even with only four matches played, Epic did make a ranking of all the teams, with first place taking $50,000.
Players in the tournament weren’t the only ones disappointed with the first Summer Skirmish. Viewers on Twitch and YouTube complained about the lack of action on-screen as teams were more strategic in matches, deciding to play defensively in order to survive as placing higher could be worth thousands of dollars.
Fortnite fans should expect an announcement from Epic Thursday about the event if it does take place on Friday.
High pings from the servers is an ongoing issue for Fortnite players ever since the release of Fortnite Season 5. The developer will conduct maintenance on the game Thursday morning, which will hopefully fix the problem.
