"Make sure the other team isn’t recording your POVs"
Yesterday, after a brief practice session, Jonathan "EliGE" Jablonowski came onto Twitter to express disappointment that a fellow North American team had been recording their side of the demo during a scrim.
PSA for teams: Make sure you check status on console before scrims to make sure the other team isn’t recording your POVs without your consent :) Pretty shady to do and so annoying teams are still doing this shit— Jonathan Jablonowski (@EliGE) October 8, 2018
After a brief bit of poking from the notorious CS:GO individual Don Haci, EliGE revealed the team to be Rogue. As such, we at Dust2.us dispatched a team of reporters to further investigate the incident.
First off, we spoke to EliGE to elaborate on his side of the incident. From this, he informed us that "its happened from other teams we have played before" and that it was the first time Liquid had scrimmed in North America for a while, going on to say that this was the first time they had played Rogue in North America. He also mentioned that he had tweeted about such an incident before, referring to this incident from January 2017, but didn't go into further details on that occasion.
From there we talked to Rogue's coach Matthew "mCe" Elmore to get their side of the incident. After he told us that "no matter what when you kick the GOTV it lags", he invited us to the Rogue scrim server to test what happened and expanded on that point:
What happens is every single time you change the map, if you put status in console, you see that there's GOTV. So on this server, it's very easy to kick on Dathost servers.
On the server we have we don't know how to turn it off, and frankly we just forget it's there, and when someone reminds us we kick it. So today with EliGE it was 5 or 10 minutes before we even played a round, so it wouldn't make sense for us to record it until we were in a round.
Afterwards he showed us what happened when you kicked the GOTV bot a number of times, indicating a small stutter during movement when it happened. We were then allowed to test it ourselves on their server, which gave the same result.